4 ms·
"... (so just one DNS request)." Are you sure? request #1 1 news.ycombinator.com: 207 bytes, 1+0+4+2 records, response, noerror query: 1 news.ycombinator.c
by ised 11y ago
"... (so just one DNS request)."
Are you sure?
request #1
1 news.ycombinator.com:
207 bytes, 1+0+4+2 records, response, noerror
query: 1 news.ycombinator.com
authority: ycombinator.com 172800 NS ns-225.awsdns-28.com
request #2
1 news.ycombinator.com:
225 bytes, 1+1+4+0 records, response, authoritative, noerror
query: 1 news.ycombinator.com
answer: news.ycombinator.com 300 CNAME news.ycombinator.com.cdn.cloudflare.net
authority: ycombinator.com 172800 NS ns-1411.awsdns-48.org
request #3
1 news.ycombinator.com.cdn.cloudflare.net:
367 bytes, 1+0+5+10 records, response, noerror
query: 1 news.ycombinator.com.cdn.cloudflare.net
authority: cloudflare.net 172800 NS ns1.cloudflare.net
request #4
1 news.ycombinator.com.cdn.cloudflare.net:
89 bytes, 1+2+0+0 records, response, authoritative, noerror
query: 1 news.ycombinator.com.cdn.cloudflare.net
answer: news.ycombinator.com.cdn.cloudflare.net 300 A 198.41.190.47
A HOSTS file entry for HN will avoid this routine.
- Twirrim 11y agomaybe I should rephrase that as one outbound DNS query? The answer should be cached locally, or at least at your next hop resolver, and the TTL of 300 seconds is long enough to make it effective