**SOLVED I'm a dork **
It was a type-o in my config never mind =) See I was loosing my mind.
Hey All,
Might be loosing my mind I think! Anyway it's odd and I have never ran across this before. This is a Ubuntu 10.04 LTS server just running Samba,Bind,and DHCP latest packages.
I have DHCP and DNS dynamically updating my DNS when a client grabs a lease from the DHCP server, as we can see form the syslog bellow.
Code:
named[21611]: client 10.10.10.120#52989: signer "rndc-key" approved
named[21611]: client 10.10.10.120#52989: updating zone 'newco.phx/IN': adding an RR at 'NXadmim-PC.newco.phx' A
named[21611]: client 10.10.10.120#52989: updating zone 'newco.phx/IN': adding an RR at 'NXadmim-PC.newco.phx' TXT
dhcpd: Added new forward map from NXadmim-PC.newco.phx to 10.10.10.170
named[21611]: client 10.10.10.120#46168: signer "rndc-key" approved
named[21611]: client 10.10.10.120#46168: updating zone '10.10.10.in-addr.arpa/IN': deleting rrset at '170.10.10.10.in-addr.arpa' PTR
named[21611]: client 10.10.10.120#46168: updating zone '10.10.10.in-addr.arpa/IN': adding an RR at '170.10.10.10.in-addr.arpa' PTR
dhcpd: added reverse map from 170.10.10.10.in-addr.arpa. to NXadmim-PC.newco.phx
dhcpd: DHCPREQUEST for 10.10.10.170 (10.10.10.120) from 00:23:5a:35:08:25 (NXadmim-PC) via eth0
dhcpd: DHCPACK on 10.10.10.170 to 00:23:5a:35:08:25 (NXadmim-PC) via eth0
named[21611]: zone newco.phx/IN: sending notifies (serial 2000111390)
named[21611]: zone 10.10.10.in-addr.arpa/IN: sending notifies (serial 2000107279)
The strange part is when I do a nslookup on the domain that was added in by the DHCP server in all lower case, it says "server can't find nxadmin-pc". BUT if I put NXadmim-PC and preserve the case which was reported to the DHCP server (NXadmim-PC is a Windows Vista Client) the server is able to resolve it? WTF? Anybody have an idea? I'm at a loss.
Cheers,
Styles
