[Bug 59375] Re: One DNS by DHCP setting overwrites another
** Changed in: Ubuntu Sourcepackagename: None => resolvconf -- One DNS by DHCP setting overwrites another https://launchpad.net/bugs/59375 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59375] Re: One DNS by DHCP setting overwrites another
I can confirm this issue in Ubuntu edgy server. When connecting to two separate host networks, with their own dhcp servers respectively, the newest registration overwrites the nameserver entry in /etc/resolve.conf. To demonstrate, take for example, interfaces eth0 and eth1 which connect to the two respective dhcp networks. Use the 'dhclient ' and cat /etc/resolve.conf to see how the file changes. E.g. $ cat /etc/resolv.conf search localdomain nameserver 172.16.254.2 $ $ sudo dhclient eth0 [... warning about killing previous dhclient process] Listening on LPF/eth0/00:0c:29:ba:1e:2d Sending on LPF/eth0/00:0c:29:ba:1e:2d Sending on Socket/fallback DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPACK from 192.168.60.254 bound to 192.168.60.128 -- renewal in 689 seconds. $ $ cat /etc/resolv.conf search localdomain nameserver 192.168.60.1 "nameserver 172.16.254.2" was set for eth1, but when dhcpclient renews the lease for eth0, it is overwritten by "nameserver 192.168.60.1". This can causes havoc with host lookups failing or one or the other side. You can manually append the missing nameserver to /etc/resolve.conf, but it gets overwritten as soon as a lease is renewed. E.g. $ sudo echo "nameserver 172.16.254.2" >> /etc/resolve.conf (or use a suitable text editor, i.e. nano, vim, gedit) There is a workaround with the dhclient.conf file. Refer to man dhclient.conf. One can hardcode DNS nameservers in with prepend. E.g. add the following line to /etc/dhcp3/dhclient.conf: prepend domain-name-servers 192.168.60.1, 172.16.254.2; Now, no matter when dhclient gets new leases, it will first place those name servers in /etc/resolve.conf. Note, this is more of a hard-coded hack. 1. The dns server address may change, and 2. duplicate entries may result in /etc/resolve.conf. Another avenue to look at is installing resolveconf -- One DNS by DHCP setting overwrites another https://launchpad.net/bugs/59375 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59375] Re: One DNS by DHCP setting overwrites another
Confirmed. We see same problem in Hardy. ** Changed in: resolvconf (Ubuntu) Status: New => Confirmed -- One DNS by DHCP setting overwrites another https://bugs.launchpad.net/bugs/59375 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59375] Re: One DNS by DHCP setting overwrites another
I couldn't reproduce the error on hardy using vpnc + resolvconf + dnsmasq(on and off). But I have wicd instead of NetworkManager, but that shouldn't affect resolvconf functionality. Everything works fine, do you have the resolv.conf managed by resolvconf? There should be a message inside the resolv.conf about it being generated,etc. If not, it was probably ovewritten by something that still doesn't play well with resolvconf. Is /etc/resolv.conf a symbolic link (as is should be, to /etc/resolvconf/run/resolv.conf) or a normal file? Q: What files are present in /etc/resolvconf/run/interfaces/ after a lease? Each file should contain a list of nameservers for each interfaces - resolvconf glues these together to create the /etc/resolvconf/run/resolv.conf. NOTE: There are restrictions: resolvconf splits the "nameserver" and "search" entries and from the nameservers it get up ti 3 entries or up to the 127.0.0.1, whichever is sooner, e.g: nameserver 127.0.0.1 nameserver 10.0.0.1 nameserver 192.168.0.1 will give: nameserver 127.0.0.1 (this is useful when you have a local DNS cacher, etc.) Hope this helps someone. -- One DNS by DHCP setting overwrites another https://bugs.launchpad.net/bugs/59375 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59375] Re: One DNS by DHCP setting overwrites another
I couldn't reproduce the error on hardy using vpnc + resolvconf + dnsmasq(on and off). But I have wicd instead of NetworkManager, but that shouldn't affect resolvconf functionality. Everything works fine, do you have the resolv.conf managed by resolvconf? There should be a message inside the resolv.conf about it being generated,etc. If not, it was probably ovewritten by something that still doesn't play well with resolvconf. Is /etc/resolv.conf a symbolic link (as is should be, to /etc/resolvconf/run/resolv.conf) or a normal file? Q: What files are present in /etc/resolvconf/run/interfaces/ after a lease? Each file should contain a list of nameservers for each interfaces - resolvconf glues these together to create the /etc/resolvconf/run/resolv.conf. NOTE: There are restrictions: resolvconf splits the "nameserver" and "search" entries and from the nameservers it get up ti 3 entries or up to the 127.0.0.1, whichever is sooner, e.g: nameserver 127.0.0.1 nameserver 10.0.0.1 nameserver 192.168.0.1 will give: nameserver 127.0.0.1 (this is useful when you have a local DNS cacher, etc.) Hope this helps someone. -- One DNS by DHCP setting overwrites another https://bugs.launchpad.net/bugs/59375 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59375] Re: One DNS by DHCP setting overwrites another
** Changed in: Ubuntu Sourcepackagename: None => resolvconf -- One DNS by DHCP setting overwrites another https://launchpad.net/bugs/59375 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59375] Re: One DNS by DHCP setting overwrites another
I can confirm this issue in Ubuntu edgy server. When connecting to two separate host networks, with their own dhcp servers respectively, the newest registration overwrites the nameserver entry in /etc/resolve.conf. To demonstrate, take for example, interfaces eth0 and eth1 which connect to the two respective dhcp networks. Use the 'dhclient ' and cat /etc/resolve.conf to see how the file changes. E.g. $ cat /etc/resolv.conf search localdomain nameserver 172.16.254.2 $ $ sudo dhclient eth0 [... warning about killing previous dhclient process] Listening on LPF/eth0/00:0c:29:ba:1e:2d Sending on LPF/eth0/00:0c:29:ba:1e:2d Sending on Socket/fallback DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPACK from 192.168.60.254 bound to 192.168.60.128 -- renewal in 689 seconds. $ $ cat /etc/resolv.conf search localdomain nameserver 192.168.60.1 "nameserver 172.16.254.2" was set for eth1, but when dhcpclient renews the lease for eth0, it is overwritten by "nameserver 192.168.60.1". This can causes havoc with host lookups failing or one or the other side. You can manually append the missing nameserver to /etc/resolve.conf, but it gets overwritten as soon as a lease is renewed. E.g. $ sudo echo "nameserver 172.16.254.2" >> /etc/resolve.conf (or use a suitable text editor, i.e. nano, vim, gedit) There is a workaround with the dhclient.conf file. Refer to man dhclient.conf. One can hardcode DNS nameservers in with prepend. E.g. add the following line to /etc/dhcp3/dhclient.conf: prepend domain-name-servers 192.168.60.1, 172.16.254.2; Now, no matter when dhclient gets new leases, it will first place those name servers in /etc/resolve.conf. Note, this is more of a hard-coded hack. 1. The dns server address may change, and 2. duplicate entries may result in /etc/resolve.conf. Another avenue to look at is installing resolveconf -- One DNS by DHCP setting overwrites another https://launchpad.net/bugs/59375 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59375] Re: One DNS by DHCP setting overwrites another
Confirmed. We see same problem in Hardy. ** Changed in: resolvconf (Ubuntu) Status: New => Confirmed -- One DNS by DHCP setting overwrites another https://bugs.launchpad.net/bugs/59375 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59375] Re: One DNS by DHCP setting overwrites another
** Changed in: Ubuntu Sourcepackagename: None => resolvconf -- One DNS by DHCP setting overwrites another https://launchpad.net/bugs/59375 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59375] Re: One DNS by DHCP setting overwrites another
I can confirm this issue in Ubuntu edgy server. When connecting to two separate host networks, with their own dhcp servers respectively, the newest registration overwrites the nameserver entry in /etc/resolve.conf. To demonstrate, take for example, interfaces eth0 and eth1 which connect to the two respective dhcp networks. Use the 'dhclient ' and cat /etc/resolve.conf to see how the file changes. E.g. $ cat /etc/resolv.conf search localdomain nameserver 172.16.254.2 $ $ sudo dhclient eth0 [... warning about killing previous dhclient process] Listening on LPF/eth0/00:0c:29:ba:1e:2d Sending on LPF/eth0/00:0c:29:ba:1e:2d Sending on Socket/fallback DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPACK from 192.168.60.254 bound to 192.168.60.128 -- renewal in 689 seconds. $ $ cat /etc/resolv.conf search localdomain nameserver 192.168.60.1 "nameserver 172.16.254.2" was set for eth1, but when dhcpclient renews the lease for eth0, it is overwritten by "nameserver 192.168.60.1". This can causes havoc with host lookups failing or one or the other side. You can manually append the missing nameserver to /etc/resolve.conf, but it gets overwritten as soon as a lease is renewed. E.g. $ sudo echo "nameserver 172.16.254.2" >> /etc/resolve.conf (or use a suitable text editor, i.e. nano, vim, gedit) There is a workaround with the dhclient.conf file. Refer to man dhclient.conf. One can hardcode DNS nameservers in with prepend. E.g. add the following line to /etc/dhcp3/dhclient.conf: prepend domain-name-servers 192.168.60.1, 172.16.254.2; Now, no matter when dhclient gets new leases, it will first place those name servers in /etc/resolve.conf. Note, this is more of a hard-coded hack. 1. The dns server address may change, and 2. duplicate entries may result in /etc/resolve.conf. Another avenue to look at is installing resolveconf -- One DNS by DHCP setting overwrites another https://launchpad.net/bugs/59375 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59375] Re: One DNS by DHCP setting overwrites another
I couldn't reproduce the error on hardy using vpnc + resolvconf + dnsmasq(on and off). But I have wicd instead of NetworkManager, but that shouldn't affect resolvconf functionality. Everything works fine, do you have the resolv.conf managed by resolvconf? There should be a message inside the resolv.conf about it being generated,etc. If not, it was probably ovewritten by something that still doesn't play well with resolvconf. Is /etc/resolv.conf a symbolic link (as is should be, to /etc/resolvconf/run/resolv.conf) or a normal file? Q: What files are present in /etc/resolvconf/run/interfaces/ after a lease? Each file should contain a list of nameservers for each interfaces - resolvconf glues these together to create the /etc/resolvconf/run/resolv.conf. NOTE: There are restrictions: resolvconf splits the "nameserver" and "search" entries and from the nameservers it get up ti 3 entries or up to the 127.0.0.1, whichever is sooner, e.g: nameserver 127.0.0.1 nameserver 10.0.0.1 nameserver 192.168.0.1 will give: nameserver 127.0.0.1 (this is useful when you have a local DNS cacher, etc.) Hope this helps someone. -- One DNS by DHCP setting overwrites another https://bugs.launchpad.net/bugs/59375 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59375] Re: One DNS by DHCP setting overwrites another
Confirmed. We see same problem in Hardy. ** Changed in: resolvconf (Ubuntu) Status: New => Confirmed -- One DNS by DHCP setting overwrites another https://bugs.launchpad.net/bugs/59375 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59375] Re: One DNS by DHCP setting overwrites another
I couldn't reproduce the error on hardy using vpnc + resolvconf + dnsmasq(on and off). But I have wicd instead of NetworkManager, but that shouldn't affect resolvconf functionality. Everything works fine, do you have the resolv.conf managed by resolvconf? There should be a message inside the resolv.conf about it being generated,etc. If not, it was probably ovewritten by something that still doesn't play well with resolvconf. Is /etc/resolv.conf a symbolic link (as is should be, to /etc/resolvconf/run/resolv.conf) or a normal file? Q: What files are present in /etc/resolvconf/run/interfaces/ after a lease? Each file should contain a list of nameservers for each interfaces - resolvconf glues these together to create the /etc/resolvconf/run/resolv.conf. NOTE: There are restrictions: resolvconf splits the "nameserver" and "search" entries and from the nameservers it get up ti 3 entries or up to the 127.0.0.1, whichever is sooner, e.g: nameserver 127.0.0.1 nameserver 10.0.0.1 nameserver 192.168.0.1 will give: nameserver 127.0.0.1 (this is useful when you have a local DNS cacher, etc.) Hope this helps someone. -- One DNS by DHCP setting overwrites another https://bugs.launchpad.net/bugs/59375 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59375] Re: One DNS by DHCP setting overwrites another
I can confirm this issue in Ubuntu edgy server. When connecting to two separate host networks, with their own dhcp servers respectively, the newest registration overwrites the nameserver entry in /etc/resolve.conf. To demonstrate, take for example, interfaces eth0 and eth1 which connect to the two respective dhcp networks. Use the 'dhclient ' and cat /etc/resolve.conf to see how the file changes. E.g. $ cat /etc/resolv.conf search localdomain nameserver 172.16.254.2 $ $ sudo dhclient eth0 [... warning about killing previous dhclient process] Listening on LPF/eth0/00:0c:29:ba:1e:2d Sending on LPF/eth0/00:0c:29:ba:1e:2d Sending on Socket/fallback DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPACK from 192.168.60.254 bound to 192.168.60.128 -- renewal in 689 seconds. $ $ cat /etc/resolv.conf search localdomain nameserver 192.168.60.1 "nameserver 172.16.254.2" was set for eth1, but when dhcpclient renews the lease for eth0, it is overwritten by "nameserver 192.168.60.1". This can causes havoc with host lookups failing or one or the other side. You can manually append the missing nameserver to /etc/resolve.conf, but it gets overwritten as soon as a lease is renewed. E.g. $ sudo echo "nameserver 172.16.254.2" >> /etc/resolve.conf (or use a suitable text editor, i.e. nano, vim, gedit) There is a workaround with the dhclient.conf file. Refer to man dhclient.conf. One can hardcode DNS nameservers in with prepend. E.g. add the following line to /etc/dhcp3/dhclient.conf: prepend domain-name-servers 192.168.60.1, 172.16.254.2; Now, no matter when dhclient gets new leases, it will first place those name servers in /etc/resolve.conf. Note, this is more of a hard-coded hack. 1. The dns server address may change, and 2. duplicate entries may result in /etc/resolve.conf. Another avenue to look at is installing resolveconf -- One DNS by DHCP setting overwrites another https://launchpad.net/bugs/59375 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59375] Re: One DNS by DHCP setting overwrites another
Confirmed. We see same problem in Hardy. ** Changed in: resolvconf (Ubuntu) Status: New => Confirmed -- One DNS by DHCP setting overwrites another https://bugs.launchpad.net/bugs/59375 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59375] Re: One DNS by DHCP setting overwrites another
** Changed in: Ubuntu Sourcepackagename: None => resolvconf -- One DNS by DHCP setting overwrites another https://launchpad.net/bugs/59375 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59375] Re: One DNS by DHCP setting overwrites another
Confirmed. We see same problem in Hardy. ** Changed in: resolvconf (Ubuntu) Status: New => Confirmed -- One DNS by DHCP setting overwrites another https://bugs.launchpad.net/bugs/59375 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59375] Re: One DNS by DHCP setting overwrites another
** Changed in: Ubuntu Sourcepackagename: None => resolvconf -- One DNS by DHCP setting overwrites another https://launchpad.net/bugs/59375 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59375] Re: One DNS by DHCP setting overwrites another
I couldn't reproduce the error on hardy using vpnc + resolvconf + dnsmasq(on and off). But I have wicd instead of NetworkManager, but that shouldn't affect resolvconf functionality. Everything works fine, do you have the resolv.conf managed by resolvconf? There should be a message inside the resolv.conf about it being generated,etc. If not, it was probably ovewritten by something that still doesn't play well with resolvconf. Is /etc/resolv.conf a symbolic link (as is should be, to /etc/resolvconf/run/resolv.conf) or a normal file? Q: What files are present in /etc/resolvconf/run/interfaces/ after a lease? Each file should contain a list of nameservers for each interfaces - resolvconf glues these together to create the /etc/resolvconf/run/resolv.conf. NOTE: There are restrictions: resolvconf splits the "nameserver" and "search" entries and from the nameservers it get up ti 3 entries or up to the 127.0.0.1, whichever is sooner, e.g: nameserver 127.0.0.1 nameserver 10.0.0.1 nameserver 192.168.0.1 will give: nameserver 127.0.0.1 (this is useful when you have a local DNS cacher, etc.) Hope this helps someone. -- One DNS by DHCP setting overwrites another https://bugs.launchpad.net/bugs/59375 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59375] Re: One DNS by DHCP setting overwrites another
** Changed in: Ubuntu Sourcepackagename: None => resolvconf -- One DNS by DHCP setting overwrites another https://launchpad.net/bugs/59375 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59375] Re: One DNS by DHCP setting overwrites another
I can confirm this issue in Ubuntu edgy server. When connecting to two separate host networks, with their own dhcp servers respectively, the newest registration overwrites the nameserver entry in /etc/resolve.conf. To demonstrate, take for example, interfaces eth0 and eth1 which connect to the two respective dhcp networks. Use the 'dhclient ' and cat /etc/resolve.conf to see how the file changes. E.g. $ cat /etc/resolv.conf search localdomain nameserver 172.16.254.2 $ $ sudo dhclient eth0 [... warning about killing previous dhclient process] Listening on LPF/eth0/00:0c:29:ba:1e:2d Sending on LPF/eth0/00:0c:29:ba:1e:2d Sending on Socket/fallback DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPACK from 192.168.60.254 bound to 192.168.60.128 -- renewal in 689 seconds. $ $ cat /etc/resolv.conf search localdomain nameserver 192.168.60.1 "nameserver 172.16.254.2" was set for eth1, but when dhcpclient renews the lease for eth0, it is overwritten by "nameserver 192.168.60.1". This can causes havoc with host lookups failing or one or the other side. You can manually append the missing nameserver to /etc/resolve.conf, but it gets overwritten as soon as a lease is renewed. E.g. $ sudo echo "nameserver 172.16.254.2" >> /etc/resolve.conf (or use a suitable text editor, i.e. nano, vim, gedit) There is a workaround with the dhclient.conf file. Refer to man dhclient.conf. One can hardcode DNS nameservers in with prepend. E.g. add the following line to /etc/dhcp3/dhclient.conf: prepend domain-name-servers 192.168.60.1, 172.16.254.2; Now, no matter when dhclient gets new leases, it will first place those name servers in /etc/resolve.conf. Note, this is more of a hard-coded hack. 1. The dns server address may change, and 2. duplicate entries may result in /etc/resolve.conf. Another avenue to look at is installing resolveconf -- One DNS by DHCP setting overwrites another https://launchpad.net/bugs/59375 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59375] Re: One DNS by DHCP setting overwrites another
Confirmed. We see same problem in Hardy. ** Changed in: resolvconf (Ubuntu) Status: New => Confirmed -- One DNS by DHCP setting overwrites another https://bugs.launchpad.net/bugs/59375 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59375] Re: One DNS by DHCP setting overwrites another
I couldn't reproduce the error on hardy using vpnc + resolvconf + dnsmasq(on and off). But I have wicd instead of NetworkManager, but that shouldn't affect resolvconf functionality. Everything works fine, do you have the resolv.conf managed by resolvconf? There should be a message inside the resolv.conf about it being generated,etc. If not, it was probably ovewritten by something that still doesn't play well with resolvconf. Is /etc/resolv.conf a symbolic link (as is should be, to /etc/resolvconf/run/resolv.conf) or a normal file? Q: What files are present in /etc/resolvconf/run/interfaces/ after a lease? Each file should contain a list of nameservers for each interfaces - resolvconf glues these together to create the /etc/resolvconf/run/resolv.conf. NOTE: There are restrictions: resolvconf splits the "nameserver" and "search" entries and from the nameservers it get up ti 3 entries or up to the 127.0.0.1, whichever is sooner, e.g: nameserver 127.0.0.1 nameserver 10.0.0.1 nameserver 192.168.0.1 will give: nameserver 127.0.0.1 (this is useful when you have a local DNS cacher, etc.) Hope this helps someone. -- One DNS by DHCP setting overwrites another https://bugs.launchpad.net/bugs/59375 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59375] Re: One DNS by DHCP setting overwrites another
I can confirm this issue in Ubuntu edgy server. When connecting to two separate host networks, with their own dhcp servers respectively, the newest registration overwrites the nameserver entry in /etc/resolve.conf. To demonstrate, take for example, interfaces eth0 and eth1 which connect to the two respective dhcp networks. Use the 'dhclient ' and cat /etc/resolve.conf to see how the file changes. E.g. $ cat /etc/resolv.conf search localdomain nameserver 172.16.254.2 $ $ sudo dhclient eth0 [... warning about killing previous dhclient process] Listening on LPF/eth0/00:0c:29:ba:1e:2d Sending on LPF/eth0/00:0c:29:ba:1e:2d Sending on Socket/fallback DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPACK from 192.168.60.254 bound to 192.168.60.128 -- renewal in 689 seconds. $ $ cat /etc/resolv.conf search localdomain nameserver 192.168.60.1 "nameserver 172.16.254.2" was set for eth1, but when dhcpclient renews the lease for eth0, it is overwritten by "nameserver 192.168.60.1". This can causes havoc with host lookups failing or one or the other side. You can manually append the missing nameserver to /etc/resolve.conf, but it gets overwritten as soon as a lease is renewed. E.g. $ sudo echo "nameserver 172.16.254.2" >> /etc/resolve.conf (or use a suitable text editor, i.e. nano, vim, gedit) There is a workaround with the dhclient.conf file. Refer to man dhclient.conf. One can hardcode DNS nameservers in with prepend. E.g. add the following line to /etc/dhcp3/dhclient.conf: prepend domain-name-servers 192.168.60.1, 172.16.254.2; Now, no matter when dhclient gets new leases, it will first place those name servers in /etc/resolve.conf. Note, this is more of a hard-coded hack. 1. The dns server address may change, and 2. duplicate entries may result in /etc/resolve.conf. Another avenue to look at is installing resolveconf -- One DNS by DHCP setting overwrites another https://launchpad.net/bugs/59375 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
