Skip to main content

Custom Domains And Email Delivery, #2

There are a lot of details involved, in setting up a custom domain. Some details are not so apparent to every blog owner, when choosing a DNS model.

From time to time, I get confused queries about whether there is a practical difference between the "asymmetrical" and "symmetrical" DNS models.

Let's compare the "Symmetrical" and "Asymmetrical" DNS address models.

Blog Published To Domain Root - Symmetrical DNS Configuration

The most obvious configuration uses a symmetrical DNS structure - dual "CNAME" referrals. This will interfere with any auxiliary services, hosted outside Google. Here, you may publish to "" or to "", at your discretion. 3600 IN CNAME 3600 IN CNAME

Blog Published To Domain Root - Asymmetrical DNS Configuration, aka "Google Apps"

If you have a domain with email, FTP, and other possible auxiliary services, or if your registrar can't provide "CNAME" referral for the domain root, you use an asymmetrical structure, which uses Google Apps to let you add auxiliary services, with quadruple DNS server redundancy. Here, you may publish to "" only. 3600 IN A 3600 IN A 3600 IN A 3600 IN A 3600 IN CNAME

If you are setting up a new domain, 9 time out of 10 you can flip a coin. If you are prepared to publish to "", either model is acceptable. With an existing domain, and services like email being used, the difference between the asymmetrical and symmetrical models may be crucial to the success of the migration of the blog to the new URL.

Many existing domains, for established companies, have auxiliary services associated with the domain root ("naked domain"). One of the most common services involves email servers, which accept incoming email. Domain email services are defined with "MX" records. 900 IN MX 10 900 IN MX 10

With some DNS servers, definition of a "CNAME" referral for "" redirects all services, including "MX", to the "CNAME" target. As soon as you add a symmetrical DNS to support a Google custom domain, incoming corporate email delivery stops working. 3600 IN CNAME 3600 IN CNAME

Many registrars will not allow "CNAME" referral for the domain root, for this reason. This is one reason why Google developed the asymmetrical model - and the Google Apps "216.239.nn.21" server series. 3600 IN A 3600 IN A 3600 IN A 3600 IN A 3600 IN CNAME

For an existing domain, the asymmetrical model is almost always preferred. And with an asymmetrical model, be prepared to publish to "" - and (if desired) select "Redirect to".


Popular posts from this blog

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.

Free Domain Registration By "UNONIC" Is Fraudulent

Blogger blog owners, like everybody else, like to save money.

Some blog owners prefer to save money when registering a custom domain, for their blogs. We've seen several free domain registration services, providing what is claimed to be a two level Top Level Domain "co.xx" (where "xx" == various country codes).

The latest in this ongoing story appears to be "" - and 13 other "top level domains".There is also an additional free service offering third-level .tf domains, under the name United Names Organisation. They occupy 14 second-level domains, including,,, and They are run by the same company as, and are given away as URL redirections.