Jump to content

So I just earlier tried adding a CNAME record or two ({*,hostname}.ddns.mydomain -> ddns.mydomain) to my Google Domain, and when I saved the GD page said "Up to 48h to take effect". Is it typically that long of a wait for that info to be up on ns-cloud-c<number>.google.com , or is it (hopefully) less?

Link to comment
https://linustechtips.com/topic/1253637-google-domains-update-time/
Share on other sites

Link to post
Share on other sites

The “up to 48h” is for the change to make it to every DNS server in the whole world. Google’s servers tend to be the fastest to update even when the update isn’t made directly with them. (And technically even the Google Domains DNS servers are separate from the Google DNS servers)

 

EDIT: also new records added to a domain update faster than changes to existing records.

Looking to buy GTX690, other multi-GPU cards, or single-slot graphics cards: 

 

Link to post
Share on other sites

That's what I thought (re: the 48h timetable being to propagate through the whole DNS infrastructure). Still though, even when I've pointed drill at the IPs of the Google Domains nameservers, drill hostname.ddns.mydomain doesn't return either a CNAME record for the subdomain or the A/AAAA records for ddns.mydomain.

 

Edit: So as a workaround I've changed wordpress's config to use ddns.mydomain instead of hostname.ddns.mydomain and I'm able to load the demo site outside of my own network.

Link to post
Share on other sites

6 hours ago, brwainer said:

Google’s servers tend to be the fastest to update even when the update isn’t made directly with them

agree

 

 

I created a dns entry for my domain earlier today and google knew it within 5 min, but it took cloudflares dns about 3x longer before it worked.

Can Anybody Link A Virtual Machine while I go download some RAM?

 

Link to post
Share on other sites

1 minute ago, unijab said:

agree

 

 

I created a dns entry for my domain earlier today and google knew it within 5 min, but it took cloudflares dns about 3x longer before it worked.

Right, but again, I was querying Google Domains' nameservers directly, where the update was made directly with them is what I'm trying to get at.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×