Diagnosing Problems With Custom Domains - Case Study #7

Google Apps, which I originally identified in my second custom domain case study, and later in a separate article, Custom Domain Publishing, And Google Apps, is what I shall call a Web Services Aggregator. Google Apps gives us the ability to combine a Blogger blog using a non-BlogSpot URL in a domain with other Google and non-Google services.

Google Apps is not the only web services aggregator that we have identifed recently. Yahoo provides a similar setup.

Let's look at a Yahoo Web Services setup, using a hypothetical domain, "mydomain.net" (name changed here to protect the unfortunate).

First, let's dig the DNS records for the primary domain "mydomain.net".

 ;; QUESTION SECTION:
 ;mydomain.net.   IN A
 
 ;; ANSWER SECTION:
 mydomain.net.  1200 IN A 68.180.151.21
 mydomain.net.  1200 IN A 68.180.151.22
 mydomain.net.  1200 IN A 68.180.151.23
 mydomain.net.  1200 IN A 68.180.151.24
 mydomain.net.  1200 IN A 68.180.151.25
 mydomain.net.  1200 IN A 68.180.151.26

p2w12.geo.sp1.yahoo.com (68.180.151.21)
68.180.128.0 - 68.180.255.255
Yahoo 

Next, the "www" alias "www.mydomain.net".

 ;; QUESTION SECTION:
 ;www.mydomain.net.   IN A
 
 ;; ANSWER SECTION:
 www.mydomain.net.  600 IN CNAME ghs.google.com.
 ghs.google.com.  40765 IN CNAME ghs.l.google.com.
 ghs.l.google.com. 300 IN A 72.14.207.121

You'll have no problem with publishing to "www.mydomain.net", as the primary URL for "mydomain.net". I don't think that Yahoo Web Services provides an option to "Redirect mydomain.net to www.mydomain.net.", though.

Yahoo provides 6 servers, in contrast to 3 provided by Google. To date, nobody has succeeded in configuring the 6 Yahoo servers to address anything but Yahoo content. This makes Yahoo Web Services useless for using the primary domain in a Google Custom Domain.

>> Top