Skip to main content

Posts

Showing posts with the label 404 Not Found - Custom Domain

New Custom Domains "In Transition" And Various Blog Gadgets

About a year after Blogger introduced custom domain publishing , they segmented the custom domain publishing process. In order to avoid database corruption, which was a frequent cause of the "Another blog ..." problem , they introduced a delay period, which we call "Transition" . Transition lets them delay key blog updates - until the world wide DNS infrastructure has a chance to reliably update with information about any new Google custom domains. In the beginning, Transition lasted almost exactly 72 hours, and delayed creation of the "301 Moved Permanently" redirect from the BlogSpot to domain URL. Later, when Following became a fixture on most blogs, we observed that the Followers gadget was also being updated on a Transition based delay.

Custom Domain Published Blogs With Earthlink As Registrar Are Showing "Not Found"

Today, we see discussions in Blogger Help Forum: Something Is Broken about a problem with blogs published to custom domains, and using Earthlink DNS servers . I have a blog showing "Server Not Found", and never got an answer here, so I called Earthlink tech support. It turns out it's an Earthlink problem with the "CNAME"s. A straight "A" retrieval Dig shows us simply no DNS addresses. ; > DiG 9.3.2 > @ localhost blog.data-miners.com A ; (2 servers found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER If we dig a bit deeper, we find out an interesting detail. ; > DiG 9.3.2 > @localhost data-miners.com ANY ; (2 servers found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER SOA localhost. hostmaster.earthlink.net. 2010033001 86400 900 2592000 86400 data-miners.com. 86400 IN MX 1 aspmx.l.google.com. data-miners.com. 86400 IN MX 5 alt1.aspmx.l.google.com. data-miners.com. 86400 IN MX 5 alt2.aspmx....

Custom Domains Redirecting To Google Sites

Similar to a redirection to the Google Apps Start Page service , some custom domains will be found to be directed to Google Sites. Again, we'll see an apparently normal (asymmetrical) DNS address configuration . mydomain.net. 3600 IN A 216.239.32.21 mydomain.net. 3600 IN A 216.239.34.21 mydomain.net. 3600 IN A 216.239.36.21 mydomain.net. 3600 IN A 216.239.38.21 www.mydomain.net. 3600 IN CNAME ghs.google.com. --- ghs.google.com. 282206 IN CNAME ghs.l.google.com. ghs.l.google.com. 300 IN A 74.125.43.121 The diagnosis, again, will be made using an (abbreviated) HTTP trace . Sending request: GET / HTTP/1.1 Host: mydomain.net User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: 1.9.0.5) Gecko/2008120122 Firefox/3.0.5 Connection: close • Finding host IP address... • Host IP address = 209.85.171.121 • Finding TCP protoc...

Custom Domains, Google Apps, FeedBurner, and An Unusual "404 Not Found"

Occasionally, the ubiquity of the custom domain curse Server Not Found Error 404 surprises even me. In this case, as in many others, the domain is properly setup. mydomain.com. 3600 IN A 216.239.32.21 mydomain.com. 3600 IN A 216.239.34.21 mydomain.com. 3600 IN A 216.239.36.21 mydomain.com. 3600 IN A 216.239.38.21 www.mydomain.com. 3600 IN CNAME ghs.google.com. --- ghs.google.com. 282206 IN CNAME ghs.l.google.com. ghs.l.google.com. 300 IN A 74.125.43.121 An an (abbreviated) HTTP trace gives intriguing details. Sending request: GET / HTTP/1.1 Host: www.mydomain.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: 1.9.0.6) Gecko/2009011913 Firefox/3.0.6 Connection: close • Finding host IP address... • Host IP address = 209.85.171.121 • Finding TCP protocol... • Binding to local socket... • Connecting to host... • Sending r...

Custom Domains, and a Second Typical "404 Not Found"

Sometimes, even with a properly setup custom domain , you (or your readers) may encounter a well known problem Server Not Found Error 404 I wrote about this earlier, about a symptom that has no obvious cause . Sometimes, the well known "Server Not Found Error 404" symptom has a cause, but you may have to look carefully to find it. Many times, you find no clue in the DNS addresses. This is a normal (asymmetrical) DNS address configuration . mydomain.net. 3600 IN A 216.239.32.21 mydomain.net. 3600 IN A 216.239.34.21 mydomain.net. 3600 IN A 216.239.36.21 mydomain.net. 3600 IN A 216.239.38.21 www.mydomain.net. 3600 IN CNAME ghs.google.com. --- ghs.google.com. 282206 IN CNAME ghs.l.google.com. ghs.l.google.com. 300 IN A 74.125.43.121 Here, an (abbreviated) HTTP trace will give you a clue. Sending request: GET / HTTP/...