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.