L
LastYJ
Is there any way to back up DNS information in Windows Server 2003
Standard?
I have a total of three Win 2003 Domain Controllers which are DNS servers
as well. Two in Toronto, one in Calgary.
Last evening, the two that are in Toronto lost all of their zones under
both the Forward and Reverse Lookup Zones.
I found out the problems when users who are on shift were kicked out of
Outlook and some were not able to login to the domain.
The first thing I did was TermServ into the Exchange 2003 server. For
something that normally takes 30 seconds, it took well over five mintues.
I then suspect it was a DNS problem.
So, I tried to TermServ into the DC's and as suspected, both the Forward
Lookup Zone and the Reverse Lookup Zone were empty, as if the DNS server
was never configured.
I looked in the event logs and these are some of the errors:
The DNS server received indication that zone zoo.domain-removed.com was
deleted from the Active Directory. Since this zone was an Active Directory
integrated zone, it has been deleted from the DNS server.
The DNS server received indication that zone 34.20.10.in-addr.arpa was
deleted from the Active Directory. Since this zone was an Active Directory
integrated zone, it has been deleted from the DNS server.
The DNS server received indication that zone 36.20.10.in-addr.arpa was
deleted from the Active Directory. Since this zone was an Active Directory
integrated zone, it has been deleted from the DNS server.
The DNS server has encountered numerous run-time events. To determine the
initial cause of these run-time events, examine the DNS server event log
entries that precede this event. To prevent the DNS server from filling the
event log too quickly, subsequent events with Event IDs higher than 3000
will be suppressed until events are no longer being generated at a high
rate.
I have no idea as to why it would think the zone was deleted from the AD.
Nobody was doing anything at that time. I called Microsoft Support, spent
$350 and over three hours being cut off, and transferred to five different
people explaining the situation over and over and over and over again, with
bad phone lines and bad accents (I don't mean to offend anyone) and didn't
get an answer or resolution.
Luckily, the DNS info were not replicated to Calgary and I was able to re-
create the zones on both Toronto DC's as secondary and copy the information
from the Calgary DNS server. I then changed one of the Toronto DC's from
seconday back to AD-integrated and all seems to be well.
So, my question is, will taking a System State snapshot for the AD-
integrated DNS server help me in backing up the DNS information and how
would I prevent this from ever happening again? Luckily it was not during
the day, and even though we have staff 24/7, it didn't cause too much
inconvenience.
Sorry for the long post and I hope someone has an idea as to what the hell
happened. Thank you.
Chris.
Standard?
I have a total of three Win 2003 Domain Controllers which are DNS servers
as well. Two in Toronto, one in Calgary.
Last evening, the two that are in Toronto lost all of their zones under
both the Forward and Reverse Lookup Zones.
I found out the problems when users who are on shift were kicked out of
Outlook and some were not able to login to the domain.
The first thing I did was TermServ into the Exchange 2003 server. For
something that normally takes 30 seconds, it took well over five mintues.
I then suspect it was a DNS problem.
So, I tried to TermServ into the DC's and as suspected, both the Forward
Lookup Zone and the Reverse Lookup Zone were empty, as if the DNS server
was never configured.
I looked in the event logs and these are some of the errors:
The DNS server received indication that zone zoo.domain-removed.com was
deleted from the Active Directory. Since this zone was an Active Directory
integrated zone, it has been deleted from the DNS server.
The DNS server received indication that zone 34.20.10.in-addr.arpa was
deleted from the Active Directory. Since this zone was an Active Directory
integrated zone, it has been deleted from the DNS server.
The DNS server received indication that zone 36.20.10.in-addr.arpa was
deleted from the Active Directory. Since this zone was an Active Directory
integrated zone, it has been deleted from the DNS server.
The DNS server has encountered numerous run-time events. To determine the
initial cause of these run-time events, examine the DNS server event log
entries that precede this event. To prevent the DNS server from filling the
event log too quickly, subsequent events with Event IDs higher than 3000
will be suppressed until events are no longer being generated at a high
rate.
I have no idea as to why it would think the zone was deleted from the AD.
Nobody was doing anything at that time. I called Microsoft Support, spent
$350 and over three hours being cut off, and transferred to five different
people explaining the situation over and over and over and over again, with
bad phone lines and bad accents (I don't mean to offend anyone) and didn't
get an answer or resolution.
Luckily, the DNS info were not replicated to Calgary and I was able to re-
create the zones on both Toronto DC's as secondary and copy the information
from the Calgary DNS server. I then changed one of the Toronto DC's from
seconday back to AD-integrated and all seems to be well.
So, my question is, will taking a System State snapshot for the AD-
integrated DNS server help me in backing up the DNS information and how
would I prevent this from ever happening again? Luckily it was not during
the day, and even though we have staff 24/7, it didn't cause too much
inconvenience.
Sorry for the long post and I hope someone has an idea as to what the hell
happened. Thank you.
Chris.