Hi Miek, > So this discussion stems from this issue: > https://github.com/skynetservices/skydns/issues/217
I deliberately didn't mention that so as to avoid getting into specifics of one case when it clearly seems to be a more general issue. :-) > And apparently the glibc resolver assume this is ordering is in > effect. Amongst others. > This btw, has nothing to with the Go language (as implied on the ietf@ > thread), but is just an issue in SkyDNS. I did not imply it had anything to do with Go, I merely sampled Go's stub resolver in my potted survey. It's actually the one that comes out best since it re-starts parsing the whole packet, as I stated. > It is also true that (stub)resolvers directly talk to SkyDNS, any > recursive queries are proxied through to a real recursor, but it will > authorative answer for the (single) domain is has configured. AIUI, forgetting SkyDNS exists, it's allowable for a stub resolver to be configured to talk to a server that can answer authoritatively for the CNAME and the A, thus some clarification may be needed. Cheers, Ralph. _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
