Google Domains - Google Registry (RIP)

  • Thread starter Thread starter Sushubh
  • Start date Start date
  • Replies Replies 83
  • Views Views 10,897
just a sour taste of past, when tried buying webhost...

What i am looking for a solid dns host, which reliable/ has very low latency (as low as possible) to resolve... this is why I tended toward google and open to looking for good solid alternatives.



I am curious why?

@mikrotik 20 what?

Are they good for a power user,?
It is 12+tax USD
 
@Realme I will echo @varkey comments. If you want complete control over your domains, you should explore running your own authoritative name servers. That way, you control the zone data for the domains and will not be under the mercy of the domain name registrar support team. The relationship with the domain name registrar then becomes purely a commercial one. I use Gandi and run my own DNS infrastructure.

The one important parameter I suggest that you seriously evaluate before finalising - if you decide to use name servers of the domain name registrar as authoritative for your domains, make it certain that they have DNSSEC support.

Edited - s/relation/relationship/
 
google domains is fine. prices are a bit on the higher side. user interface initially was a mess as it switched between two different layouts for different aspects of domain management. but now it's fine. i still have two domains on google both of which are not supported by cloudflare domains right now. dns management is good. changes are processed at good speeds.

one thing about cloudflare. they sell domain services at zero profit. this means that prices of most tlds are quite good on them compared to competition. but they are not going to be cheapest in all cases because tld operators might sell domains to them at higher price. cloudflare has not added support for new tlds in a long time. i assume this is because other domain companies are not happy with their zero-profit model so are probably demanding higher sale price for cloudflare so that they themselves remain competitive.
 
domain pricing depends upon tlds. .co is pricey compared to .com for instance.
 
I have moved all my domains to namesilo a few years back. They have the third lowest price ( at 8.99$/yr for .com) and also provides free private registration.
 
all decent domain companies provide free private whois protection. anyone still not providing it should just be avoided. name.com does not do it for free but usually always have a coupon that adds it for free. always annoyed me. no longer using them now.
 
@Realme I forgot to mention a couple of most important pieces of advice so instead of editing my earlier comment, sharing it separately as a comment. From a security standpoint, make sure the domain name registrar supports the following,

1. 2FA - Most domain takeovers happen due to lack of 2FA and weak passwords.
2. Registry Lock - With a registry lock in place, domain hijacking gets thwarted. You can read more about the registry lock here
 
Thank you everyone for sharing your wisdom.

I should have been more exact with my requirements

The domains is not user facing (except homepage?) but API/ App facing and lowest possible resolving latency is required ( hard-coding IP is not possible), based on geolocation I want it to be resolved to nearest server(or server with lowest latency)

That's why I was into Google's offfering and I will look into cloudflare now too

Thanks again :)
 
The domains is not user facing (except homepage?) but API/ App facing and lowest possible resolving latency is required ( hard-coding IP is not possible), based on geolocation I want it to be resolved to nearest server(or server with lowest latency)

Okay, but this has absolutely no relation to your domain registrar. ;)

Are you going to have API/APP servers in various regions? It's the latency to your servers that would matter more. Although DNS is critical, the name resolution happens once and is cached for an hour or so on average (unless you have really low TTLs). So number of name lookups would be really low in comparison to the requests being made to your API/APP endpoints.

Also, nobody queries your nameservers directly, they'd use a recursive DNS resolver from Google or CloudFlare or ISP etc right which would have its own caching too.
 
Back