DNS Accidently Removed - Question

[-=gu=-]

Hello,
My partner was trying to troubleshoot some DNS errors and
for whatever reason, he decided it would be prudent to
uninstall and then reinstall DNS from one our our 3 DNS
servers. (DOH!) He says that is ALL he did, says he did
NOT delete any zones.

Our DNS contained 4 Forward Lookup Zones and a Reverse
lookup zone. All zones (to my knowledge) were AD
integrated. Whatever he did, it removed all Forward
lookup zones on the other two DNS servers. Of course I
grabbed my chest and went into shock. We scrambled and I
quickly recreated an AD integraged Foward Lookup Zone on
the other 2 servers and began running a
"ipconfig /flushdns and ipconfig /registerdns" on all
servers in the infrastructure. I saw workstations
checking in and showing up as well. I also had some
documentation on our DNS, so I was able to recreate the
additional HOST and ALIAS records. When creating these
records, I could not create associated PRT records
(sorry - didn't write down the error) but later, the
Reverse Lookup Zones started working properly. Everything
seems to be working as of now but I am waiting for some
fallout.

OK, so here's my question. Under forward lookup zones on
all DNS servers there are three entries that now have
the ".old" extension on them. They are "1.10.in-
addr.arpa.old & 2.10.in-addr.arpa.old and &
rootdnsservers.old"
My event viewer is generating error messages on all DNS
servers with an Event Code 4004. I'll paste the error
below but I need to know if I should delete these Forward
Lookup Zones or not. I fear these errors will be
generated every 15 minutes for eternity if I don't.
However, I'm somewhat concerned about the
rootdnsservers.old because I know internet root dns
servers are important. Our internet connection is fine
though, and we can resolve any external URL we try. I
would appreciate your guidence and suggestions on this.
Thank you very much. -=gu=-

Here's the dns event viewer error:
The DNS server was unable to complete directory service
enumeration of zone 1.10.in-addr.arpa.old. This DNS
server is configured to use information obtained from
Active Directory for this zone and is unable to load the
zone without it. Check that the Active Directory is
functioning properly and repeat enumeration of the zone.
The event data contains the error.
(this same error comes up for 1.10.in-addr.arpa.old and
rootdnsservers.old)

 

[Kevin D. Goodknecht [MVP]]

In

Hello,
My partner was trying to troubleshoot some DNS errors and
for whatever reason, he decided it would be prudent to
uninstall and then reinstall DNS from one our our 3 DNS
servers. (DOH!) He says that is ALL he did, says he did
NOT delete any zones.

Our DNS contained 4 Forward Lookup Zones and a Reverse
lookup zone. All zones (to my knowledge) were AD
integrated. Whatever he did, it removed all Forward
lookup zones on the other two DNS servers. Of course I
grabbed my chest and went into shock. We scrambled and I
quickly recreated an AD integraged Foward Lookup Zone on
the other 2 servers and began running a
"ipconfig /flushdns and ipconfig /registerdns" on all
servers in the infrastructure. I saw workstations
checking in and showing up as well. I also had some
documentation on our DNS, so I was able to recreate the
additional HOST and ALIAS records. When creating these
records, I could not create associated PRT records
(sorry - didn't write down the error) but later, the
Reverse Lookup Zones started working properly. Everything
seems to be working as of now but I am waiting for some
fallout.

OK, so here's my question. Under forward lookup zones on
all DNS servers there are three entries that now have
the ".old" extension on them. They are "1.10.in-
addr.arpa.old & 2.10.in-addr.arpa.old and &
rootdnsservers.old"
My event viewer is generating error messages on all DNS
servers with an Event Code 4004. I'll paste the error
below but I need to know if I should delete these Forward
Lookup Zones or not. I fear these errors will be
generated every 15 minutes for eternity if I don't.
However, I'm somewhat concerned about the
rootdnsservers.old because I know internet root dns
servers are important. Our internet connection is fine
though, and we can resolve any external URL we try. I
would appreciate your guidence and suggestions on this.
Thank you very much. -=gu=-

Here's the dns event viewer error:
The DNS server was unable to complete directory service
enumeration of zone 1.10.in-addr.arpa.old. This DNS
server is configured to use information obtained from
Active Directory for this zone and is unable to load the
zone without it. Check that the Active Directory is
functioning properly and repeat enumeration of the zone.
The event data contains the error.
(this same error comes up for 1.10.in-addr.arpa.old and
rootdnsservers.old)

Did you rename these objects in ADU&C?
How did they get renamed, uninstalling DNS does not delete or change these
zones. I would suggest you read up on how to reinstall AD DNS zones. It is
really a pretty simple and straight forwaord process.
You should start by pointing the DCs to one DC that the operation will be
performed from. Change the zone from AD integrated to standard primary,
delete the objects from ADU&C, recreate the zones in the DC you are working
from, run ipconfig /flushdns, ipconfig /registerdns, restart the netlogon
service. The new zone will be replicated to all DCs with DNS installed. That
is the just of it, you can read more here.
How to Reinstall a Dynamic DNS Active Directory- Integrated Zone
http://support.microsoft.com/default.aspx?scid=kb;en-us;294328&Product=win2000

 

[Herb Martin]

My partner was trying to troubleshoot some DNS errors and

for whatever reason, he decided it would be prudent to
uninstall and then reinstall DNS from one our our 3 DNS
servers. (DOH!) He says that is ALL he did, says he did
NOT delete any zones.

Read what Kevin says (above), but consider this the other 3 DNS
servers likely hold the zone still, so just make this server a secondary
(or AD integrate if the others are set that way) and repopulated
through zone transfer.

No big deal. Unless of course "your partner" deleted the zone from
ALL servers where it was held.