• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

having problems with AD server

Z

zerocool1

Diamond Member
Ok our server is running windows 2k server and we're having this problem where it decides to give us the middle finger. Ever 2 hours or so its giving an error in event viewer that 'Dynamic registration or deregistration of one or more DNS records failed because no DNS servers are available.' Until now we've just been restarted the router, which seems to help, but eventually this problem happens again. Any ideas?


Thanks


Amit
 
Is it the only domain controller on your network? If so have you made any changes to it recently? A DC will usually have the DNS pointed to itself. So if you have no other DC's on the network hosting DNS I would check the DNS on that machine and verify that it is funtioning correctly. A failed DNS will usually bring you AD domain down to a crawl.

John
 
to my knowledge, there have been no recent changes.Yea, its the only domain controller. question tho, is there something on Linux similar to AD? Just curious.
 
What is your server used for...a file server? Check the DNS logs and see what the errors are. Also have you re-booted the AD Server?

John
 
not for a while to my knowledge, I'm not the only one that has admin privs and I haven't talked to the other admin about this for a while.
 
Well either you can re-boot the machine or first try to stop and re-start the DNS service on the Server. That would be the first place to start. I have had my DC's DNS fail a number of times...though the server still runs OK.

John
 
the other admin just restarted the dns process, we'll see how that works out

Edit: he also pointed DC machine to itself.
 
Was it pointed to the router before? That will cause that problem.

Primary DNS should be itself and alternate should be blank. Configure a forwarder in DNS to the router or the ISP.
 
The DNS needs to be running on there or on anoter BOX. DNS and DHCP shoudl be on the same box. All 3 can be on the DC this is the typical way.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top