Hi Everyone, I have a 2003 AD DC running DNS services.I also have a 2008R2 as an additional DC also running DNS. When a computer or object is added to DNS, it only goes into Forward Lookup Zone, and does not create an associated PTR record. If you use a third-party DNS server to support Active Directory, you must perform configuration tasks manually, and doing so, you might cause common configuration errors that prevent DNS and Active Directory from working properly.The following sections describe tests that you can perform to verify that your DNS server is working properly, that the forward and reverse lookup zones are properly configured, and that DNS can support Active Directory.
Before checking anything else, check the event log for errors.Using Netflow, I could see the ip address of the offender but couldnt see the hostname of the computer/workstation that was the offender.Here is my config for DHCP on the switch -ip dhcp pool PC network 10.1.70.0 255.255.255.0 domain-name dns-server 10.1.1.1 10.1.1.2 default-router 10.1.70.1 lease 8This is an office across the street from the main building.I scoured the internet for a solution and found none, but it was mentioned somewhere that I should enable "option 81" on my EX4200 DHCP server. and does anyone know how to configure "option 81" and what is needed to be configured on the Microsoft DNS server side ?Hi Everyone, I have 3 DNS servers (win2k3) integrated into AD that their reverse DNS is not updating. Both Forward and reverse DNS was screwed up to begin with.