Bug Report: systemd-resolved is listed as dependency but breaks the system #339
Labels
bug
Something isn't working
Comments
|
Today I had a similar issue with installation on fresh (12.4) Debian. Even while feeling desperate and depressed I had to reinstall the system. After many hours of experiments I managed to magically solve it by removing and reinstalling systemd-resolved package. After this dns resolving has been fixed. |
|
Can't find the source anymore, but this worked for me: Edit /etc/systemd/resolved.conf Uncomment the following lines and change DNS to your router/DNS-Server and DNSStubListener to no: DNS=192.168.178.1 Then restart systemd-resolved: sudo systemctl restart systemd-resolved |
You really help me with this. |
|
May be it's happend couse you use su root, su - instead |
|
I checked new release 1.6.0 |
|
This is a fresh installation output on Debian 12.4 with latest version (1.6.0).... Prerequisites installation: Checking Checking name resolution... From now I can't do anything...so...I fix the Now name resolution is ok Installing os-agent Installing HA Supervised So I stop the installation. and name resolution doesn't work again... So...i changed "again" now name resolution works again... and now installation works fine... |
|
Does your network provide a DNS server via DHCP? If not, then the fact that you have to set a DNS server manually is expected. 🤷♂️ systemd-resolved knows two level of fallback DNS server: Built-in fallback DNS, and configured fallback DNS. On Home Assistant OS, we have built-in fallback DNS servers. It seems that systemd-resolved as provided by Debian has no built-in fallback enabled. That is why you have to configure it in order to take effect. |
|
Ok, but... my network provides DNS via DHCP. With 1.5.0 version there was the same problem, but after systemd-resolved and prerequisites packages, after editing resolved.conf with a valid dns server, everything worked fine. (#304) Now...with 1.6.0 version the problem Is still present after prerequisites packages, but during supervised installation the resolved.conf file Is modified and manually added DNS in resolved.conf are nor present anymore. |
So this is reproducible with a vanilla 12.4 and just installing systemd-resolved? Ok, but so then the question becomes, why does Debian's systemd-resolved does not pick up that DHCP provided DNS? 🤔 |
|
Just another try... clean installation... This is my So...I install and now...these are |
|
Create a file at Or whatever set of options is appropriate for your system. |
|
I just went through the exact same thing on a fresh new Debian 12 install. |
I really can't get this one to run and I am always stuck here [info] Waiting for checkonline.home-assistant.io - network interface might be down... Is there any fix? Is there any guide that I can follow to get this install go through under Debian? Maybe I use the wrong DNS IP? Super confusing all |
How did you fix the problem? I tried now everything in this thread but nothing seem to work |
Did you try this? |
|
I had to disable the IPV6... Okay I found a solution for anyone still struggling:
sudo nano /etc/sysctl.conf add this in the bottom net.ipv6.conf.all.disable_ipv6 = 1 Reboot. And it installed finally.. Maybe this helps to pin point the problem for some users. This install is forcing the ipv6 ... no idea why. That's why it is so confusing... when I ping some website or install some package the DNS is resolved normally only with the install of Home Assistant Supervised it forces the ipv6 which doesn't work then and doesn't resolve. |
|
Disabling IPv6 Is not a solution |
only thing that worked for me so I guess my Router is the problem then. But weird that the installation forces ipv6 (not active on my router) and other installations don't? I don't say it's a solution but I read all comments here and in the Debian Setup Thread and nothing worked till I finally turned off ipv6 and it went through. Didn't need to change my DNS to 8.8.8.8 or anything. How did I find this? I read through the whole Guide Thread in the Home Assistant server and found one comment where someone was complaining that the installation forces ipv6 ... wouldn't have found it otherwise. |
|
@ChristBKK what router make/model do you have? I am guessing your router announces an IPv6 DNS server, which ultimately is not reachable (for some reason). Instead of disabling IPv6, I'd check what DNS servers your system receives (check |
thanks for the explanation. Will check it's for sure my routers fault I agree. |
|
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
|
This issue has not been resolved, but there is a pull request. Until that has been merged I would like this issue to stay open in order for people to find the workarounds in the comments above. |
|
Hi |
|
try this
i think it is better solution that hardcoding router ip in resolve.conf |
|
@lokomass, waiting for PR, this Is the clean workaroumd -> #339 (comment) |
|
Thanks for reply, when do you think this Will be published ? |
@snakuzzo also, this workaround can be shrinked to just And for now we don't have any hardcoded addresses. |
jhampson-dbre
added a commit
to jhampson-dbre/home_assistant
that referenced
this issue
Jul 29, 2024
A new variable `supervised_install_resolve_conf_overrides` can be used to configure resolve.conf overrides if the supervisor's default configuration breaks DNS resolution. ref: home-assistant/supervised-installer#339
jhampson-dbre
added a commit
to jhampson-dbre/home_assistant
that referenced
this issue
Jul 29, 2024
A new variable `supervised_install_resolve_conf_overrides` can be used to configure resolve.conf overrides if the supervisor's default configuration breaks DNS resolution. ref: home-assistant/supervised-installer#339
|
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
|
Not solved with latest version |
|
Hi, I've just run in to this myself. The issue isn't, per-se, systemd on it's own (although clobbering resolve.conf in the install probably isn't helping 😃 ) , there's a second side-effect coming from the network-manager (NM) install. NM dynamically creates resolve.conf itself (to provide a per-connection based system). When it's installed it doesn't handle global dns settings set in the resolve.conf very well. It only seems to honour settings made directly in the interface file(s). As a result, people using DHCP or defining nameservers directly on the interface are fine. Anyone using resolve.conf to configure DNS settings more globally will find they lose DNS unexpectedly during the restart of the NM service too. I'm currently using an override file that presets global DNS setting for NM and it's working neatly (even to the extent of being able to install netmasq as an alternative to resolve). It's the same principle as the previous suggestion, just for NM instead. /etc/NetworkManager/conf.d/99-local.conf I'm not sure how required NM is and I'm not entirely sure which of the resolve.conf settings are vital either, but NM has a rich array of settings. There's probably enough there to consider doing all the settings directly with it rather than modifying resolve. Maybe? Regards, Edit: Fix typos etc |
|
I just ran into this issue recently I was getting an internet connection but no DNS and removing eth0 (or whatever interface you are using) from |
|
Still not solved. Happened when I use dhcp to get ip,dns server and search domain: I added to: /etc/systemd/resolved.conf |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
OS Version
Debian 12 Bookworm latest
System Information
Linux debian 6.1.0-14-amd64
What happened?
Clean debian installation.
Trying to install HA supervised.
When I install systemd-resolved, the system can no longer resolve hostnames.
Hence I can not install docker (next step - address can not be resolved).
And I can no longer install any packeges (apt cannot resolve any hostname).
I understand this is not caused by Home assistant but is there an alternative to 'systemd-resolved'? Is the package going out of fashion?
When you build the OS version, how do you get it to work?
Machine Type
generic-x86-64
Installer output
No response
Relevant log output
No response
ADR
Code of Conduct
The text was updated successfully, but these errors were encountered: