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 attempting to setup split horizon dns for a small business (Windows 2003 SBS). The network internally uses a .local domain. Now I've setup a zone for the extern domain, but am having troubles getting the results I (think) I want.

The problem is that the SOA field for the new zone keeps resetting to the internalserver.domain.local, even though I want it to be internalserver.domain.local is the name of the DC/DNS server. This leads to trouble when I run a diagnostic software from outside the network, since it cannot resolve the .local adress.

Also, if I do dig host.domain.local I can get the information from the internal network, which I clearly do not want. How can this be prevented?

share|improve this question
up vote 0 down vote accepted

I think your life would be easier if you had your ISP or another hosted DNS provider host the public version of the zone.

share|improve this answer
We've been having dyndns doing dns for us the last five years (set up before I started at the company). However, times are as they are, and if we could do dns ourselves we'd save money. – carlpett Nov 24 '10 at 7:46
I hear ya - but you can get premium DNS hosting for less then $5 a month through someone like Also, most registrars include DNS hosting with your registration - have you explored that route? – CurtM Nov 24 '10 at 7:58
The registrar doesn't provide that service, however I can change registrar without cost... I'll look into wether this would be cheaper than the current option! – carlpett Nov 24 '10 at 8:42
That's the route we went down in the end. – carlpett Feb 15 '11 at 11:30

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.