Using the internal DNS server(Windows 2003 Server), can I point a single URL from a legitimate domain to a certain IP address, while leaving all other variances of that domain pointing to their existing location?
Here’s an example of what I’m looking for.
http://www.notourdomain.com/ needs to route over the internet
http://inside.notourdomain.com/ needs to be routed over an internal VPN connection
Can it be done?
6 thoughts on “Windows Server DNS question”
Of course you can – depending on the dns server, you may just be able to put the ip address in your hosts file on the server. I think this is what I did to block myspace.com – added the entries to our dns server. Alternatively just create a new dns zone for the domain – as long as forwarding is on, the rest of the traffic should get forwarded out.
It gets more difficult if you want to transfer http://www.notourdomain.com/inside leaving other subdirectories intact though…
Thanks Andy! That’s what I figured. I didn’t want to add a DNS zone for this domain as I didn’t want to break any current connectivity to it. This client spends 95% of it’s day attached to their services.
As soon as I added the zone, no one could get to any of the domains they needed to. I had to delete the zone.
I tend to think this is not possible, because as soon as you enter the dns into the windows server, your clients are going to be looking at that server to resolve ALL records for that domain. I’ve run into the problem before and never found a solution, other then relocating your dns server into a dmz outside of the internal network.
Hey did you ever figure this out?
Ended up not having to. Issue was worked around with some static routing in their Cisco.
Comments are closed.