Discussion Locked

DNS config for domain over vpn

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have 2 remote sites and one w2k3 server as a domain controller at the main site. both remote sites only have workstations (about 10 at each site). I have joined the computers to the domain and this works fine. I have the workstations at both remote sites pointing to the domain controller for DNS. I don't like depending on the domain controller for resolving DNS over a vpn at the remote sites because the vpn can go down at anytime but if you don't point the remote workstations to the domain controller for DNS you have long logon times and authentication for domain access can be very unstable and sometimes not work. What do you do? configure the domain controller for primary DNS for the remote workstations and use a public DNS server for secondary DNS. Thanks in advance.

6 replies

by techkid

There isn't anything you can do in this setup. Workstations need to contact the domain dns servers for logon, if they can't contact the dns server, they will wait for a timeout and used cached credentials.

This was the same with Windows NT. No domain controller onsite and the clients can't find one... you get the "domain controller could not be found... please contact network administrator..." error message.

Don't know how your vpn is setup but doesn't the internet access go down when the vpn goes down for these offices?

The only option is to put a domain controller on site.

by cg it

Install a DC at each site and give the DC the Global Catalog role. Then set replication schedules during a time when there isnt' a lot of traffic on the network.

by nico baggus

How aboutr allowing to do a (LM)HOST lookup for
your domain controller only.
It would still allow to reach your domain
controller and (in the process) pull up your VPN
link. When that link is there you can continue.

Kind regards,
Nico Baggus

by jt

the quickest and dirtiest hack of them all for this would be to
put entries for each machine in the hosts file (c:
\windows\system32\drivers\ets\hosts). it's tedious (assign
each machine a static IP, then put the entries from all the
machines from that network into a hosts file, copy the hosts file
to each machine) but it will work.

The best solution would be to deploy a domain controller at
each site (with management it's almost never possible!)

by cweaver

If your VPN is down, you're out of luck anyway with domain access. But if the VPN goes down for some reason and you still have Internet Access, you can just set the ISP's DNS as a secondary on each workstation and they can at least access the Internet. I don't see a point in putting a DC at each site for 10 workstations. I don't see a problem with setting each workstation statically either since there are only 10 at each site. If you are that worried about the VPN going down, you should look into another method. I have a lot of clients with remote sites set up with VPN and they very rarely go down...if at all.

by jwahau

Experiencing all the problems described using a managed VPN and w2003 server. IPSEC tunnel from remote workstation (workgroup) to win domain - account in domain using shared drive for business. VPN works and doesn't work,internet not affected. Message - "credentials are invalid unable to access server". Solution restart remote device repair local network and pray.

This discussion is closed to new replies.