DNS on local network vs public network 2

[dibthree]

I have two primary DNS servers.
We have our local DNS server on our local network as part of our local domain. "office.companynetwork.com"
We also have a Public DNS server with DNSMadeEasy that we use for our website and MX records.
On the Public DNS I have an A Record of IM.companydomain.com that point to our firewall’s public IP address and then gets port forwarded to an internal IP address 10.x.x.x on our local network.

When a user is on the local network I would like the local DNS server to point the record them directly to the local 10.x.x.x address instead of them hitting the public address.

The problem I am having is that when I add an A record to our local domain it is adding it as IM.office.companydomain.com instead of IM.vdicommunications.com.

Is there a way to work around this? Thanks for your help.

.

 

[lgarner]

You need to set up vdicommunications.com on your internal DNS server, then add the necessary records (

http://www,im,

etc) for it.

The Pix, and probably other firewalls, can do DNS aliasing to translate the DNS replies for you.

 

[lhuegele]

Yes, you want to set-up your external domain as a forward look-up zone on your internal DNS server as lgarner explained above. Then you can create the records for that domain with your internal IP addresses. We've been doing that here for years and years.

Good luck,

 

[elgrandeperro]

A simple forward is not the solution, because you want split DNS. For instance,

http://www is

the external public IP but internally it is the 10 net ip.

lgarner has it right, you need to become authoritative for the domain internally so it will not go to your external DNS. This requires keeping 2 DNS-s in sync, but generally the external changes are less often.

There are techniques (views in BIND) let 1 DNS server serve both internal and external records, but since your external is separate, that would be a moot point.