DELETED the ROOT DNS "Forward Lookup"

[Jeffwmg]

I have made a big mistake. I was trying to make my Client logins faster. I went into the DNS, deleted the "." forward look up. Now I am having all kinds of problems with my DNS and Active Directory. I am running Win2K on two servers. Now, when I go into the other server, I see the "." DNS Foward Lookup. When I try to add that back to my other server, it says "Access Denided", Now, I know, and yes I have permissions for everything, It is more of a "cannot update the ROOT DNS server" problem. is there anyway to get the Root DNS server to look across at the other Server and replicate the information there????

I have already tried to unistall Active directory on both boxes. and I get errors, won't let me do this

I had figured to unistall AD and reinstall it to fix problem. I just run into more problems....

Any Help would be appreciated..... Thanks in advance.

 

[jjgraf]

without DNS Active Directory does not work try restoring from Backup.

if you don't have a backup you have two choices format and reinstall the W2K servers or try to rebuild the
DNS forward lookup.

Since chances are the DNS was AD intergrated. When you deleted it, all kinds of damage was done to the AD.

The DNS is used to lookup which servers are incharge of AD, security, LDAP, kerbose, and among other things.

In short this is not an easy fix. without DNS the DCPROM tool can not figure out which servers are in charge of what so all kinds of errors occur

I also looked on MS Knowledge base no luck

 

[dankelt]

There is no need for the "." Forward Lookup Zone. All this does is designates the server as a ROOT server, which means it will answer all queries for any domain, and if it can't anwser, it just gives up. Which is something I don't think you really want. If you are having problems with dns, I don't see how it is related to the "." zone being deleted. If fact, I would recommend you delete it on your other server(Unless you have some reason for designating these servers as ROOT DNS server).

Dan

 

[jjgraf]

just to make my self clear

By judging from the errors Jeffwmg describes i'm betting he deleted the AD domain from DNS which would cause all kinds of problems because it would flow back to the AD and that is a cricial object. Offcourse this deepends on DNS being AD intergate

Also what the above guy said is correct . is not a critical object and can be deleted but anything else can not.

Go around and check all the Primary DNS settings in Network Settings to make sure the servers point to them seleves. the GC if running DNS should have entry 127.0.0.1 or it's IP address or point the primary DNS server