Hello...

We have two Windows 2000 SP4 domain controllers, and we are currently having
a problem with the PDC. If for some reason we have to restart it, the reverse
lookup zone file is not reloaded. No events are logged. The file can be
loaded manually by clicking on the "Add a new Zone" link, and following the
wizard until the point where you are given the option of "use existing zone
file". All the ptr records are retained, and all that remains is to turn on
dynamic updates, and DNS then works perfectly. Both forward and reverse zones
are configured as standard primary.

Has anyone experienced anything similar to this? I've seached the Microsoft
Knowledgebase, and this group, and not found anything. Also, our identically
configured BDC does not have the same problem.

Thanks very much for your .

Chris Johnson

Hi
Sounds conflict!!!
If you restart the DNSservice what happens?
You can also configure the DNSserver to log all events in the server
properties, or enable debug inf.

--
I hope that the information above s you
Good Luck

Jorge Silva
MCSA
Systems Administrator

"Chris J" <ChrisJ@discussions.microsoft.com> wrote in message
news:12458144-8FF9-4B45-B84C-53905A07DCA9@microsoft.com...
> Hello...
>
> We have two Windows 2000 SP4 domain controllers, and we are currently
> having
> a problem with the PDC. If for some reason we have to restart it, the
> reverse
> lookup zone file is not reloaded. No events are logged. The file can be
> loaded manually by clicking on the "Add a new Zone" link, and following
> the
> wizard until the point where you are given the option of "use existing
> zone
> file". All the ptr records are retained, and all that remains is to turn
> on
> dynamic updates, and DNS then works perfectly. Both forward and reverse
> zones
> are configured as standard primary.
>
> Has anyone experienced anything similar to this? I've seached the
> Microsoft
> Knowledgebase, and this group, and not found anything. Also, our
> identically
> configured BDC does not have the same problem.
>
> Thanks very much for your .
>
> Chris Johnson
>
>

Thanks for your ...

I tried restarting the service, and the same thing happened.

I then discovered the following setting for the DNS server, in the Advanced
Tab:

Load Zone Data on Startup: From Active Directory and Registry

I've changed this to: From File, and it works perfectly.

Thanks again.

Chris.

Great!!! But did you actually solved?
Is your DNS zone AD Integrated or did you created a Primary Zone (from
File)?
You see if you have AD integrated Zone the replications will fail because
you already have a Primary Zone in place, so you need to remove that primary
zone (assuming that you have AD integrated) and delete it from
System32\DNS\zonename.dns and wait for replication (do this only if your
zone is a Primary Zone and only if your're in AD Integrated scenario,
otherwise don't delete the AD integrated zone because it will remove from
all servers).


--
I hope that the information above s you
Good Luck

Jorge Silva
MCSA
Systems Administrator

"Chris J" <ChrisJ@discussions.microsoft.com> wrote in message
news:78F0C70C-BFA7-44C0-828A-98B315BD5734@microsoft.com...
> Thanks for your ...
>
> I tried restarting the service, and the same thing happened.
>
> I then discovered the following setting for the DNS server, in the
> Advanced
> Tab:
>
> Load Zone Data on Startup: From Active Directory and Registry
>
> I've changed this to: From File, and it works perfectly.
>
> Thanks again.
>
> Chris.