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 request...
• Waiting for response...
Receiving Header:
HTTP/1.1·302·Moved·Temporarily(CR)(LF)
Location:·http://feedburner.google.com/fb/a/home(CR)(LF)

Even FeedBurner, it appears, is involved in the Google Apps quagmire.

Fortunately, there's a possibility to sort this. We may be able to use the FeedBurner MyBrand wizard to remove the domain mappings.

1. Use the FeedBurner MyBrand wizard, and define "feeds.mydomain.com" in Step 1 of MyBrand.
2. Add a new virtual host to your domain, defining the target URL, as specified in Step 2 of MyBrand.

   feeds.mydomain.com.      3600    IN      CNAME   1e0jtkx.feedproxy.ghs.google.com.

3. Activate the MyBrand service.
4. Deactivate the MyBrand service.

>> Top