mark-wa
asked on
What does "Reload DNS Zone Information" mean?
Hi,
I am getting a particular error in the event log of my Exchange server. I looked it up at Eventid.net and one person said to "Reload the DNS Zone Information". I'm not sure how to do that or what that even means, but I think it may be what I need to do. Here's a little history to the problem....
I am rebuilding out Win2k Domain Controller with larger hard drives. Our offsite backup provider lent us a server to use until we got ours back up and running. This server is our main DC and also is the DNS server. So, we restored our server software and settings to their server and have been running on it just fine. We purchased the larger hard drives for our server, installed them and then restored everything back to our server. I came in this last weekend to put our server back into production. After doing so, things seemed a little flaky on the network. I couldn't browse the internet, on my Exchange server, the information store and system attendant services stopped and wouldn't restart. Yet, I could browse computers on the network by name still. I finally got the internet working and thought that DNS might be ok, but the Exchange server still couldn't start those 2 services. And things still just didn't seem right on the network. So, I shutdown our server and plugged the borrowed server back in and everything was fine again. So, I think DNS may have gotten goofed up somehow on the restore of our old server.
Also, I am getting some errors in the event log that would indicate that the network may be seeing 2 servers with the same name, but yet I don't see this as being the case when looking in DNS or in Active Directory.
Anyways thoughts? Can someone tell me how to reload the dns zone information?
Thanks.
Mark
I am getting a particular error in the event log of my Exchange server. I looked it up at Eventid.net and one person said to "Reload the DNS Zone Information". I'm not sure how to do that or what that even means, but I think it may be what I need to do. Here's a little history to the problem....
I am rebuilding out Win2k Domain Controller with larger hard drives. Our offsite backup provider lent us a server to use until we got ours back up and running. This server is our main DC and also is the DNS server. So, we restored our server software and settings to their server and have been running on it just fine. We purchased the larger hard drives for our server, installed them and then restored everything back to our server. I came in this last weekend to put our server back into production. After doing so, things seemed a little flaky on the network. I couldn't browse the internet, on my Exchange server, the information store and system attendant services stopped and wouldn't restart. Yet, I could browse computers on the network by name still. I finally got the internet working and thought that DNS might be ok, but the Exchange server still couldn't start those 2 services. And things still just didn't seem right on the network. So, I shutdown our server and plugged the borrowed server back in and everything was fine again. So, I think DNS may have gotten goofed up somehow on the restore of our old server.
Also, I am getting some errors in the event log that would indicate that the network may be seeing 2 servers with the same name, but yet I don't see this as being the case when looking in DNS or in Active Directory.
Anyways thoughts? Can someone tell me how to reload the dns zone information?
Thanks.
Mark
ASKER
So, what if this is the primary (and only) DNS zone? Thanks!
Mark
Mark
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Is there anything that I need to clear out first, or do I just uninstall DNS and reinstall it? Thanks!
Mark
Mark
you can just uninstall it and let it repopulate
ASKER
I'll give it a shot! Thanks for helping! I'll let you know what the results are. Worse case, I might have to just try doing the restore over again. I'm starting to think something may have happened the first time causing all of these issues. Thanks!
Mark
Mark
no worries, restoration can be dicey if not performed 100% correctly
reloading zone information is usally done when you have a secondary zone or replicated zone from aother server... you have to right click on the zone within DNS and select reload DNS zone info, this then refreshes the current DNS info from the "Primary" or parent zone