No DNS after reboot #5787
benjamindaines
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This has been giving me major issues for a while now. I can't even say for sure that it's an adguard issue, but this nightmare began after upgrading my Ubuntu 16.04 server to 20.04. As the title implies, after I reboot the machine I have no DNS and have to restart systemd-networkd manually. This is the case whether I have a public DNS configured in networkd or have the machine's own IP as the DNS entry. After I restart netword everything works fine, but this means that reboots require this intervention and I cannot figure out why or how to fix it.
I'm hoping someone here can help, none of the folks providing support for Ubuntu could figure it out. Man I really wish they had not switched to netplan....
I've already removed netplan and switched to networkd to manage my static IP. But why no DNS after reboot? Fresh install is not an option, it seems like there is some kind of conflict between AdGuard and the system's own DNS nonsense. AdGuard is the DHCP server for my network until I get a pfsense box set up, which is why I need to establish an IP manually with networkd, but why do my DNS settings not work, then work just fine after manually restarting networkd?
Should have never updated my LTS install.... very frustrated.
Not sure if it matters, but dnsmasq is disabled.
Beta Was this translation helpful? Give feedback.
All reactions