I've got a VPN server set up in my Active Directory on a remote network. (VPN Server is separate box from DNS/AD) When I dial into the network (client machine is not a member of the AD) the machine does not register its IP or Hostname in the DNS. I've played with all possible combinations of DHCP and RRAS-allocated IP pools, and none of them seem to cause my client to register. Is it because my client has to be a member of the domain? Are there some security settins I can tweak so that it can register its hostname/ip? I've looked in the event logs (System and Security) for the AD, DNS, DHCP, RRAS, and the client machine, and don't see anything relating to DNS Registration.

Here's the IPConfig on the client machine (once connected):

PPP adapter My VPN Name:
   Connection-specific DNS Suffix  . : mydomain.local
   Description . . . . . . . . . . . : My VPN Name
   Physical Address. . . . . . . . . :
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . :
   Subnet Mask . . . . . . . . . . . :
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . :   <- DC1
                                <- DC2
   NetBIOS over Tcpip. . . . . . . . : Enabled


It looks like my clients are not recieving the DHCP Scoope Options. I found this great article in Microsoft's KB. So the problem here is that the VPN Server "pre-reserves" the DHCP addresses, but then you have to add the DHCP Relay Agent to relay the secondary request for scope options. My problem is that the DHCP Relay Agent isn't relaying to the local DHCP server (same box as the VPN/RRAS). I've configured the DHCP Relay Agent according to this KB, but it dosn't work for a local DHCP server. (I see the request count increasing, but no responses)

I was able to get everything working by specifying the DNS server and domain name in the VPN connection properties on the client. But am still unable to assign it (or the default gateway) dynamically via DHCP. The client also has to be a member of the remote domain.

  • Need more specific info about how the VPN is setup, what the client is connecting to and what (if any) software is running on the client. – tomjedrz May 8 '10 at 0:15
  • For starters you have DHCP enabled = no, so that removes any possibility the the DHCP server will update the DNS for you. – John Gardeniers May 8 '10 at 2:51
  • The VPN is set up using Windows Server 2008 RRAS (Network Policy and Access Services Role). The client is standard Windows Vista or Windows 7 connecting via PPTP. The client is not "added to the Active Directory". In the above, I used RRAS to assign the IP address. I've also used DNS, and even used the options in DNS to "register client even if they don't request it." – Eric Falsken May 9 '10 at 17:14

Normally AD DNS zone updates are set to Secure Only. Since you are not using DHCP, DHCP will typically update DNS dynamically on behalf of the client. Try using ipconfig /registerdns and check the output of the command.

  • I've used DHCP with the /registerdns option. nothing in the local, DHCP, DNS, or RRAS event logs to indicate an error. I've also tried setting the DNS to allow insecure edits to the domain. Nothing in the event log to indicate a failure. (not even the security event log) – Eric Falsken May 9 '10 at 17:17
  • For starters you have DHCP enabled = no, so that removes any possibility the the DHCP server will update the DNS for you – Net Runner Jun 5 '17 at 20:39

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.