Discussion Locked

DNS between to VPN networks

0 helpful
12 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have 2 Forests that are VPNed together and I can ping each others IP address. So we can get to each others resources, but we can not use host names like "STIMPY" but I can ping it's IP.

I have added forwards on both networks DNS server. I have tried added a secondary zone in each DNS to the other one, but it doesn't work. Says it can't connect. But again, I can ping everything.

I need to make a trust between the two, but must have DNS setup first. What should I look at or try?

ps. The branch office DNS is on the VPN, D.C. and Firewall server and the main office DNS is on a D.C. hope that helps.

12 replies

by mark

You want one DNS to be primary and the other secondary. Don't mix.

If you are having problems with DNS, you can try using the HOSTS and/or LMHOSTS files. There are samples and explanations in the system folder. If you don't have too many PCs, you can make a master HOST file on a server and make a batch file to copy them to the other PCs or just let users know where to get it. Each PC needs it in their Windows Folder. The HOST file is a simple text file with Name, spaces or tabs, IP address. The best solution is to get the DNS working, but it's not necessarily the easiest if you are not familiar with setting it up.

by cldboone

Did you check the SRV records on each DNS server? and did you flush and register the DNS?

by chrisdent

Basically you need to be able to find names and services on the domain which is what you've tried a little. I don't think however a secondary zone is what you require.

The best way to do that is to add a stub zone file to your server. This file contains only two bits of information, the Nameservers and the Start of Authority for the domain in question.

When you make a secondary zone it also registers your own server as Start of Authority, so if the zones aren't replicating it'll just be looking at an empty zone file and saying "host doesn't exist".

This should be replicated on the other site so they can find your domain as well.

Domain Suffix Search order should dictate whether or not you can find it via just the first part of the name (rather than the FQDN).

You can use NSLookup to test the set-up as a whole.

If this isn't clear enough or doesn't work let me know.

by chrisdent

Forgot to add that the Start of Authority will be the Primary DNS server on the other site.

Using NSLookUp you should then be able to resolve the FQDNs of every host on the alternative site, your DNS server should ask the SOA / DNS for each name.

Its worth planning a DNS structure carefully to make life easier in the long run.

by chrisdent

With a little planning a DNS structure can work very effectively. How you do it depends on your current set-up and how you prefer to have it organised.

I would personally do the following:

Primary Site Master Server:

zone localdomain.local.
SOA for localdomain.local = ns1.localdomain.local

Nameservers for localdomain.local = ns1.localdomain.local

zone site1.localdomain.local.
SOA for Site1.localdomain.local = ns1.localdomain.local
Nameservers for Site1.localdomain.local = ns1.localdomain.local

ns1.site1.localdomain.local IN CNAME ns1.localdomain.local

zone site2.localdomain.local.
SOA for Site2.localdomain.local = ns1.site2.localdomain.local
Nameservers for Site2.localdomain.local = ns1.site2.localdomain.local

The reverse lookup table should also be considered:

If the local site has the range 10.0.0.0/24 and the remote site has the IP Range 10.1.0.0/24 then:

zone in-addr-arpa.0.0.10.
SOA for in-addr-arpa.0.0.10 = ns1.localdomain.local
Nameservers = ns1.localdomain.local

zone in-addr-arpa.1.0.10.
SOA for in-addr-arpa.1.0.10 = ns1.site2.localdomain.local
Nameservers = ns1.site2.localdomain.local

The remote site's server will look similar:

zone localdomain.local
SOA = ns1.localdomain.local
NS = ns1.localdomain.local

zone site1.localdomain.local
SOA = ns1.localdomain.local
NS = ns1.localdomain.local

zone site2.localdomain.local
SOA = ns1.site2.localdomain.local
NS = ns1.site2.localdomain.local

by chrisdent

One final comment.

Windows 2000 DNS isn't as capable as it first appears. These type of records only really appeared in Windows 2003 DNS, which is a little strange since BIND (Linux DNS) has been capable of such functionality for years.

If you can make a Win 2003 server the primary DNS it would probably help you out.

by mark

I'm a little confused. Are these public domains or private? Do you have one server setup as a PDC and the other a BDC or are you using Active Directory? If you have them both setup as PDCs, then there is your problem. Demote one to a BDC.

This discussion is closed to new replies.