[Bug 404663] New: DHCP does not update DNS when configured to do so in Yast on x86_64
https://bugzilla.novell.com/show_bug.cgi?id=404663 Summary: DHCP does not update DNS when configured to do so in Yast on x86_64 Product: openSUSE 11.0 Version: Final Platform: x86-64 OS/Version: openSUSE 11.0 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: drankinatty@suddenlinkmail.com QAContact: qa@suse.de Found By: --- Devs, 11.0 doesn't update dns when using either dhcpcd or dhclient. This occurs over both wired (dhcpcd) and wireless (dhclient) connections. Yast is configured with "[x] Update DNS data via DHCP", just as it aways is by default. Both wired and wireless connect fine and receive address, gateway, wins and dns info just fine. The problem is that the client does not update DNS with its hostname to allow it to be found on the network. Example: 11.0 x86_64 laptop connecting wirelessly. Jun 25 22:08:46 acrp205d rcnetwork: Starting the NetworkManager Jun 25 22:08:50 acrp205d kernel: r8169: eth0: link down Jun 25 22:08:50 acrp205d kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready Jun 25 22:08:52 acrp205d avahi-daemon[2350]: Registering new address record for fe80::21b:9eff:fea9:382d on ath0.*. Jun 25 22:09:01 acrp205d kernel: ath0: no IPv6 routers present Jun 25 22:15:33 acrp205d dhclient: Internet Systems Consortium DHCP Client V3.0.6 Jun 25 22:15:33 acrp205d dhclient: Copyright 2004-2007 Internet Systems Consortium. Jun 25 22:15:33 acrp205d dhclient: All rights reserved. Jun 25 22:15:33 acrp205d dhclient: For info, please visit http://www.isc.org/sw/dhcp/ Jun 25 22:15:33 acrp205d dhclient: Jun 25 22:15:33 acrp205d dhclient: wifi0: unknown hardware address type 801 Jun 25 22:15:33 acrp205d dhclient: wifi0: unknown hardware address type 801 Jun 25 22:15:33 acrp205d dhclient: Listening on LPF/ath0/00:1b:9e:a9:38:2d Jun 25 22:15:33 acrp205d dhclient: Sending on LPF/ath0/00:1b:9e:a9:38:2d Jun 25 22:15:33 acrp205d dhclient: Sending on Socket/fallback Jun 25 22:15:33 acrp205d dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 5 Jun 25 22:15:34 acrp205d dhclient: DHCPOFFER from 192.168.6.17 Jun 25 22:15:38 acrp205d dhclient: DHCPREQUEST on ath0 to 255.255.255.255 port 67 Jun 25 22:15:38 acrp205d dhclient: DHCPACK from 192.168.6.17 Jun 25 22:15:38 acrp205d avahi-daemon[2350]: Joining mDNS multicast group on interface ath0.IPv4 with address 192.168.6.135 . Jun 25 22:15:38 acrp205d avahi-daemon[2350]: New relevant interface ath0.IPv4 for mDNS. Jun 25 22:15:38 acrp205d avahi-daemon[2350]: Registering new address record for 192.168.6.135 on ath0.IPv4. Jun 25 22:15:38 acrp205d dhclient: bound to 192.168.6.135 -- renewal in 1408 seconds. Jun 25 22:15:39 acrp205d nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1. Jun 25 22:15:39 acrp205d SuSEfirewall2: SuSEfirewall2 not active Jun 25 22:15:39 acrp205d nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/netcontrol_global_hooks' exited wit h error status 1. Jun 25 22:15:39 acrp205d nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/nfs' exited with error status 2. After connect, the server DNS (bind 9.4.1 openSuSE 10.3 x86_64) is not updated with the client information. All other machines (10.3, xp, and god forbid vista) all work OK. Here is the DNS zone after connect by "acrp205d": $ORIGIN . $TTL 172800 ; 2 days 3111skyline.com IN SOA nirvana.3111skyline.com. root.nirvana.3111skyline.com. ( 2008030946 ; serial 86400 ; refresh (1 day) 7200 ; retry (2 hours) 3600000 ; expire (5 weeks 6 days 16 hours) 172800 ; minimum (2 days) ) NS nirvana.3111skyline.com. NS nemesis.3111skyline.com. MX 10 nirvana.3111skyline.com. MX 20 nemesis.3111skyline.com. $ORIGIN 3111skyline.com. $TTL 10800 ; 3 hours alchemy A 192.168.6.102 $TTL 172800 ; 2 days ftp CNAME nirvana gw A 192.168.6.13 $TTL 14400 ; 4 hours kidsdell A 192.168.6.150 TXT "31187155d49801422fdafba6e674914fe6" $TTL 172800 ; 2 days lakehouse A 192.168.6.20 localhost A 127.0.0.1 mail CNAME nirvana nemesis A 192.168.6.16 nirvana A 192.168.6.17 $TTL 10800 ; 3 hours Rankin-P35a A 192.168.6.101 $TTL 86400 ; 1 day ripper A 192.168.6.149 TXT "313c41f262462bc25dedc4fa3bb99bc318" $TTL 172800 ; 2 days trinity A 192.168.6.18 www CNAME nirvana zion A 192.168.6.19 Reverse zone is likewise not updated. This may apply equally to 11.0 i386 as well, but I haven't tested. Let me know what else I can send you and I'll be happy to do so. Not knowing more, it looks like a problem with "nm-dispatcher." -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=404663 User rvojcik@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=404663#c1 Robert Vojcik <rvojcik@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rvojcik@novell.com Status|NEW |NEEDINFO Info Provider| |drankinatty@suddenlinkmail.com --- Comment #1 from Robert Vojcik <rvojcik@novell.com> 2008-07-08 10:38:39 MDT --- hello, hmm I am not sure if I realy understand your problem but I think this is not a bug. DHCP client update only ip adress and dns servers in /etc/resolv.conf where are DNS servers which you use for resolving hostnames. It doesn't update any record in bind zones informations. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=404663 User drankinatty@suddenlinkmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=404663#c2 --- Comment #2 from David Rankin <drankinatty@suddenlinkmail.com> 2008-07-09 13:00:03 MDT --- Hello Robert, Thanks for looking into this with me. I agree with your statement about /etc/resolv.conf, but disagree about your conclusion regarding whether there is a bug. The /etc/resolve.conf is: 13:44 acrp205d~> cat /etc/resolv.conf nameserver 192.168.6.17 search 3111skyline.com Specifically, since SuSE 8.0 pro, I have run servers with BIND configured to accept dynamic updates from dhcpd to update the forward and reverse zones. See: /usr/share/doc/packages/dhcp-server/DDNS-howto.txt included in the 11.0 dhcp-server documentation. <quote> Short outline of how things work together: - DHCP clients send their preferred hostname along the request - dhcpd acknowledges the lease - dhcpd contacts named, asking it to update the zone, using an HMAC-MD5 key (TSIG, short for transaction signature) for authentication - named updates the zone (and rewrites the zone files periodically) - when the lease times out or is freed, named will remove it </quote> That is what is broken for 11.0 clients, whatever you call it. For some reason in the dhcp transaction with 11.0 clients, the zone files are not updated with the client preferred hostname and IP. For the above server "nirvana" it servers roughly 4-Win XP, 3-openSuSE 10.3, 1-vista and 1-opensuse 11.0 client. Every client except the 11.0 client properly cause the BIND zones to be updated with the preferred hostname and IP. For some reason the 11.0 client will not do this. That is the bug. It doesn't matter whether the 11.0 client establishes the connection via eth0 or wirelessly with ath0, the result is the same. Let me know what else I can send. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=404663 User drankinatty@suddenlinkmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=404663#c3 David Rankin <drankinatty@suddenlinkmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|drankinatty@suddenlinkmail.com | --- Comment #3 from David Rankin <drankinatty@suddenlinkmail.com> 2008-07-09 14:20:01 MDT --- sorry, forgot to change the status... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=404663 User novell@chromanet.de added comment https://bugzilla.novell.com/show_bug.cgi?id=404663#c4 Andreas Wolf <novell@chromanet.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |novell@chromanet.de --- Comment #4 from Andreas Wolf <novell@chromanet.de> 2008-07-09 15:11:52 MDT --- I have the same problem. After upgrading a client to 11.0 DynDNS on the server (10.3) was not working any more. I found out that dhclient doesn't send the hostname during DHCPREQUEST. My DHCPD does not send a hostname to the clients (via setting a ddns-hostname) and so it has no hostname to update the zone. There is an option in Yast -> Network settings -> General -> DHCP Client -> Hostname. This option was set to AUTO, but even setting the hostname there does not help. There is a forum post related to the problem: http://forums.opensuse.org/network-internet/387180-hostname-issues.html They found a workaround by setting: send host-name "computername"; in /etc/dhclient.conf. It seems to me that the mentioned option in Yast does nothing at all. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=404663 Cyril Hrubis <chrubis@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |mzugec@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=404663 User mzugec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=404663#c5 Michal Zugec <mzugec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mzugec@novell.com |tambet@novell.com --- Comment #5 from Michal Zugec <mzugec@novell.com> 2008-07-10 03:04:48 MDT --- from log: Jun 25 22:08:46 acrp205d rcnetwork: Starting the NetworkManager .. reassigned to NetworkManager maintainer -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=404663 User rob@hasselbaum.net added comment https://bugzilla.novell.com/show_bug.cgi?id=404663#c6 Rob Hasselbaum <rob@hasselbaum.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rob@hasselbaum.net --- Comment #6 from Rob Hasselbaum <rob@hasselbaum.net> 2008-07-26 16:38:57 MDT --- Confirmed here as well with 32-bit version of openSUSE 11.0. Version 10.3 worked fine. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=404663 Federico Mena Quintero <federico@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=404663 User jaylinux52@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=404663#c7 Jay Mistry <jaylinux52@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jaylinux52@gmail.com --- Comment #7 from Jay Mistry <jaylinux52@gmail.com> 2008-08-28 11:50:22 MDT --- Hello, Not sure if my problem is related to the above bug. Am using the x86 (32-bit) version of openSUSE 11 & the following relates to that. The problem is as follows- (mentioned between the "=====" lines for sake of clarity- =============================================================================== On openSUSE 11.0 with updates (as of 27 Aug 08), the net connection using a DSL Router connected through a USB port (detected as eth1: TI NDIS USB Device, where TI = Texas Instruments) worked fine till now (installed a week ago) ; but by error I altered the connection settings to include DHCP (i.e. obtain DNS Name addresses via DHCP). Now, I cannot configure it connect using a static IP & using the DNS Servers that the ISP provides. Now, the 'Update DNS data via DHCP' box remains checked (it is greyed out, as seen in the picture) & I cannot connect to the web. The screenshot is that of the Yast Network Configuration screen with the error is here - http://lvznow.bay.livefilestore.com/y1p8roNEK4Ir1jpwshCeT66N06PsZGI5uIOHrNuo... I have a feeling that if I can get rid of the DHCP-enable option (the grayed-out button in the pict in url above), then after changing to static IP & DNS (ie I would enter them manually from provided by ISP), it would resolve the problem, since the past week, I had net access with the static IP option). Any suggestions/further steps on how to resolve this? PS: - On shutting down the system yesterday, there was a message stating the eth1 (TI NDIS USB Device) connection was not detected/changed & that I should file a bugzilla report. It scrolled out too fast for to note the exact message. - I have not added any additional hardware or made any significant system changes other checking the DHCP one (obtain IP Address & update DNS address via DHCP) by mistake; that I can't seem to reverse now. - eth0 is the inbuilt ethernet card (mcp73) of the mainboard (nvidia 610i chipset). I do not use this for networking or connecting to the net. ================================================================================ Thanks, -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=404663 User bphilips@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=404663#c8 --- Comment #8 from Brandon Philips <bphilips@novell.com> 2008-11-04 13:11:54 MST --- In 11.1 Beta3 I still need to set send host-name "computername"; in /etc/dhclient.conf. Can this be fixed by RC1? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=404663 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=404663#c9 --- Comment #9 from Tambet Ingo <tambet@novell.com> 2008-11-05 01:33:24 MST ---
In 11.1 Beta3 I still need to set send host-name "computername"; in /etc/dhclient.conf.
You can do that - go to NM's connection editor, choose the connection, click edit, go to "IPv4 Settings" tab and specify the host name in "DHCP Client ID" field. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=404663 User bphilips@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=404663#c10 --- Comment #10 from Brandon Philips <bphilips@novell.com> 2008-11-05 14:43:10 MST --- (In reply to comment #9 from Tambet Ingo)
In 11.1 Beta3 I still need to set send host-name "computername"; in /etc/dhclient.conf.
You can do that - go to NM's connection editor, choose the connection, click edit, go to "IPv4 Settings" tab and specify the host name in "DHCP Client ID" field.
No, this doesn't work. "send dhcp-client-identifier" is not the same as "send host-name". And according to the dhclient.conf that network manager generates it is sending a dhcp-client-identifier <value of DHCP Client ID box>. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=404663 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=404663#c11 --- Comment #11 from Tambet Ingo <tambet@novell.com> 2008-11-19 02:37:06 MST --- Ah right, my mistake. You can configure "send host-name" directly in /etc/dhclient.conf file (as comment #4 already suggests). NM will overrider the "send dhcp-client-identifier" from that configuration file with the value from connection editor (if set), but all the other variables are still used. What do you think of an idea of always using "send host-name" when static hostname is used? Would it produce any side effects? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=404663 User bphilips@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=404663#c12 --- Comment #12 from Brandon Philips <bphilips@novell.com> 2008-11-20 01:55:39 MST --- (In reply to comment #11 from Tambet Ingo)
What do you think of an idea of always using "send host-name" when static hostname is used? Would it produce any side effects?
I think this is reasonable. You may consider informing users that setting the hostname will cause the hostname to be advertised via DHCP. Or, just have a checkbox in the network manager to enable sending of the current /etc/HOSTNAME. Thanks, Brandon -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=404663 User rob@hasselbaum.net added comment https://bugzilla.novell.com/show_bug.cgi?id=404663#c13 --- Comment #13 from Rob Hasselbaum <rob@hasselbaum.net> 2008-11-20 11:00:33 MST --- At some point (probably following an update to 11.0), the workaround described in comment #4 stopped working for me. The send host-name directive still appears in my /etc/dhclient.conf file, but it no longer seems to have an effect. Have others noticed this? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=404663 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=404663#c14 --- Comment #14 from Tambet Ingo <tambet@novell.com> 2008-11-21 00:15:39 MST --- There hasn't been any NM updates for 11.0. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=404663 User cmaessen@casco.demon.nl added comment https://bugzilla.novell.com/show_bug.cgi?id=404663#c15 Caspar Maessen <cmaessen@casco.demon.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cmaessen@casco.demon.nl --- Comment #15 from Caspar Maessen <cmaessen@casco.demon.nl> 2008-11-22 14:39:37 MST --- (In reply to comment #13 from Rob Hasselbaum)
appears in my /etc/dhclient.conf file, but it no longer seems to have an effect. Have others noticed this?
Yes. Inspecting active processes with ksysguard, I found dhclient and its commandline: "/sbin/dhclient -d -sf /usr/lib/NetworkManager/nm-dhcp-client.action -pf /var/run/dhclient-eth0.pid -lf /var/run/dhclient-eth0.lease -cf /etc/dhclient-eth0.conf eth0" No option -H <hostname>, and I couldn't figure out where this commandline was assembled. Then I noticed that a configfile is used per interface. I created therefore a config for both my interfaces (eth0 and wlan0). This solved the problem. At least for now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=404663 User rob@hasselbaum.net added comment https://bugzilla.novell.com/show_bug.cgi?id=404663#c16 --- Comment #16 from Rob Hasselbaum <rob@hasselbaum.net> 2008-11-23 08:34:56 MST --- (In reply to comment #15 from Caspar Maessen)
Then I noticed that a configfile is used per interface. I created therefore a config for both my interfaces (eth0 and wlan0). This solved the problem. At least for now.
Ahh, thanks. Yes, I created /etc/dhclient-eth0.conf and /etc/dhclient-wlan0.conf containing only the send host-name directive and it works again. It will be nice to get this fixed for real in 11.1, though. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=404663 User bphilips@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=404663#c17 --- Comment #17 from Brandon Philips <bphilips@novell.com> 2009-03-16 18:25:15 MST --- (In reply to comment #16)
(In reply to comment #15 from Caspar Maessen)
Then I noticed that a configfile is used per interface. I created therefore a config for both my interfaces (eth0 and wlan0). This solved the problem. At least for now.
Ahh, thanks. Yes, I created /etc/dhclient-eth0.conf and /etc/dhclient-wlan0.conf containing only the send host-name directive and it works again. It will be nice to get this fixed for real in 11.1, though.
Should this become a FATE request for 11.2? Cheers, Brandon -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com