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

2 Exchange servers on same subnet going though 1 firewall interface - Split DNS?

I read a posting of a problem which I am also experiencing but I don't quite understand the solution  I was hoping someone could clarify it for me.

subnet 172.20.10.0
Gateway 172.20.10.1

Exchange server 172.20.10.100 domainone.local

Exchange server 172.20.10.101 domaintwo.local

Both handling internal DNS for themselves.

I am getting the error:  unable to bind to the destination server in dns.

Could someone detail for me exactly how the solution was resolved in the previous PAQ.

http://www.experts-exchange.com/Networking/Email_Groupware/Exchange_Server/Q_21093840.html
0
kapara
Asked:
kapara
  • 3
  • 2
1 Solution
 
SembeeCommented:
Split DNS.

http://www.amset.info/netadmin/split-dns.asp

You basically create a dnszone for the other domain.
In this case, as you have two domains on the same subnet, you could create all the information for a domain on the same DNS server, then allow zone transfers. On the other domain, configure a new secondary zone and point it at the server that holds the information. Only need to maintain one set of data then - rather than two copies of the DNS zone.

Simon.
0
 
kaparaAuthor Commented:
Are you talking about creating a primary for the external names for the server internally?

Existing Zone:  Active Directory Integrated:   Ex. exchange.mydomain.local 192.168.1.50


Do you need me to create the following:

Primary Zone:  mail.externalname.com 192.168.1.50

Thanks


 
0
 
SembeeCommented:
You need to create a primary zone of externalname.com
Then put the MX records, hosts etc in to that zone. As you are creating a zone for that domain, it will also have to include any external hosts - web sites, ftp sites etc.

Simon.
0
 
kaparaAuthor Commented:
But I will point the External names to internal IP's.  Correct?

Thanks
0
 
SembeeCommented:
Yes.
So that when any machine inside the network does a DNS lookup it gets the internal IP address...

mail.domain.com inside 192.168.1.11
mail.domain.com outside 62.72.82.92

Simon.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

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