openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #04644
Re: dns issue?
On Mon, 2011-10-10 at 16:07 -0400, Sharif Islam wrote:
> I am still stuck with this problem: my instances can ping only with ip
> addresses. I deleted nova-network and created it again and then fired up
> an instance. But still resolv.conf shows nameserver 10.0.1.1. I only
> have one instance running now, this is not the route looks (a.b.c.d is
> my public ip. v.x.y.z is my nova network host):
>
> # iptables -L -t nat|grep 10.0
> DNAT all -- anywhere a.b.c.d to:10.0.1.2
> ACCEPT all -- 10.0.0.0/8 10.128.0.0/24
> ACCEPT all -- 10.0.0.0/8 10.0.0.0/8
> DNAT all -- anywhere a.b.c.d to:10.0.1.2
> SNAT all -- 10.0.1.2 anywhere to:a.b.c.d
> SNAT all -- 10.0.0.0/8 anywhere to:v.x.y.z
>
>
> mysql> select * from networks \G
> *************************** 1. row ***************************
> created_at: 2011-10-10 18:32:06
> updated_at: 2011-10-10 18:32:54
> deleted_at: NULL
> deleted: 0
> id: 24
> injected: 0
> cidr: 10.0.1.0/24
> netmask: 255.255.255.0
> bridge: br100
> gateway: 10.0.1.1
> broadcast: 10.0.1.255
> dns: 8.8.4.4
> vlan: NULL
> vpn_public_address: NULL
> vpn_public_port: NULL
> vpn_private_address: NULL
> dhcp_start: 10.0.1.2
> project_id: NULL
> host: i26
> cidr_v6: NULL
> gateway_v6: NULL
> label: public
> netmask_v6: NULL
> 1 row in set (0.00 sec)
>
> root@i-00000499:~# cat /etc/resolv.conf
> domain novalocal
> search novalocal
> nameserver 10.0.1.1
>
> How does nova assign the nameserver to the VMs? Can I change it someone
> so it has 8.8.4.4?
I assume you are using Vlan or Flatdhcp? If so add --dns-server=8.8.4.4
to your flags file. The network managers that use dnsmasq do not respect
the db entries.
Happy Hacking!
7-11
Follow ups
References