I pinged a couple of people associated with kube-dns and they were able to reproduce the issue on the latest kube-dns release (1.14.10). They are planning on tagging a new release of kube-dns that includes an improvement to the behavior. Thank you all for the guidance.
On Friday, August 31, 2018 at 1:13:45 AM UTC-6, mikioh...@gmail.com wrote: > > On Friday, August 31, 2018 at 2:54:08 PM UTC+9, Jason Newman wrote: >> >> Is it worth creating an issue around this? We have extracted the DNS >> client from `net` and are currently using it with the compressed flag >> enabled to allow compressed hostnames - the behavior that existed in go >> 1.10 and earlier. >> > > sure, please file an issue, at least we need to discuss how to deal > with srv rrs not only for classical unicast dns but for the latest unicast > dns, multicast dns and dns-sd, though there's no guarantee that the > previous wrong behavior will be back in future releases. > > for the record: > - in rfc2782, "... name compression is not to be used for this field." > - in rfc6762, "One specific difference between Unicast DNS and Multicast > DNS is that ... all Multicast DNS implementations are REQUIRED to decode > compressed SRV records correctly." > - in rfc6763, "Using DNS name compression ..." > > unfortunately, the dns specifications are everybody's friend; it's hard > to tame, to make a one-fits-all solution for the specs. > >> -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
