Failed to do run once: RFC2136 had errors in one or more of its batches: [dns: bad authentication]
#5299
Replies: 1 comment
-
|
Apparently some deployment tried to set a DNS A record xyz.k8s.example.com (instead of xyz.k8s.example.de). Since external-dns was not configured for k8s.example.com it got confused and died, instead of logging and ignoring the bad FQDN. This could be improved, I would guess. external-dns is version 0.14. Version 0.16.1 showed some hiccups as well, but I am not sure they were related to this problem. |
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.
-
updating external-dns from 0.14 to version 0.16.1 I got
The bind log shows
This is weird. There is no zone "." (AFAICT).
I found similar reports, but they did not elaborate what has to be changed to make external-dns work again. Every helpful hint is highly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions