I have a Windows 2003 server acting as a DHCP server (among other things). I want the clients on the internal network to resolve addresses using DNS, but the problem is that the network is sometimes connected to a different ISP. The server itself gets the ISP's DNS server using DHCP. I thought of few solutions, but couldn't get any of them to work as I want.

The first one is letting my DHCP server give the ISP's DNS server to clients. The problem is that I have to enter the DNS server manually in Windows DHCP server, so I can't make it change as the ISP changes.

The second one is making my server a DNS server, but again, I have to manually enter the DNS server of the ISP in Windows DNS server.

The third solution, which actually worked, is using RRAS (Routing and Remote Access) for DNS instead of the full Windows DNS server. The problem is that it only works if NAT is enabled and I do not want to enable Windows NAT since I'm using a different NAT program, Routix NetCom.

So, is there a DHCP or DNS server, other than the RRAS one, which can change dynamically according to the configuration of one NIC (which changes using DHCP)?

link|improve this question
Do you have a reason for actually wanting to swap your DNS servers every time you change ISP? A servicable alternative might be to use a public-access DNS server, such as Google's Public DNS (code.google.com/speed/public-dns). You may then either distribute these two DNS servers directly using DHCP, or run your own DNS server as a caching resolver forwarding to Google's servers. – Per von Zweigbergk Jan 2 at 12:07
@PervonZweigbergk : That's a good idea. And no, there is no reason to not use an external DNS server (other than me not thinking about it). My problem is fixed now, thanks. – imgx64 Jan 3 at 4:46
feedback

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown

Browse other questions tagged or ask your own question.