Windows Server VPN | RAAS Not Assigning Connection specific DNS Suffix

Question

Hello, I've set up a new VPN Server using SSTP to our secondary DC VM which uses Microsoft Windows Server 2019 10.0.17763 N/A Build 17763 and it doesn't append connection specific DNS suffix when connecting from client and I can't reach resources using short hostnames by ping or NSLOOKUP, I can only reach it by using FQDN.

I set the VPN up to use a static address pool of IPs that I excluded for automatically distribution from DHCP, enabled broadcast name resolution, set-up the RAAS TCP/IP to use the secondary DNS server as preferred and the main one as alternate (FYI, even changed it between them and had no success), enabled append primary and connection specific DNS, append parent suffixes of the primary DNS suffix, set-up the DNS suffix for this connection, Register this connection's addresses in DNS, Use this connection's DNS suffix in DNS registration, I disabled the TCP/IPv6 because we don't use it and came across some threads that it can interfere with the DNS suffix appending, set up DNS Suffix and NetBIOS Computer Name in System Properties, in DHCP I have enabled DNS always dynamically update DNS records and it still won't Assign Connection Specific DNS Suffix.

I'm attaching a picture of the configs I made and the nslookup test.

Other Things I tried :

Deleting the virtual network adapter, reset it on the HOST MACHINE, re-adding it, uninstalling RAAS, scanning for corrupted files, repairing system image using DISM, reinstalling RAAS.

I have another VPN connection that has been used on the main DC server which is in another location, it's set up exactly the same only that it actually assigns the connection specific DNS Suffix.

The workaround I'm using for now it's specifying it from Powershell on the client side.

I don't know what to do and check anymore. I have been trying to find solutions on other threads for a few days now, the only thing that remains and I think it's the most desperate measure is to delete the VM and start configuring it again from 0 so help me out please.

Thank you and sorry for the bad English and the bad technical explanation that I gave.

Answer 1

Hi,

Thank you for posting your query.

Kindly follow the steps provided below to resolve your issue.

So if we want to use DNS suffix, we could add it in the TCP/IP properties of VPN connection.

Even if we choose DHCP to assign IP address, the DNS suffix also won’t be assigned to the VPN client.

When the VPN server uses DHCP to assign IP addresses, the RRAS obtains 10 IP addresses from its configured DHCP server. It records the following information for each lease response it obtains from the DHCP server:

• The IP address of the DHCP server.
• The client leased IP address (for later distribution to the Routing and Remote Access client).
• The time at which the lease was obtained.
• The time at which the lease expires.
• The duration of the lease.

All other DHCP option information returned by the DHCP server is discarded.

For more details, please refer to this article below,

RRAS and DHCP

http://technet.microsoft.com/en-us/library/dd458962(v=ws.10).aspx

Go to this link for your reference and other troubleshooting procedures https://social.technet.microsoft.com/Forums/ie/en-US/0d67aa00-f760-4db0-9bae-a78ea241821b/raas-not-assigning-connection-specific-dns-suffix?forum=winserverNIS

Do not hesitate to message us if you need further assistance.

If the answer is helpful kindly click "Accept as Answer" and up vote it.