Possible to Force a DNS server

Hi.

I’ve got myself in a pickle where I cannot perform updates. When I attempt to update, I get (for example):

Error: Update of Supervisor failed: Can’t install ghcr.io/home-assistant/amd64-hassio-supervisor:2023.12.0: 500 Server Error for http+docker://localhost/v1.42/images/create?tag=2023.12.0&fromImage=ghcr.io%2Fhome-assistant%2Famd64-hassio-supervisor&platform=linux%2Famd64: Internal Server Error (“Get “https://ghcr.io/v2/”: dial tcp: lookup ghcr.io: no such host”)

If I run nslookup ghcr.io on my HA OS VM, I’m told that connection to 192.168.1.12 was refused. 192.168.1.12 is the address of my HA OS, and I believe DNS is trying to use that because it had been using DNSmasq.

If I run nslookup ghcr.io on any other machine on my network, it correctly resolves ghcr.io via my router and Google’s DNS server.

I may have misconfigured the DNSmasq AddOn, or misunderstood what my router was doing, but

I have tried ha network update enp0s18 --ipv4-nameserver 192.168.1.1" and it claims to have completed sucessfully, but the nameserver is still 192.168.1.12

If I go to the HA file editor in the GUI, I get

401: Unauthorized

This, I can’t explain.

Further, when I try to run DNSmasq, from within the GUI, I’m told

Image homeassistant/amd64-addon-dnsmasq:1.6.0 does not exist for addon_core_dnsmasq

I have tried:

ha dns options --servers dns://192.168.1.1

and, if I subsequenty try to update supervisor, the error message is now:

Error: Abort update because of an issue with AppArmor: Can’t fetch AppArmor profile https://version.home-assistant.io/apparmor_stable.txt: Cannot connect to host version.home-assistant.io:443 ssl:default [Try again]

If I “Try again” I get the original error message above.

Can anyone help? Has anyone seen this before?

Thanks.

OKay. All sorted. I was looking at this the hard way. I never thought of simply adjusting the DNS server within the GUI.

With resect to the 401: Unauthorised message, that was fixed by clearing down my browser cache.