DNS/WINS - resolution for second domain through VPN

We have some people at our office that are from a partner company.  A VPN exists between the two sites.  I can ping IPs on their subnet and they can do likewise to us.

When their people come here, they get a local address from our DHCP server.  They can ping their servers across the VPN.

However, name resolution does not work for their servers when they are here.

What is the best way to resolve this?
  Should I setup static addresses in our WINS database for their servers?  

  Should I setup another local zone in our DNS database for their domain, and add A records for their servers?  If I do that, will it still update public records for that domain (such as www, and other web servers, and mx records)?

  Should they use local static entries?

Thanks!





LVL 16
robrandonAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

msiceCommented:
Adding the A records for their servers in the DNS server is a simple solution if there are not a lot.
0
methabhayaCommented:
There are several solutions that you can do here.

I assume that you have your own domain and they have their own domain.
Also I would assume that when you mean name resolution you mean that the computer names (NetBIOS) inside your LAN and their LAN.

You should setup Static WINS entries.  or for the machines that they use simply edit their hosts file and add entries there.

DNS entry is only needed if you have internal DNS names. for public domains like something.microsoft.com you would not need to add entries to your DNS to recognise them as your DNS would resolve those or forward those request to other DNS server that can resolve those and return the entries to your DNS clients.

For a complete solution what you would do is combine the two companies LAN into one. Have a uniform IP assignment accross both companies and that means when users move from one company to another they have to do nothing. They simply keep working as they were in the other company. The users simply keep their existing IP's. This would mean less work for you to manage IP's. Once properly setup you can practically leave it alone.

0
robrandonAuthor Commented:
Thanks both.  Here is some more info (and questions):

methabhaya:
Merging the two networks is not an option.

I'd like the visiting users to be able to click on their My Network Places icon and still see all the computers in their domain.  Not sure if that is WINS or DNS related.  I think I can setup the static WINS records for their Outlooks to resolve, but what about browsing the servers in theirdomain.com?

msice:
I don't know if I can just add A records to our domain and have it work for them.  Say our domain is mydomain.com and their domain is theirdomain.com.  If I add an A record for a computer on their domain, lets say called Server1, it would be in our zone, i.e. Server1.mydomain.com, not theirs, Server1.theirdomain.com.  Do you know for sure that it would work?  Also, per my previous question, what about public DNS entries for their public web servers?  If I create a local zone for theirdomain.com would I have to statically assign those or would they populate from the internet DNS servers?





0
methabhayaCommented:

In order to get them to browse their domain computers simply find "lmhosts.sam" file on their computer and add entries. Try with 1 computer first. It should work.

For WINS you will be running your own domain. so if you add a static record to thier computers that should also work as long as the DHCP has WINS server defined as one of the option. which means when they get the IP they also get WINS server as well. But this is not gauranteed that you will see them under "My Network Places", so that's where the "lmhosts.sam" file comes in.

Try these. it should give you a workable solution. You don't need to do any changes to the DNS as that's not what you want.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
robrandonAuthor Commented:
methabhaya, thanks for your help.  I added static addresses to our wins database for their server's netbios names.

0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 2000

From novice to tech pro — start learning today.