F5F Stay Refreshed Power Users Networks Update time for Google domains is currently available.

Update time for Google domains is currently available.

Update time for Google domains is currently available.

K
Kayla0719
Member
Find
75
06-02-2025, 08:34 AM
#1
Typically, the process can take anywhere from a few minutes to a couple of hours before the changes fully propagate across the network. It depends on factors like DNS server load and your internet connection speed.
Reply
Reply
K
Kayla0719
06-02-2025, 08:34 AM #1

Typically, the process can take anywhere from a few minutes to a couple of hours before the changes fully propagate across the network. It depends on factors like DNS server load and your internet connection speed.

Reply
Reply
M
Mr_Floobiful
Posting Freak
Find
890
06-03-2025, 02:00 AM
#2
The “up to 48h” applies to updating every DNS server globally. Google’s servers usually refresh quickly, even without direct interaction, and their domain DNS servers operate independently. Note that new records for a domain are added more swiftly than modifications to existing ones.
Reply
Reply
M
Mr_Floobiful
06-03-2025, 02:00 AM #2

The “up to 48h” applies to updating every DNS server globally. Google’s servers usually refresh quickly, even without direct interaction, and their domain DNS servers operate independently. Note that new records for a domain are added more swiftly than modifications to existing ones.

Reply
Reply
A
AlexLemire
Member
Find
88
06-04-2025, 07:02 PM
#3
That's what I assumed about the 48h timetable spreading across the entire DNS setup. Nonetheless, even after targeting the IPs of Google's domain name servers, drill hostname.ddns.mydomain still doesn't show a CNAME record for the subdomain or A/AAAA records for ddns.mydomain. Updated: To avoid this issue, I switched WordPress's configuration to use ddns.mydomain instead of hostname.ddns.mydomain, which now allows me to load the demo site outside my local network.
Reply
Reply
A
AlexLemire
06-04-2025, 07:02 PM #3

That's what I assumed about the 48h timetable spreading across the entire DNS setup. Nonetheless, even after targeting the IPs of Google's domain name servers, drill hostname.ddns.mydomain still doesn't show a CNAME record for the subdomain or A/AAAA records for ddns.mydomain. Updated: To avoid this issue, I switched WordPress's configuration to use ddns.mydomain instead of hostname.ddns.mydomain, which now allows me to load the demo site outside my local network.

Reply
Reply
L
Lillen110
Junior Member
Find
33
06-04-2025, 08:58 PM
#4
I set up a DNS record for my domain yesterday, and Google recognized it in just five minutes. Cloudflare’s DNS took roughly three times longer to respond before it functioned properly.
Reply
Reply
L
Lillen110
06-04-2025, 08:58 PM #4

I set up a DNS record for my domain yesterday, and Google recognized it in just five minutes. Cloudflare’s DNS took roughly three times longer to respond before it functioned properly.

Reply
Reply
A
Aquaman_JLA
Junior Member
Find
44
06-04-2025, 10:01 PM
#5
Sure, I understand. You're focusing on how the update was communicated through Google Domains' name servers.
Reply
Reply
A
Aquaman_JLA
06-04-2025, 10:01 PM #5

Sure, I understand. You're focusing on how the update was communicated through Google Domains' name servers.

Reply
Reply