Right now, we’ve got one gateway router and WAN link. A new router for a second WAN link (to connect to our company intranet at main office, we’re a remote branch office) is coming tomorrow. It will be set up as a second gateway/WAN link. I’ll enter it in TCP/IP properties as a second gateway on all the PCs and servers here. Our local network is all MS, NT servers and Win9x clients.
Right now the two DNS servers we have configured on all servers/clients are located at the other end of our existing WAN. When the new router is set up, I’ll either need to add a hosts file entry on all our computers for the new remote DNS server (only 70 clients, not too bad), or figure a way to add it to the existing DNS entries and make it work.What I’m wondering is if I were to remove the existing secondary DNS server entry to add the new DNS server (that way my primary and secondary DNS servers would be at the remote end of 2 different WAN links), would it present any problems?
Here’smy current thinking on a solution:
1. Remove current SECONDARY (leave PRIMARY as is) DNS server address in TCP/IP properties on all PCs here, replace it with new one from new remote site.
2. When clients here enter URL for new remote intranet site, the system will first go to the primary (existing router)gateway and primary DNS server to try to resolve. That will fail.
3. Search for secondary DNS server will fail because it’s not there through old existing gateway.
4. Client will then inquire through second, new gateway and successfully find secondary DNS server.
5. Resolution will occur and connection successful.
Am I thinking right, or what can anyone suggest?
My record shows that I diligently award my points for correct solutions. I can test solutions early next week. Thanks, all.