stop and deactivate do not restore previous dns settings

[MarkWieczorek]

Context

• CLI Version: 1.41.0
• Platform: Fedora Linux 39

I would like to use nextdns on a laptop, but only when I am not on my home network. Based on the instructions, I thought that I would be able to easily activate/deactivate nextdns by using either

nextdns start
nextdns stop

or

nextdns activate
nextdns deactivate

However, when using the "stop" command, the dns settings are not restored, and simple commands like "ping" no longer work. The "deactivate" command, on the other hand, seems to keep the nextdns resolver in place (though I see that it does change the /etc/resolv.conf file).

So, either (1) there is a bug in the start/stop script, or (2) after the stopping nextdns, the user needs to do something else (like restart a service?). If it is the second, the documentation should be updated to reflect this.

[lavendercolor]

I'm facing the same issue on my laptop. Ubuntu 23:10, NextDNS CLI 1.41.0.

[MarkWieczorek]

My solution is to run

nextdns deactivate
sudo systemctl restart systemd-resolved.service

in order to get back the original settings. There should be a more elegant way of doing this. At a minimum, after running nextdns activate it should tell the user that they need to restart the service and provide the command.

[sergeevabc]

I'm facing a similar issue on Windows 7 x64. After executing the nextdns deactivate, OS does not communicate with my native resolver so even the ping does not work.