Split DNS Configuration in BIND

Sten Carlsen stenc at s-carlsen.dk
Mon May 30 22:34:16 UTC 2011

In a number of cases NATs have a problem to access the internal boxes
via an external address from inside the NAT.

In such cases it is much easier to just access the box from inside with
it's internal address and from outside with its external address.

Using the two views allows for all sorts of scripting etc. without
having to consider whether you are on the outside or the inside. I have
used that for many years now.

On 30/05/11 21:20, Doug Barton wrote:
> On 05/29/2011 23:17, babu dheen wrote:
>> We have DNS record called "mail.company.com" which is hosted in internal
>> company LAN network. When any users try to access mail.company.com in
>> browser, they will get private IP address and immediately they will get
>> mail.company.com website home page whereas if any of my company users
>> try to access the mail.company.com website from internet(outside
>> company), they should get public IP address which should be pointed to
>> mail.company.com website.
> It's not clear to me from this description why you need 2 different IP
> addresses for the same resource.

Best regards

Sten Carlsen

No improvements come from shouting:


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20110531/21a36d7d/attachment.html>

More information about the bind-users mailing list