Google DNS not resolving certain SRV records

64 views
Skip to first unread message

Stefan Möller

unread,
Mar 29, 2019, 11:46:31 AM3/29/19
to public-dns-discuss
Hello,

dig @8.8.8.8 SRV _sip._udp.bc.soluno.se

does not resolve with or without DNSSEC (+cr), while

dig @4.2.2.1 SRV _sip._udp.bc.soluno.se
dig @1.1.1.1 SRV _sip._udp.bc.soluno.se

does. How come?

Domain provider is Loopia.se.

Any ideas are welcome.

Thanks

Alex Dupuy

unread,
Apr 14, 2019, 10:30:47 AM4/14/19
to public-dns-discuss
Hi Stefan,

You wrote:
dig @8.8.8.8 SRV _sip._udp.bc.soluno.se

does not resolve with or without DNSSEC (+cr), while

It is resolving now, and the problem was probably DNSSEC since the soluno.se domain is DNSSEC enabled.

Your +cr is short for the new +[no]crypto flag, which omits long (and meaningless to humans) DNSSEC key/digest/signature data if you have +dnssec to get those. (I have to say that generalized option abbreviation is a bug, not a feature.)

You meant to use the rather obscurely named +cd (for "checking disabled") flag, which likely would have succeeded.


Reply all
Reply to author
Forward
0 new messages