|
Hi, we have a multihomed exchange server with internal and external IP addresses. there are host records in DNS for both ip addresses. problem is, the external ip address is being served to internal clients instead of the internal address. is there a configuration that will allow only the internal ip address to be served by DNS. thanks, Deb |
|
I feel forced to make certain assumptions about your configuration in order to be able to answer your question. If I make wrong assumptions, please edit your question and elaborate on your configuration, and I will revise my answer accordingly. If this Exchange server is also acting as a routing server, and cannot be reached using its public IP, then I would suspect that you have a routing problem. To resolve such a problem, you would have to make some changes to the server's routing configuration (by the way, you didn't mention your operating system). For detailed guidance on how to configure Routing and Remote Access on Windows Server, I recommend consulting Microsoft's documentation and/or forums.
No. If it's a private IP (for an exact definition, please see Wikipedia's article on private networks), then it is not routable from the Internet, and can't be used for remote access. Hi, thanks for your prompt reply. to attempt to clarify the infrastructure: It is not a routing issue. the ip address can be pinged. and there is no remote access involved. we think we solved the problem by disabling dns round robin on both dns servers. any other suggestions appreciated. Deb
Jan 20 at 05:29 PM
user-148 (google)
|
|
It sounds like you want Split Horizon DNS - your DNS server needs to provide a different IP (the LAN IP) to requests coming from the LAN that those from outside the LAN. I don't believe you can do that with Custom DNS. You could however have all your clients use a DNS server on the LAN. On that server you create a zone with the name of your Exchange server with the LAN IP of the Exchange server. On the DNS server for the domain remove the LAN IP entry. Then any host contacting your public DNS server will get the WAN IP, any host contacting your LAN DNS server will get the LAN IP. |
Closing this as the originator hasn't been back in a month. This will stop the community bot bumping this regularly.