i have this one device that can’t resolve a url using the vpn dns, so i connect to the VPN in scutil --dns i see the dns servers and nameservers being pushed through the dns but when i go to ping said url or nslookup it, it doesn’t resolve and the nslookup is using the default router dns to try and resolve it and not even trying to use the vpn dns.
nslookup URL doesn’t resolve or find it
nslookup URL <<IP of VPN DNS>> it resolves it to it’s correct VPN
Any idea what could have been gone wrong?
Hi lexilex,
“nslookup” can’t be used to test resolving an address as it is a legacy tool that doesn’t use macOS’s resolver system (along with “dig” and “host”). Please see:
https://www.sparklabs.com/support/kb/article/configuring-dns-and-wins-settings/#notes-for-linuxunix-users
You can use the commands listed here to test resolving a domain:
https://www.sparklabs.com/support/kb/article/configuring-dns-and-wins-settings/#looking-up-or-testing-a-domain-name
If you’re still stuck, I recommend running through the steps listed in the following article:
https://www.sparklabs.com/support/kb/article/troubleshooting-dns-problems/
Cheers,
James
thanks for your reply, i did use the proper tool from mac but it was empty too, but with a split dns i’m guessing that it might be that the url doesn’t match our search domains that’s why it’s not going through split dns, but in that case if the primary resolver couldn’t find it shouldn’t it use the secondary resolver?
just to add i tried using the use full VPN dns options and now it’s using the vpn dns and search domains primarily, rather than the router or default one
