cannot unmarshal DNS message (SRV record)

[jose-lmax]

We have in a centos 8 machine installed:
choria 0.18.0-1
sernet-samba 4.13.3-5

Having samba configured to use its internal DNS service, choria-server cannot unmarshal the DNS message when it is about SRV records. And finally it takes the puppet server address from a CNAME we have defined.

host -t SRV _mcollective-server._tcp.my.domain
works, but not for choria-server.

[ripienaar]

please show relevant bits from dig +trace srv _mcollective-server._tcp.my.domain

[jose-lmax]

It is not giving result for that query.

[ripienaar]

if your host works then so should dig :)

[jose-lmax]

dig SRV _mcollective-server._tcp.my.domain

; <<>> DiG 9.11.20-RedHat-9.11.20-5.el8 <<>> SRV _mcollective-server._tcp.my.domain
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56094
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 9, ADDITIONAL: 10

;; QUESTION SECTION:
;_mcollective-server._tcp.my.domain. IN SRV

;; ANSWER SECTION:
_mcollective-server._tcp.my.domain. 21600 IN SRV 10 0 4222 mypuppet01.my.domain.

[AaronFriel]

I may have good news, I'd root caused this and worked with the Go team to ensure this was released & backported to Go 1.17 and 1.16, just need to update and rebuild on those versions: golang/go#51127

That DNS response looks really short, so I'm surprised to see a "cannot unmarshal DNS" response with that query and answer, but perhaps there's something else going on.

[ripienaar]

Amazing, thanks for that, we track go releases quite closely so hopefully this will just go away soon then, thank you @AaronFriel