rubbaninja
MIS
Our company is directly connect to a partner but have seperate LANs, DNS, etc. and are seperated by a firewall.
Our company NATs our address and they NAT their address.
Both companies access each others resources.
Their dns uses one.com for resolution of our address in their private DNS.
We use two.com for everything on our network to resolve address on our LAN it is also our external domain name (two.com)
We also have one.com in our forward lookup zone to resolve their addresses.
We recently ran into an issue where some of our web apps use the FQDN or the site; xxx.two.com.
Now their people cannot connect to a lot of the web apps because they cannot resolve xxx.two.com.
They use BIND for their private DNS. Is it possible to add a forward lookup zone, two.com, in BIND to resolve our private addresses? If yes, will they be unable to resolve two.com public entries, like www, if they don't manually enter them into the two.com forward lookup zone or will BIND say "Hey, is not in this forward lookup zone, let me check the public DNS server"?
Our company NATs our address and they NAT their address.
Both companies access each others resources.
Their dns uses one.com for resolution of our address in their private DNS.
We use two.com for everything on our network to resolve address on our LAN it is also our external domain name (two.com)
We also have one.com in our forward lookup zone to resolve their addresses.
We recently ran into an issue where some of our web apps use the FQDN or the site; xxx.two.com.
Now their people cannot connect to a lot of the web apps because they cannot resolve xxx.two.com.
They use BIND for their private DNS. Is it possible to add a forward lookup zone, two.com, in BIND to resolve our private addresses? If yes, will they be unable to resolve two.com public entries, like www, if they don't manually enter them into the two.com forward lookup zone or will BIND say "Hey, is not in this forward lookup zone, let me check the public DNS server"?