Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DNSSEC breaks SRV discovery #327

Open
blakerouse opened this issue Feb 27, 2022 · 0 comments · May be fixed by #328
Open

DNSSEC breaks SRV discovery #327

blakerouse opened this issue Feb 27, 2022 · 0 comments · May be fixed by #328

Comments

@blakerouse
Copy link

I am trying to use SRV discovery in gobetween (Docker :latest) and it is failing because the domain I am using has DNSSEC enabled. The results in a dns.RRSIG to be included in the answers from the DNS server.

Output from gobetween:

{"level":"info","msg":"Fetching 1.1.1.1:53 _api._tcp.k8s.example.net.","name":"srvFetch","time":"2022-02-27T12:30:28Z"}
{"level":"debug","msg":"Fetching 1.1.1.1:53 A/AAAA node1.example.net.","name":"srvFetch","time":"2022-02-27T12:30:28Z"}
{"level":"warning","msg":"No IP found for node1.example.net., skipping...","name":"srvFetch","time":"2022-02-27T12:30:28Z"}
{"level":"error","msg":"srv error Non-SRV record in SRV answer retrying in 2s","name":"discovery","time":"2022-02-27T12:30:28Z"}
{"level":"info","msg":"Applying failpolicy keeplast","name":"discovery","time":"2022-02-27T12:30:28Z"}
@blakerouse blakerouse linked a pull request Feb 27, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant