Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm trying to create a static DNS entry (Windows 2003) to a server outside my network. Server is on a different subnet which does not show up as a zone on my DNS server. Would I be better off just using Windows hosts file for this since I only have one zone in my DNS?

share|improve this question
Expand on your question please. How is the subnet relevant to DNS? Is this an external server? – joeqwerty Jun 6 '12 at 21:17
Yes, it's an external server. Multiple users are using this application that points to SERVERNAME rather than the IP address. SERVERNAME doesn't resolve to as there is no DNS entry and I cannot add one in DNS because it's outside our zone of 192.168.1.x – Jagger Jun 6 '12 at 21:23

A few things:

  1. You wouldn't add a record for the server to a reverse lookup zone because you're trying to resolve the server name to an ip address. That's what forward lookup zones facilitate.

  2. Reverse lookup zones resolve ip addresses to names. That's not what you're trying to do.

  3. Whether or not the server is in your subnet or not, you can create a reverse lookup zone on your DNS server for any network/subnet you wish. You're not limited to creating reverse lookup zones only for the subnets that are actually in use in your network.

  4. You're not limited to creating forward lookup zones for domain names that are in use in your network or that belong to you or your company. You can create a forward lookup zone for any domain you wish. For example, if I set up a forward lookup zone on my DNS server for, then my server is going to be authoritative (within the scope of my network and for my DNS clients) for everything under Granted that presents some challenges for users who actually need to resolve legitimate DNS records in the domain, but there's nothing technically to stop you from doing so.

share|improve this answer

Why not just create the record in the DNS server responsible for that subnet, then make sure your DNS server can query the other DNS server?

Edit: Create a DNS A record in your DNS server that points to the IP of the server and call the A record "SERVERNAME". It will work based on what you've said above.

share|improve this answer
We only connect to this one server on that subnet... – Jagger Jun 6 '12 at 21:17

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.