• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 514
  • Last Modified:

Split Brain DNS

I have a lync 2013 fe server running correctly internally on domain xserver10.local with other domains Xserver10.com, and xserverb.com.  

I have the edge server built and running but it appears that the split brain DNS is the issue connecting externally.  What entries do I need to make for xserverb.com and xserver10.com to allow it to connect to .local domain?
0
brandywine
Asked:
brandywine
1 Solution
 
giltjrCommented:
Can you give us more info on what the problem is?

Split brain DNS is when you have a DNS sever resolve the same FQDN, say like "host.public.domain" for internal networks and the Internet.  The splint brain DNS will use the internal network address for requests coming from the internal network and the public address when resolving names from the Internet.

You are showing you have multiple domain names, which should have nothing to do with split brain DNS.
0
 
brandywineAuthor Commented:
I actually formatted and just started over.  The issue was with the communicator connecting from external (internal worked fine).   I believe it was DNS related and know that Lync 2013 is different the Lync 2010 and need to be pointed in the right direction of which DNS records I need internally and externally with the above type scenario
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now