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

What's The URL Of My Blog?

We see the plea for help, periodicallyI need the URL of my blog, so I can give it to my friends. Help!Who's buried in Grant's Tomb, after all?No Chuck, be polite.OK, OK. The title of this blog is "The Real Blogger Status", and the title of this post is "What's The URL Of My Blog?".

Leave Comments Here

Like any blogger, I appreciate polite comments, when they are relevant to the blog, and posted to the relevant article in the right blog. If you want to ask me a question thats relevant to blogging, but you can't find the right post to start with (I haven't written about everything blogger related, yet, nor the way things are going I don't expect to either), ask your questions here, or leave an entry in my guestbook.

As noted above, please note my commenting policy. If you post a comment to this post, I will probably treat it as a "Contact Me" post. If you have an issue that's relevant to any technical issue in the blog, please leave a comment on the specific post, not here. This post is for general comments, and for non posted contact to me.

If the form below does not work for you, check your third party cookies setting!

For actual technical issues, note that peer support in Blogger Help Forum: Something Is Broken, or Nitecruzr Dot Net - Blogging is, almos…

What Is "" vs. ""?

With Google Domains registered custom domains becoming more normal, we are seeing one odd attention to detail, expressed as confusion in Blogger Help Forum: Learn More About Blogger.My website uses "" - am I supposed to use "", instead?It's good to be attentive to detail, particularly with custom domain publishing. This is one detail that may not require immediate attention, however.