DNS issue on HA (if I'm right) but Why

Configuration
1

Hi All,

I need your help because for the moment I don’t know why I have this issue
I’m not sure but it arrived, may be, after upgrade in 2024.12.4

HA Version :
image

Sorry I’m french so my HA is in french
I have this message. HA would like to correct the problème if I click on validate button. And to correct it, HA will uninstall Cloudflared in this print screen. Because HA doesn’t find the repo and for this addon the repo is Github
I have the same problem for ESPHome, Mosquitto, …

image
image818×1136 59.4 KB

That I understand and after test, this is a DNS resolution problem
I try to uninstall cloudflare for exemple and when I would like to reinstall it, I received a error message : Could not resolved github.com :woozy_face:

So I try this in SSH on my HA
I haven’t a DNS resolution for the Github Domain
image

Strange, so immediatly I try to ping Github Domain
That works, I ping the FQDN and HA find the IP. So the resolution works
image

A new DNS resolution after the ping and resolution is OK
image

And of course if I reboot my HA, the problem come back

What do you think about that ?
Do you have this problem ?
Do you have an idea to help me to find a solution ?

Many thanks if you can help me to find a solution

1 Like
2

Add print screen in English

image
image769×1094 51.3 KB

3

I have the exact same problem.
And it seems to get worse after every restart or reboot of my HA instance.
A few days ago (after an update), I lost ESPHome.
Today, it’s the backup to google drive which is now missing.

And I too have no clue on how to resolve the issue.

1 Like
4

Same issue here, lost many of the intergrations activities due the need of proper DNS resolution. Cannot even do rollback to previous backup because supervisor relies on DNS as well. DNS is set now as static to google dns, no ipv6 no wifi… still cannot make anything working except those connection I have on internal network. Cannot do updates, obviously.

1 Like
5

I have my own DNS on my LAN, ok it’s an old Win2003 :rofl: :rofl:
But my DNS works. And HA had this DNS.
Before the upgrade that works fine

So now I changed DNS only on HA by Google DNS 8.8.8.8
I restarted HA.
It’s OK, all messages are not present

And since yesterday evening HA run perfectly

I’m waiting an update and I will try to set my own DNS

6

I also run my own DNS and it seems to be the root cause of this problem.
Changed my DNS settings to google (8.8.8.8) and my own server as the secondary DNS and now I can reinstall all the previously deleted add-ons.
This is weird.
A wild guess would be that HA doesn’t like private IP adresses for the DNS.
Dunno.
But it works now.

1 Like
7

I removed my router’s DNS completely (its anyway rooting to google) and kept only google ones… doesnt work, even weather app doesnt work!

1 Like
8

Posting a log might reveal something.

image
image929×811 46.8 KB

9

Yes but before the last update an own DNS works. So …

10

Strange …
For me and another member of this forum that works

11

I will check that tomorrow morning
Thanks

12

is that similar?

1 Like
13

Same here, this behavior started with 2024.12.4, if I change the DNS then integrations work again, then I can roll back to my default DNS, very weird.

1 Like
14

This has started to happen for me tonight too, on two different HA/RPi installs at separate locations. one on 2024.12.4 another on 2024.12.5

lots of custom components fail to load/can’t be found

1 Like
15

So, I tried the same HA url from a browser I don’t normally use and HA / custom components worked fine. Cleared browser cache in my normal browser and that’s now working too.

1 Like
16

Ok but I don’t understand the link between DNS and cache …
I will check

17

There was an update this morning Core in 2024.12.5

  • Core 2024.12.5
  • Supervisor 2024.12.0
  • Operating System 14.1
  • Interface utilisateur 20241127.8

So I fall back to my own DNS
Message for Repair Issue has disappear. I’m waiting some days

Also DNS log not very verbose

Same as two days ago
Dig doesn’t work
Ping the FQDN
Dig works

No difference into log output :face_with_raised_eyebrow:

image
image892×119 4.66 KB

18

Not sure how it happened, but was able to update to core 12.5… but problem persists. Cannot resolve anything, direct ping works.

s6-supervise coredns warning unable to spawn ./run Exec format error

2 Likes
19

Same problem for me. Worked for years, but now the configuration of a local DNS breaks the DNS resolution of some external addresses (like github) but not all of them.

I was able to fix it once when it first happend to me 2 weeks ago by rebuilding core via ‘ha core rebuild’ using my local DNS but that does not work anymore either.

Additionally, there seems to be no way to rebuild or reload the ‘to be removed add-ons’ and repository entries when the DNS resolution works again, which is very annoying.

I’m running HA version 2024.12.5

Any help would be appreciated.

Thanks!

1 Like
20

I tried some restart oh HA (5 or 6)
And after the last restart, the problem is present again

image

I’m going to change the DNS by 8.8.8.8 same as yesterday