Link to home
Start Free TrialLog in
Avatar of syinfra
syinfraFlag for India

asked on

DNS Errors

Hello,

We have following setup

Common Domain :- xyz.lan
Sites :- 2 (Site 1 & Site 2)
Site 1 :- Domain Controller / DNS (172.25.0.20) + Member Server (172.25.0.54)
Site 2 :- 2 Member Servers / DNS (172.21.0.20 & 172.21.0.54)
Site 1 IP Network :- 172.25.0.0/22
Site 2 IP Network :-  172.21.0.0/22

We are facing following issues.
Event ID 4521, The DNS server encountered error 9002 attempting to load zone......
Event ID 1054 Windows cannot obtain the domain controller name for your computer network.....
Event ID 13508 The file replication Service is having trouble enabling replication from <old DC> to <new Dc>......
Event ID 27 While processing a TGS request for the target server krbtgt/xyz.lan, the account.....did not have a suitable key for generating a Kerberos ticket.....
Not able to create reverse lookup zone 172.21.3.x on any of the AD. It gives error The zone cannot be created. There was a server failure.

I have searched & tried to apply all the threads in Google however not able to succeed. Request help to resolve the issue.

Regards
Guru
Avatar of Rich Weissler
Rich Weissler

I'd start with "The DNS server encountered error 9002 attempting to load zone"
Because you've specified some DNS servers as member servers, I assume you are not using AD Integrated zones.  I assume there is one server that is the primary for the zone which includes your active directory objects.  I assume that's the server on which you have the error concerning not being able to load a zone.   Added to the reference to "<old DC>", I have this fear that it may be possible that the machine which had been the primary on the zone has been demoted/retired.  If the zone one which active directory relies has failed to load on the primary, and everything is counting on the primary (all the secondaries have expired references)... then all the error messages would be a symptoms of the same cause.

Unfortunately, I've had to assume a lot.  (And because so much needs to be assumed, I also assume that's why the question is currently neglected.  :-)  It's hard to guess what might be occurring here.)

To proceed... confirm which assumptions you can.  On which server was that first (failed to load) error?  Where there any other recent problems with that server?  Was the old DC retired 'recently'?
Avatar of syinfra

ASKER

Thank you Rich for your response.

The error is appearing on all the Servers (PDC & Member Servers). There was an old DC, however it is removed long time back.
If you open DNS Manager, and look at the properties if the individual forward lookup zones... are they Active Directory Integrated, Primary, or Secondary zones?
Avatar of syinfra

ASKER

They are Active Directory Integrated
ASKER CERTIFIED SOLUTION
Avatar of Rich Weissler
Rich Weissler

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial