wickit Posted January 22, 2021 Posted January 22, 2021 Hi, This is doing my NUT in. I have setup a RRAS VPN on the server, and can connect and ping remote lan IP address's no problem I can also resolve the FQDN of servers on the remote lan, but I can not get it to use the short suffix for the servers, it will not resolve at all. This is an issue for remote users with mapped drives! I have checked that the VPN client is getting the VPN servers DNS servers and that the VPN adaptor is the highest in the network Interface metric order. Any ideas?
bald_pig Posted January 22, 2021 Posted January 22, 2021 In my experience, you need to use the fqdn to use the remote DNS and not local.
Davit2005 Posted January 22, 2021 Posted January 22, 2021 (edited) Whilst on VPN check using NSLOOKUP what server is been used and then you can test to see if the server names resolve properly. FQDN is favourable Are there any firewall rules blocking DNS ports UDP/TCP 53? Edited January 22, 2021 by Davit2005
mrwoberts Posted January 22, 2021 Posted January 22, 2021 When configuring the Windows VPN connection, we add the domain DNS suffix Run 'rasphone' (I just prefer to use this to configure VPN settings) VPN Properties >> Networking >> IPv4 Properties >> Advanced >> DNS >> 'DNS Suffix for this connection:' Add your domain suffix here.
wickit Posted January 25, 2021 Author Posted January 25, 2021 When configuring the Windows VPN connection, we add the domain DNS suffix Run 'rasphone' (I just prefer to use this to configure VPN settings) VPN Properties >> Networking >> IPv4 Properties >> Advanced >> DNS >> 'DNS Suffix for this connection:' Add your domain suffix here. This might work, as I am using this on locked down units and normal access to network setting is restricted!
CHiLL Posted January 25, 2021 Posted January 25, 2021 I couldn't resolve this and resorted to just changing all paths to FQDN, so mapped drives, home folders, shortcuts and other services.
mrwoberts Posted January 25, 2021 Posted January 25, 2021 One other way of doing this, although definitely not a long-term solution, is to add entries to the clients' HOSTS file in the C:\Windows\System32\Drivers\etc folder. Add entries for all important netbios names and FQDN with their matching IP address. Warning: Make a note that you've done this otherwise it could come back to bite you if any of those IP addresses change because you're essentially overriding your domain DNS lookups !!
free780 Posted January 25, 2021 Posted January 25, 2021 You can push out the DNS suffix by group policy.
wickit Posted January 26, 2021 Author Posted January 26, 2021 I have solved this issue by adding a WINS server. This seems to add the suffix to the clients and all dns queries now resolve.
free780 Posted January 26, 2021 Posted January 26, 2021 I wouldn't do that. Windows Internet Name Service (WINS) | Microsoft Docs
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now