DNS "island" problem....

  • wlandymore
  • Newbie
  • Newbie
  • wlandymore
  • Posts: 14

Post 3+ Months Ago

there are a few articles about this problem that exists where you set domain controllers with their own address as the primary or alternate DNS address and kill replication because of it.
However, if you only have two domain controllers how can you create redundancy if you don't?
For example, if you have domain controller1 pointing to itself for DNS and then everything else pointing to controller1 (as they suggest), what happens if controller1 goes down?
Then controller2 will be trying to get it's DNS from controller1 and nothing will happen.
How are you supposed to keep at least one DC up for people to use if it can't use it's own address for DNS, in the event that the other one goes down???
  • DuckIT
  • Graduate
  • Graduate
  • User avatar
  • Posts: 155
  • Loc: London, UK

Post 3+ Months Ago

Not aware of this issue of replication failing but we would normally set the primary DNS server as itself only then secondary as itself for primary then the primary DNS server at its secondary. Never noticed any issue with this method!


Post Information

  • Total Posts in this topic: 2 posts
  • Users browsing this forum: No registered users and 14 guests
  • You cannot post new topics in this forum
  • You cannot reply to topics in this forum
  • You cannot edit your posts in this forum
  • You cannot delete your posts in this forum
  • You cannot post attachments in this forum

© 1998-2017. Ozzu® is a registered trademark of Unmelted, LLC.