Open micsport13 opened 4 weeks ago
Hi, thanks for your feedback.
I've managed to reproduce the issue and register a bug on our side.
If there are 2 DNS servers into resolv.conf and if the first is down then the resolver will jump automatically to the second, after retrying several times the first server. But this will slowdown the system.
Until then there is a workaround for /etc/resolv.conf
. When the file is immutable NordVPN application will not change it. But this would mean that you'll have to manage the file content manually. To make the file immutable sudo chattr +i /etc/resolv.conf
.
Thanks
I was setting up a local DNS server to route my traffic, but since it's a test, I decided to add a fallback dns when executing the command
nordvpn set dns
in the event my local DNS server is down. It appears that the dns search order is in the alphabetical order of the DNS servers, not the order it's provided in the CLI. So, if I have a DNS Server located at 172.168.2.15 and I specify 1.1.1.1 as the backup DNS, all queries go through 1.1.1.1 since it comes first alphabetically, even if I executednordvpn set dns 172.168.2.15 1.1.1.1
.Reproduction
Non-authoritative answer: Name: google.com Address: 192.178.49.206 Name: google.com Address: 2607:f8b0:402a:80d::200e
Server: 10.0.0.106 Address: 10.0.0.106#53
Non-authoritative answer: Name: google.com Address: 172.217.0.78 Name: google.com Address: 2607:f8b0:4025:810::200e