Windows server 2003 DNS split domain

Win XP
Win 2k3 server
-------------------
The company that develops our software uses an external domain that they control to identify our internal servers.

server1.xyz.com   10.0.1.1

The problem is that when their internet connection fails (or our does) we can not continue to work because our servers are unable to resolve the IP address.  I can't create a forward zone on our internal DNS server only for the names that resolve to our servers because then I'm unable to reach other subdomains like www.xyz.com (which is their external web server).  and they have hundred that I don't want to update - ever.

Short of manually copying a HOSTS file to each of a couple thousand Win XP desktops (whose users do not have local admin rights anyway) is there any decent way to solve this?

Our "firewall" (Sonicwall Pro 2040) doesn't provide any DNS control at all.
midnightdataAsked:
Who is Participating?
 
oBdAConnect With a Mentor Commented:
Yes, that's possible. In your DNS, create a new zone "server1.xyz.com" (yes, the server's FQDN).
Then add a new A (host) record, leave the name field empty, and add the IP address. This will create a "Same as parent" entry which will then resolve "server1.xyz.com" to the IP address (the same way your AD domain name is resolved).
0
 
midnightdataAuthor Commented:
Painfully obvious but an excellent answer nonetheless. :)

Thank you.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.