Win2k domain root woes 1

[Sleigher]

Hi all,

I've got my own little domain at home with 2 machines.
One client one server
The server is set up with win2k, Active Directory.
I've set up ISA server so I can browse from the client (and test various scenarios regarding ISA for work)

Problem is, the DNS is set up as a root server.
I'm not sure if this is REQUIRED for AD, but it's completely screwing up my DNS resolutions for the client. The server itself can resolve everything because the dial-up connection settings send requests straight out, but if I nslookup with my server as the name server nothing resolves (obviously)

I can delegate sub-domains under . root zone pointing to my ISP's name server which works, but I really don't want to have to go and create delegated sub-domains for each and every sub domain out there! (.com, .org etc. etc.)

If I try set up the root zone as a secondary it doesn't transfer from the ISP's dns.

help?



JS

 

[GrnEyedLdy]

In your DNS console you have a '.' (root zone) which was created during installation due to the fact that no Internet presense was found. In essence, your computer made itself a root server since it couldn't contact any root servers on the Internet.

What you need to do is delete the '.' zone. Then go to the properties of your DNS server and enable Forwarding. The addresses you include on the Forwarding tab will be your ISP's DNS servers. Make sure your primary DNS on the Domain Controller is pointed at itself and that your clients primary DNS setting is also pointed at the Domain Controller.

DNS requests from the client will first be sent to the Domain Controller and if they are unable to be resolved, they will be forwarded to your ISP's DNS servers that you have listed on the Forwarders tab.

Hope this helps,

Patty

 

[Serbtastic]

You don't actually need to set up the forwarders. If you omit them, your DNS server will query root DNS servers for names it can't resolve.