I want to get DNS working on my LAN, which includes some downlevel clients and a single Windows 2000 Server. I set up the namespace to reflect my registered internet domain name and made the local domain a child of the registered domain (e.g., lan.registeredname.com). Active Directory, WINS and DHCP are active and clients can browse the LAN, but the Win2K Server’s DNS doesn’t resolve names out on the internet.
The Win2K Server itself is able to browse the internet because it has a DSL router, which is performing NAT, assigned as both a gateway and a DNS server.
I have no proxy server. I expect to install Exchange 2000 on the same machine that is running Windows 2000 Server soon. Eventually, I might host a web site on my server, butright now my web site is hosted by my ISP, which also hosts the authoratative name servers associated with my registered domain name.
I don’t mind if the local DNS server gets confused when clients on the LAN try to hit portions of my registered namespace that lie outside my firewall, so long as the clients can get names resolved for the rest of the internet.
Ideally, I would like the DNS to recognize its start of authority at lan.registeredname.com, but by default it sees its start of authority at the root level. If it would just take responsibility for addresses on the LAN and pass everything else to the DSL/Ethernet router, which in turn queries my ISP’s DNS servers, it seems like everything should work fine.
The other issue Iam unsure of is how to set up replication given that I only have one DNS server and it really doesn’t control anything other than the LAN.
So to boil it down, my questions are:
1. How can I set up my DNS so that it will server Windows 2000 andWindows 9x clients on my LAN?
2. How should I configure replication so that my solo DNS server gets the information it needs but does not become a problem on the internet?
