• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Windows 2000 DNS server problem

M

mrCide

Diamond Member
First venture into this forum so excuse me if something like this has been brought up 🙂

I've got 2 workstations and a Windows2k Advanced Server box at work. I'm running AD/DNS on the server, the DNS to resolve local addresses for the network (which is working fine). I want to, however, use the same server for dialup networking for the workstations to get online. In other words, I want to be able to resolve local addresses and remote addresses (when it cannot solve local addresses) through the same DNS server. I was told to define the local zones and have the local dns server forward anything it can't answer itself to and external dns, which is okay, but it will not allow me to because it's the root server.

What do I do? It's currently setup as the 'root' domain controller.
 
First off, you have to let your DNS server know that it isnt a root server any longer. To do this, go into the forward lookup zone folder and erase the "." root forward lookup zone.
Then you need to let your DNS server know where it should go when it cannot resolve a name itself. You do this by configuring a forwarder. Right click the server in the DNS window and select properties. It's under one of the tabs there. You should put in the IP of your ISP's DNS server.

DNS is like a chain, it needs links. Forwarders create those links.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top