Windows reverse dns not updating
I was able to manually create the A record, but still that has me concerned a little. Also if I point so my second DNS box, even though the DNS record table looks updated, it issues out my old IPs. Is this new subnet that you have created accessing the same DNS server?
Very odd, I think I need to decommission that box soon. Also, does this DNS server handle your external DNS or just your internal alone?
Check the command line set command for logonserver: set logonserver ....ensure this is set to a replciated DC -- or use NLTest and Net Diag for definitive tests.
(But this latter is usually overkill.) After I had proven authentication then I might consider (with permission from management etc) using the Network Monitor or something similar on the DHCP server to capture all of the DHCP and registration traffic. Com (phone on web site) Hi, I'm having the same problem, Windows Clients are registering but nothing else.
DHCP also, registers in the DNS servers in TCP/IP properties of the machine it is running on.
Your upstream provider need to delegate the reverse DNS lookup zone to your DNS servers.
I will forward your tips to our system administrators and hope they NOW are able to solve our problem... Kind regards, Tobias Olofsson ONLY if you don't use "Update Credentials" (a regulary user account with non-expiring password).
Update Credentials are set to the same account on all (competing) DHCP servers so that the secure updates will not conflict.
Especially when you do it over a month after the last post.
Am I missing a something that would be stopping this from populating? When I get a change to dig around on my servers today, I will give you an update.
I have a couple of ideas but I want to look cross check a few things so I don't lead you down the wrong path. Make sure it's authorized to update the DNS entries, if it's not your DC that's also doing the DHCP server work.
Oh and be sure to restart the DNS service on your DCs to make sure it reloads itself properly and starts populating the addresses.
Interesting, not only am I missing the reverse zones (unless I manually create something in a forward zone and create the associated PTR record) but I am also missing my exchange records, even the A record in the forward zone.