Maintaining AD-Integrated Reverse Zone With No DHCP Server on Domain Controller

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



We had the DHCP server running on the domain controller, and when we did
that we saw the DNS AD-integrated reverse lookup zone automatically
maintained. Apparently the DHCP and DNS applications cooperate with each
other? As soon as we implemented a dedicated DHCP server and stopped
running DHCP on the domain controller, the AD integrated reverse lookup
zones are no longer automatically being maintained. In fact even the
domain controller IPs are not appearing in the reverse zone (I had to
manually insert them). What is the secret to getting the AD integrated
reverse zones to auto populate when the DHCP server is on a separate
computer from the domain controller?

I am really confused on other related issues. I created two AD
integrated reverse zones on two separate domain controllers for the same
domain. They don't appear to be replicating the same information to each
other. Is the reverse zone not automatically replicated by Active
Directory? What is the point of making the zone Active Directory
integrated if AD isn't going to replicate the information automatically?

I'm also confused by the option in the DNS forward lookup Properties for
each DNS object to "Automatically update reverse zone record" (or words to
that effect). This checkbox can be selected but the next time you re-enter
the Properties dialog for the same DNS object it is no longer selected.
Why? Morever, selecting the checkbox does *not* have the suggested effect
of populating the DNS reverse PTR record for the AD integrated reverse zone
in which the DNS object should be appearing. How do we get the AD
integrated reverse zone information to appear?

--
Will


.



Relevant Pages

  • Re: Error 40960
    ... Hello Shana, ... Do you have the Reverse lookup zone in DNS? ...
    (microsoft.public.windows.server.general)
  • Re: Multiple questions regarding a DNS migration to MSDNS
    ... move them to microsoft DNS. ... to my domain controller when I de-commissioned the DNS servers. ... and administer only the Canada zone. ...
    (microsoft.public.windows.server.dns)
  • RE: Broken reverse DNS lookup which I cant fix
    ... 4015 about DNS and you cannot delete a wrong reverse zone. ... Open Active Directory Users and Computers, click View, Advanced Features. ...
    (microsoft.public.windows.server.sbs)
  • Re: DNS problem during NT4 - W2003 migration
    ... rebuild the new zone on the current the current domain controller so you can ... > create on the new server using nltest. ... > during dcpromo is related to the DNS problem? ...
    (microsoft.public.windows.server.active_directory)
  • Re: Reverse DNS Forwarding between 2003 Domains
    ... The syntax for the entry in the conditional forwarding is what was getting ... '1.1.1.in-addr.arpa' (your reverse lookup zone name) in. ... about reverse dns forwards. ...
    (microsoft.public.windows.server.dns)