Replies: 2 comments 2 replies
-
|
Some logging and examples would help. My compose stack always comes up fine without DNS issues. |
Beta Was this translation helpful? Give feedback.
-
|
Agreed, though I'm not sure what to log other than curl or dig tests. When I run a dig within the jail after restart, no issues, but when I run a dig or curl against an FQDN within a container such as frigate or sonarr it fails. Is there a specific syslog or similar that may be helpful? |
Beta Was this translation helpful? Give feedback.
-
|
What to collect can be found in #135 (yes, long read, but relevant for those wanting help) |
Beta Was this translation helpful? Give feedback.
-
|
I wasn't quite able to get to the bottom of this, but I moved off of local Adguard home to NextDNS so it's no longer a concern. |
Beta Was this translation helpful? Give feedback.
-
Subject, mostly. After restarting a docker enabled jail such as for adding new datasets to bind mounts, compose services that were already up and persist/relaunch upon OS restart appear to have invalid DNS.
If I bring everything down and let my dynamic networks get removed and recreated with new containers this issue is resolved.
Has anyone seen behavior like this? Thanks.
Beta Was this translation helpful? Give feedback.
All reactions