Docker containers DNS lookups fails? #6913
Replies: 1 comment
-
I found the solution here: Add:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Couple of weeks ago deployed Adguard docker container on my home server and configured my router to point at it. It seemed to work just fine, clients get the DNS and Adguardhome is dealing with the reqests as exptected. However, it seems that my other docker containers DNS lookup fails entirely. For example I use Watchtower to update my containers, upon startup it gives me the following error:
watchtower | time="2024-04-13T20:32:50+02:00" level=error msg="Failed to send shoutrrr notification" error="error getting SMTP client: error connecting to server: dial tcp: lookup smtp.gmail.com on 127.0.0.11:53: server misbehaving" index=0 notify=no service=smtp
On my server, checking the dns, it seems to point at the correct adress:
And I can see in adguard that requests are indeed made to smtp.gmail.com and are not blocked.
So what do I do here?
Beta Was this translation helpful? Give feedback.
All reactions