One Of The Blogger / Google Custom Domain Dns Servers Is Down
Saturday, September 28, 2019
Edit
This afternoon, nosotros started seeing about frantic work reports, inward Blogger Help Forum: Something Is Broken.
When nosotros expect at the DNS addresses for the domains involved, nosotros meet 1 mutual element - a custom domain, relying alone on the Google Apps DNS server "216.239.32.21".
Long ago, I warned people close the dangers of relying on 1 unmarried DNS server, for domain address resolution.
Now, nosotros meet simply that, happening.
This is the right DNS address setup, for your domain "mydomain.com".
This volition operate - for a spell (but non this week).
This volition operate - for a spell (but non this week).
This volition operate - for a spell (but non this week).
None of the inward a higher house 3 DNS address setups are working, right forthwith - in addition to hither is why.
Conversely,
If yous specified "216.239.32.21" yesteryear itself, for a host address inward your domain, that address is forthwith downward - except, possibly, for readers who purpose Firefox. One server ("216.239.32.21") is downward - maybe intentionally - but the remaining 3 servers ("216.239.34.21", "216.239.36.21", in addition to "216.239.38.21") are up. Google volition locomote along every bit is, until "216.239.32.21" tin endure conveniently repaired or replaced.
It's Labour Day Weekend inward the USA, in addition to all is good - for everybody who specified all iv servers for their domains.
>> Top
My custom domain published spider web log is non loading today. What is going on alongside your servers???The numbers, of concerned spider web log owners, are relatively small, compared to normal custom domain publishing problems - but the work organisation is real real.
When nosotros expect at the DNS addresses for the domains involved, nosotros meet 1 mutual element - a custom domain, relying alone on the Google Apps DNS server "216.239.32.21".
Long ago, I warned people close the dangers of relying on 1 unmarried DNS server, for domain address resolution.
But non 1 server is going to endure 100% reliable, or concluding forever. Every reckoner always made, similar every human born, volition die, 1 day.
Related
This is the right DNS address setup, for your domain "mydomain.com".
mydomain.com. 3600 IN Influenza A virus subtype H5N1 216.239.32.21
mydomain.com. 3600 IN Influenza A virus subtype H5N1 216.239.34.21
mydomain.com. 3600 IN Influenza A virus subtype H5N1 216.239.36.21mydomain.com. 3600 IN Influenza A virus subtype H5N1 216.239.38.21
www.mydomain.com. 3600 IN CNAME ghs.google.com.
This volition operate - for a spell (but non this week).
mydomain.com. 3600 IN Influenza A virus subtype H5N1 216.239.32.21
mydomain.com. 3600 IN Influenza A virus subtype H5N1 216.239.34.21
mydomain.com. 3600 IN Influenza A virus subtype H5N1 216.239.36.21
mydomain.com. 3600 IN Influenza A virus subtype H5N1 216.239.38.21
www.mydomain.com. 3600 IN Influenza A virus subtype H5N1 216.239.32.21
This volition operate - for a spell (but non this week).
mydomain.com. 3600 IN Influenza A virus subtype H5N1 216.239.32.21
www.mydomain.com. 3600 IN CNAME ghs.google.com.
This volition operate - for a spell (but non this week).
blog.mydomain.com. 3600 IN Influenza A virus subtype H5N1 216.239.32.21
None of the inward a higher house 3 DNS address setups are working, right forthwith - in addition to hither is why.
C:\>ping 216.239.32.21 Pinging 216.239.32.21 alongside 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 216.239.32.21: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),Server "216.239.32.21" is non online.
Conversely,
C:\>ping 216.239.34.21 Pinging 216.239.34.21 alongside 32 bytes of data: Reply from 216.239.34.21: bytes=32 time=25ms TTL=52 Reply from 216.239.34.21: bytes=32 time=23ms TTL=47 Reply from 216.239.34.21: bytes=32 time=24ms TTL=52 Reply from 216.239.34.21: bytes=32 time=34ms TTL=52 Ping statistics for 216.239.34.21: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate circular trip times inward milli-seconds: Minimum = 23ms, Maximum = 34ms, Average = 26msServer "216.239.34.21" is online.
C:\>ping 216.239.36.21 Pinging 216.239.36.21 alongside 32 bytes of data: Reply from 216.239.36.21: bytes=32 time=49ms TTL=47 Reply from 216.239.36.21: bytes=32 time=45ms TTL=47 Reply from 216.239.36.21: bytes=32 time=25ms TTL=52 Reply from 216.239.36.21: bytes=32 time=23ms TTL=47 Ping statistics for 216.239.36.21: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate circular trip times inward milli-seconds: Minimum = 23ms, Maximum = 49ms, Average = 35msServer "216.239.36.21" is online.
C:\>ping 216.239.38.21 Pinging 216.239.38.21 alongside 32 bytes of data: Reply from 216.239.38.21: bytes=32 time=45ms TTL=52 Reply from 216.239.38.21: bytes=32 time=71ms TTL=47 Reply from 216.239.38.21: bytes=32 time=46ms TTL=52 Reply from 216.239.38.21: bytes=32 time=24ms TTL=52 Ping statistics for 216.239.38.21: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate circular trip times inward milli-seconds: Minimum = 24ms, Maximum = 71ms, Average = 46msServer "216.239.38.21" is online.
If yous specified "216.239.32.21" yesteryear itself, for a host address inward your domain, that address is forthwith downward - except, possibly, for readers who purpose Firefox. One server ("216.239.32.21") is downward - maybe intentionally - but the remaining 3 servers ("216.239.34.21", "216.239.36.21", in addition to "216.239.38.21") are up. Google volition locomote along every bit is, until "216.239.32.21" tin endure conveniently repaired or replaced.
It's Labour Day Weekend inward the USA, in addition to all is good - for everybody who specified all iv servers for their domains.
>> Top
