Ptr records not updating
Note: DHCP failover does not support for BOOTP in Windows Server 2012 RTM, but DHCP failover does support BOOTP in Windows 2012 R2.
Here is a screenshot of BOOTP being disabled on the scope.
I did a bit of reading and discovered that the group should have DNS computer accounts in, if the zones are configured to only be updated securely - which they were. I am forever getting incorrect / outdated lookups when connecting to machines.
I also read that a service account should be configured to carry out the zone updates - which I have now done. Our domain's zone is configured as an AD-Integrated zone with replication to all DNS servers in the forest.
As far as I know it is OK deleting Reverse Lookup Zones more often since ADdoesn't rely on that.
Hi all, Yesterday I found almost PTR records in Reserve Lookup zone were disappeared.
DNS & DHCP is intergreted, DHCP already be configured like: - Always dynamic update DNS A and PTR records - Discard A and PTR records when lease is deleted - Dynamically update DNS A and PTR records for DHCP clients that do not request updates.
Under the SOA tab, the refresh interval is 15 minutes, retry is 10, and the expiration is 1 day. There are no DNS events in the log which suggest that something is set up wrong.Any problem deleting Reverse lookup zones more often (3 days) than deletingthe Forward Lookup Zones (14 days) ?I want to make sure that I don't end up having problems in case my domaincontrollers go down on remote sites or deleting legitimate records out of my DNS.Archived from groups: microsoft.public.win2000(More info? )In my organization folks run an application that performs reverse nslookupsand in the past my vast large of mobile clients returned lots of duplicatedrecords.
Then on my DNS settings I did: Scavenge old records=1 day I kept the "Forward Lookup Zones" as refresh interval=7 days, no-refresh=7days.
Under Windows NT, DNS was static and had to be manually altered to make changes.