Failed to resolve DNS
-
Getting a lot of DNS errors when using the Quectel 5G hat
here is one from tailscale
- not logged in, last login error=fetch control key: Get "https://controlplane.tailscale.com/key?v=63": failed to resolve "controlplane.tailscale.com": no DNS fallback candidates remain for "controlplane.tailscale.com"I believe this is more of a Ubuntu issue than a modalai issue, but I thought I would track my progress here incase anyone else has issues
-
seems like it is coming from resolvconf program
-
busybox udhcpc client might be the culprit
https://unix.stackexchange.com/questions/174349/what-overwrites-etc-resolv-conf-on-every-boot
-
@wilkinsaf I've had to use this script for some of the modem workflows in the past:
https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-modem/-/blob/master/scripts/enable-dns.sh
-
@tom Gotcha, thanks! I was trying to figure out how to do it straight from the get go instead of a patch, but this is probably fine.
Did you end up throwing it in a service file? wondering if I should create a script to wait for a ping to succeed and then activate the dns
-
@wilkinsaf Oh actually it does get called in the VOXL1 + quectel workflow it seems: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-modem/-/blob/master/scripts/voxl-modem-start#L200
but not the VOXL2 flow
-
@tom here is a question...for voxl2 what should i set my modem to be if it is through quectel? Do i set it to "v2"?
-
@wilkinsaf It should be set to "quectel", you can use
voxl-configure-modemto setup the config file -
@tom out of curiosity what is v2 for? is that the sierra wireless hat?
-
