Matt Schreiber
Matt Schreiber
Thanks for your report. The issues you mentioned should be solved via #99 and #106.
It appears that you are using NetworkManager. There are known issues with certain NetworkManager releases (see [here](https://github.com/jonathanio/update-systemd-resolved#networkmanager) and [here](https://github.com/jonathanio/update-systemd-resolved#networkmanager-1)). Seems plausible that this is yet another manifestation of NetworkManager naughtiness....
@vishnus @audetto @mihneadb -- does the tip about `DOMAIN-ROUTE` and/or the [NetworkManager script from #59](https://github.com/jonathanio/update-systemd-resolved/issues/59#issuecomment-465276476) address your issues?
NetworkManager release 1.26.6 no longer assigns the `~.` routing domain to all managed interfaces (see [its NEWS file](https://github.com/jonathanio/update-systemd-resolved/issues/89#issuecomment-891909933)). Closing this issue; please reopen if upgrading NetworkManager and/or setting `dhcp-option DOMAIN-ROUTE...
The `up-restart` directive may help with some causes of forgotten DNS settings, though evidently not _all_ of them given [this comment](https://github.com/jonathanio/update-systemd-resolved/issues/89#issuecomment-891909933). If you don't currently have `up-restart` in your config,...
Is there still interest in porting this to Python?
Cool cool; no pressure :slightly_smiling_face: . Just didn't want to close this if it's still a live matter.
@Edu4rdSHL -- It's not `busctl call FlushCaches`, it's `busctl_call FlushCaches`, where `busctl_call` is [this function](https://github.com/cmadamsgit/update-systemd-resolved/blob/d2f5ee51fe531ebd473fa4550dafe7db81f939fa/update-systemd-resolved#L47-L54): ```shell busctl_call() { # Preserve busctl's exit status busctl call "$DBUS_DEST" "$DBUS_NODE" "${DBUS_DEST}.Manager" "$@" ||...
> I just want nameserver 192.168.0.1 and search lan to disappear while using vpn and then come back when turn it of. Could this be achieved by this tool? This...