Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Benchmarking DNS response times of TLDs

bunnycdn.com

Post reply on HN
Print view View original

21–30 of 141 posts

Re: Benchmarking DNS response times of TLDs

#21

Post by Eikon »

frereubu wrote: post #16

We have a client who insisted on using a .house domain. It kept triggering alerts on our uptime monitoring service with DNS errors, so we had to reduce the sensitivity of that specific test. We also had a client who had to change their TLD from .healthcare to .org.uk because (a) people were confused because they didn't understand that there are all these new TLDs and kept adding .co.uk, .org etc and (b) some NHS syst…

> I still advise clients to use www rather than a plain domain name for websites

And you should. Not only can’t you put CNAME at the zone APEX without doing nasty tricks but not doing so is also a security risk when dealing with cookies.

Re: Benchmarking DNS response times of TLDs

#22

Post by syshum »

frereubu wrote: post #16

We have a client who insisted on using a .house domain. It kept triggering alerts on our uptime monitoring service with DNS errors, so we had to reduce the sensitivity of that specific test. We also had a client who had to change their TLD from .healthcare to .org.uk because (a) people were confused because they didn't understand that there are all these new TLDs and kept adding .co.uk, .org etc and (b) some NHS syst…

as with all things, this depends on your target audience.

If you seeking a general population for something like healthcare, finance, or any other ever day task then yes stick to the old school TLD's

Re: Benchmarking DNS response times of TLDs

#24

Post by javajosh »

sdan wrote: post #9
jjcm wrote: post #5

This is one of those things you simply don't expect to test when you're benchmarking performance. I've been trying to cut away chunks of 20-50ms on a side project I've been working on hosted on a .io domain, and I'm seriously considering switching because of this. Great article for sure. I also wonder at what point the trade off is between a vanity domain vs a more performant domain. For a CDN this makes perfect sens…

Although I may see what the BunnyCDN is trying to get at, personally I've gotten under 10ms with .com (even w/o caching). I find this a bit hard to believe without more people justifying or backing this work up. So yeah, don't worry about your TLD. .io is perfectly fine and companies and people internationally use it.

I'd like to point out that these are empty platitudes. Imagine going to your boss to justify not moving tlds and saying, "well sdan on hackernews said it was fine!"

Re: Benchmarking DNS response times of TLDs

#25

Post by pjc50 »

frereubu wrote: post #16

We have a client who insisted on using a .house domain. It kept triggering alerts on our uptime monitoring service with DNS errors, so we had to reduce the sensitivity of that specific test. We also had a client who had to change their TLD from .healthcare to .org.uk because (a) people were confused because they didn't understand that there are all these new TLDs and kept adding .co.uk, .org etc and (b) some NHS syst…

Even .org.uk isn't foolproof; I've had mine for 20 years and still occasionally get people leaving off the .uk. The most recent suspect is Google Android keyboard will autocomplete my email address .. and leave off the ".uk"!

Re: Benchmarking DNS response times of TLDs

#26

Post by sdan »

javajosh wrote: post #24
sdan wrote: post #9

Earlier quoted context omitted.

Although I may see what the BunnyCDN is trying to get at, personally I've gotten under 10ms with .com (even w/o caching). I find this a bit hard to believe without more people justifying or backing this work up. So yeah, don't worry about your TLD. .io is perfectly fine and companies and people internationally use it.

I'd like to point out that these are empty platitudes. Imagine going to your boss to justify not moving tlds and saying, "well sdan on hackernews said it was fine!"

if anyone does tell their boss, let me know ;) haha

Re: Benchmarking DNS response times of TLDs

#27

Post by pidg »

pjc50 wrote: post #25
frereubu wrote: post #16

We have a client who insisted on using a .house domain. It kept triggering alerts on our uptime monitoring service with DNS errors, so we had to reduce the sensitivity of that specific test. We also had a client who had to change their TLD from .healthcare to .org.uk because (a) people were confused because they didn't understand that there are all these new TLDs and kept adding .co.uk, .org etc and (b) some NHS syst…

Even .org.uk isn't foolproof; I've had mine for 20 years and still occasionally get people leaving off the .uk. The most recent suspect is Google Android keyboard will autocomplete my email address .. and leave off the ".uk"!

As the former holder of yahoo.org.uk, I can also confirm that ordinary people don't understand the difference between .org.uk and .co.uk.

Re: Benchmarking DNS response times of TLDs

#28

Post by Tade0 »

sdan wrote: post #10

I find this a bit hard to believe. Who's servers were you running this test on? Which regions exactly? Is there any other sources that back up this claim? Also interesting that .in (even though indian tld) is faster...

The company I used to work for switched from .io to .dev, because the former had issues with availability.

Re: Benchmarking DNS response times of TLDs

#29

Post by thrwaway69 »

sdan wrote: post #9
jjcm wrote: post #5

This is one of those things you simply don't expect to test when you're benchmarking performance. I've been trying to cut away chunks of 20-50ms on a side project I've been working on hosted on a .io domain, and I'm seriously considering switching because of this. Great article for sure. I also wonder at what point the trade off is between a vanity domain vs a more performant domain. For a CDN this makes perfect sens…

Although I may see what the BunnyCDN is trying to get at, personally I've gotten under 10ms with .com (even w/o caching). I find this a bit hard to believe without more people justifying or backing this work up. So yeah, don't worry about your TLD. .io is perfectly fine and companies and people internationally use it.

.io doesn't have a good history though outside of this - https://hn.algolia.com/?query=io%20domain&sort=byPopularity&...
Post reply on HN