This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/dns-wg@ripe.net/
[dns-wg] Question about use of cname in Google's services
- Previous message (by thread): [dns-wg] Question about use of cname in Google's services
- Next message (by thread): [dns-wg] Call for Presentations - DNS-OARC Fall Workshop, Oct 2016
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jason Fesler
jfesler at gigo.com
Sat Jun 4 18:43:49 CEST 2016
A single query to the Google DNS server does return the CNAME - but it also gives the results to the CNAME. Which means, from the single packet reply, you get back the A or AAAA that you asked for. Are we really concerned over a few extra bytes? The fact that Google exposes the CNAME at all is just an implementation detail; one that has no practical impact to us. It might have simplified their serving platform - static DNS entries vs GSLB. But they take the effort to collapse the answer, and give an actionable response with the single packet. No extra round trips. Much nicer than some other implementations I've seen for serving both static and GSLB DNS assets. -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/dns-wg/attachments/20160604/8c34a366/attachment.html>
- Previous message (by thread): [dns-wg] Question about use of cname in Google's services
- Next message (by thread): [dns-wg] Call for Presentations - DNS-OARC Fall Workshop, Oct 2016
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]