The VM can not setup correct DNS server

asked 2013-10-25 00:15:22 -0500

Dongjh gravatar image

updated 2013-10-25 16:24:45 -0500

smaffulli gravatar image

I created the vmnet and specified the dns servers are 192.168.11.36/192.168.11.24,but when i boot the VM, the DNS server always be the gateway IP. What is the issue ?**

root@compute1:~# nova network-create vmnet --fixed-range-v4=192.168.11.0/24 --bridge-interface=br100 --multi-host=T --gateway=192.168.11.253 --dns1=192.168.11.36 --dns2=192.168.11.24

root@compute1:~# nova net-list
+--------------------------------------+-------+-----------------+
| ID                                   | Label | CIDR            |
+--------------------------------------+-------+-----------------+
| 31762768-d03c-4871-9d8e-d521afeaa190 | vmnet | 192.168.11.0/24 |
+--------------------------------------+-------+-----------------+

root@compute1:~# nova network-show 31762768-d03c-4871-9d8e-d521afeaa190
+---------------------+--------------------------------------+
| Property            | Value                                |
+---------------------+--------------------------------------+
| bridge              | br100                                |
| vpn_public_port     | 1000                                 |
| dhcp_start          | 192.168.11.3                         |
| bridge_interface    | br100                                |
| updated_at          | 2013-10-25T03:57:58.000000           |
| id                  | 31762768-d03c-4871-9d8e-d521afeaa190 |
| cidr_v6             | None                                 |
| deleted_at          | None                                 |
| gateway             | 192.168.11.253                       |
| rxtx_base           | None                                 |
| label               | vmnet                                |
| priority            | None                                 |
| project_id          | 382ce85ef00948a3a1442e44f9d033ed     |
| vpn_private_address | 192.168.11.2                         |
| deleted             | 0                                    |
| vlan                | 100                                  |
| broadcast           | 192.168.11.255                       |
| netmask             | 255.255.255.0                        |
| injected            | False                                |
| cidr                | 192.168.11.0/24                      |
| vpn_public_address  | 10.10.10.182                         |
| multi_host          | True                                 |
| dns2                | 192.168.11.24                        |
| created_at          | 2013-10-25T03:56:08.000000           |
| host                | None                                 |
| gateway_v6          | None                                 |
| netmask_v6          | None                                 |
| dns1                | 192.168.11.36                        |
+---------------------+--------------------------------------+

root@compute1:~# ssh -l cirros 192.168.11.191
The authenticity of host '192.168.11.191 (192.168.11.191)' can't be established.
RSA key fingerprint is ad:84:6f:04:39:38:38:ff:25:7c:5f:1f:d5:4b:c3:14.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.11.191' (RSA) to the list of known hosts.
cirros@192.168.11.191's password:

$ hostname
cirros

$ cat /etc/resolv.conf
search novalocal
nameserver 192.168.11.253

root@compute1:~# nova console-log ec8f7952-d56a-46f5-a933-6d96bd20660d
......
Sending discover...
Sending select for 192.168.11.194...
Lease of 192.168.11.194 obtained, lease time 120
deleting routers
route: SIOCDELRT: No such process
adding dns 192.168.11.253
cirros-ds 'net' up at 1.41
checking http://169.254.169.254/2009-04-04/instance-id
failed 1/20: up 1.43. request failed
failed 2/20: up 3.52. request failed
failed 3/20: up 5.53. request failed
failed 4/20: up 7.54. request failed
failed 5/20: up 9.55. request failed
failed 6/20: up 11.56. request failed
failed 7/20: up 13.57. request failed
failed 8/20: up 15.58. request failed
failed 9/20: up 17.59. request failed
failed 10/20: up 19.60. request failed
failed 11/20: up 21.61. request failed
failed 12/20: up 23.62. request failed
failed 13/20: up 25.63. request failed
failed 14/20: up 27.64. request failed
failed 15/20: up 29.66. request failed
failed 16/20: up 31.67. request failed
failed 17/20: up 33.68. request failed
failed 18/20: up 35.69. request failed
failed 19/20: up 37.70. request failed
failed 20/20: up 39.71. request failed
failed to read iid from metadata. tried 20
no results found for mode=net. up 41.72. searched: nocloud configdrive ec2
failed ...
(more)
edit retag flag offensive close delete

Comments

I mean the nameserver in resolv.conf in the VM's is always been set to the gateway IP.

Dongjh ( 2013-10-25 00:17:58 -0500 )edit