DNS Record Issue
I've stumbled across a strange DNS issue at our HQ location.
C:\Users\x>nslookup adm24-keyscan
Server: our.primary.dc
Address: 192.168.6.5
*** our.primary.dc can't find adm24-keyscan: Non-existent domain
C:\Users\x>ping adm24-keyscan
Pinging ADM24-Keyscan.local [192.168.6.250] with 32 bytes of data:
Reply from 192.168.6.250: bytes=32 time<1ms TTL=128
Reply from 192.168.6.250: bytes=32 time<1ms TTL=128
Reply from 192.168.6.250: bytes=32 time<1ms TTL=128
Reply from 192.168.6.250: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.6.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
The thing is, that box is on the domain. I can login with domain credentials. It can access domain resources. I do note that, for whatever reason, the DNS entry is missing from our forward-lookup zone, but NOT missing from the reverse-lookup zone. The reverse-lookup zone keeps getting updated as expected, but the forward record is just MIA. I believe that is why I am getting these results, but I am not sure why.
Scavenging is enabled. DHCP leases are eight hours, no-refresh is four hours, and refresh is six hours. The thing is, this box is static and should not be scavenged. Not fake-static using DHCP reservations, truly static.
Also, what is up with the topic length requirements? Anything I tried was either too long or too short! Anything that fit was truncated and made no sense.