Dns timestamp not updating chivalrous dating

Our DHCP was set to lease addresses for 1 day, for reasons which were never explained to me.I set this back to 7 days, in an attempt to give DNS a chance to 'catch up' before the addresses potentially changed again, but we're still getting incorrect DNS entries. Our settings are now an amalgam of what went before (which didn't work) and what I've gleaned from MS documentation.Windows Server 2008's DNS engine has a nice feature that shows a timestamp for objects that are created directly by Active Directory (AD).Figure A below shows a zone with AD objects: The one unfortunate fact is that non AD-integrated records have a static timestamp.DHCP is set as follows: Enable DNS dynamic updates - always dynamically update DNS A and PTR records.

dns timestamp not updating-65dns timestamp not updating-8dns timestamp not updating-57dns timestamp not updating-84

Delete the computer account (PC1) from the Active directory compute names (of the old laptop) 2.At the same time, I'm combing through AD and rationalizing group memberships.The Dns Update Proxy group, despite its description, had a domain admin account and the BES Service Account as members.If the ping and traceroute test show your server with us in the outcome, you know the DNS is propagated. You can try speeding up the propagation time by having your TTL set to a lower number (not recommended). We set the default TTL to 14400 (4 hours); however the network that you are using to access the internet may update at a slower rate.In the course of reading Michael Kassner's post DNS: Painful Reminders of How Important It Is, I echo all his comments and want to follow up with one feature that can slightly assist in this area.

Leave a Reply