Very few registrars allow multiple "CNAME" addresses, for a single DNS host.
When I diagnose DNS address problems, I generally recommend
Add the addresses highlighted in green.
Remove the addresses highlighted in red.
I find that it helps to have the old address visible, while the new address is being composed. This does not always produce the desired result, unfortunately.
Many registrars do not allow multiple "CNAME" addresses, for DNS hosts - and the zone editors reject new address attempts.
When DNS addresses for a Blogger custom domain need to be corrected, I recommend
Add the addresses highlighted in green.
Remove the addresses highlighted in red.
I recommend correction in this order, so the blog owner can view the current (incorrect) addresses, while adding new (correct) addresses. This compensates for various zone editor syntax oddities.
Making corrections in this order - adding correct addresses, then removing incorrect addresses - does not always produce the anticipated results. If the zone editor checks as each individual address change is made, we see the result.
"That name is reserved (already in use)."
Some zone editors check, immediately, when a second "CNAME" is entered, for a given "Host" address. When multiple "CNAME"s are forbidden, and the zone editor checks for multiple "CNAME"s immediately, we have a problem.
Other zone editors check for a correct address complement, when Saving multiple zone editor changes - after all additions and removals are successfully made and verified. These zone editors do not present a challenge - as long as the blog owner removes all incorrect addresses.
When the incorrect addresses are not removed properly, we see the result.
That name is reserved (already in use).
This leads the blog owner to cancel the recommended correction - and we wait, in vain, for the domain to come online.
In a worse case scenario, we can even end up with another case of "Another blog ...".
Right now, though, we can only diagnose the problem, one domain at a time.
Some registrars have zone editors which forbid multiple "CNAME"s for specific addresses - and check, one entry at a time, for mistakes. This may cause a problem, with a #Blogger blog owner making custom domain DNS address corrections, when instructed to "Add addresses highlighted in green.", then "Delete addresses highlighted in red."
Some blog owners buy domains, for publishing a Blogger blog, and ask about how to address the domain.What address do I use for "Points to"?
Other owners may ask a similar question, referencing "Destination" or maybe "Target".
There is no real difference, between all 3 labels. "Destination", "Target", and "Points to" all refer to the same DNS address value.
To compound the confusion, 4 different addresses are required, when addressing a Blogger custom domain root.
Defining the DNS servers used by the domain root ("naked domain") requires 4 address records - and the labels used, in the zone editor, will vary from registrar to registrar.
We know of 3 different labels, used by Blogger custom domain instructions.
The referential Blogger document How do I use a custom domain name for my blog? uses 3 labels to identify the 4 name servers, which are provided by Google. Blogger uses the triplet label "Destination, Target, or Points to" as their example.
Note that not all registrars use "Name, Label, or Host" and "Destination, Target, or Points to" - because not all registrar zone editors display addresses in a neat column based display.
Google provides 4 name servers, to give us multiple redundancy.
Google provides four mutually redundant individual servers, each responding to a specific IP address - for custom domain clients to address the domain root, in a round robin sequence.
There are 4 name servers provided by Blogger, to address a custom domain root.
Each domain root name server entry uses 2 important label values ("Name, Label, or Host" - and "Destination, Target, or Points to") - with a zone editor that displays addresses in columns.
Each label may have 1 of 3 values, depending upon the zone editor provided by the registrar.
Here is the Dig Log, for the domain root. Look at the 2, 4, 6, and 8, in the 4 address entries.
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
In the GoDaddy zone editor, you'll see these entries depicted as
Host Points to TTL
@ 216.239.32.21 1 Hour
@ 216.239.34.21 1 Hour
@ 216.239.36.21 1 Hour
@ 216.239.38.21 1 Hour
The GoDaddy zone editor uses the labels "Host" and "Points to".
Similar labels ("Name", "Label" and "Destination", "Target") are used by various other registrars, in their own zone editor.
A Zone Editor display, showing the base DNS addresses, for GoDaddy.
Here is the display, used by GoDaddy, for "nitecruzr.co.uk".
Here is the zone editor display, as provided by GoDaddy.
Do you see the 4 address records, beneath "Points to"?
The labels in the address records differ, from registrar to registrar. The "Name, Label, or Host" address values (here, shown as "@") will differ, from registrar to registrar - but the "Destination, Target, or Points to" address values will not differ. A properly addressed domain will have the same 4 "Destination, Target, or Points to" address values, as every other properly addressed domain.
mydomain.com. 3600 IN A 216.239.3n.21
Each address will have one of four values for n: 2, 4, 6, or 8.
Complementing "Destination, Target, or Points to", we have another label set.
Complementing the 3 "Destination, Target, or Points to" label address values, for addressing the 4 name servers provided by Google, we have a similar set of 3 "Name, Label, or Host" label address values.
Addressing "Name, Label, or Host" is somewhat simpler - as all 4 entries are identical to each other, for any domain root address entry.
The Blogger instructions, like the GoDaddy zone editor, use "@", when addressing the domain root. The zone editor value used, however, may differ from registrar to registrar.
Any blog owner, wishing to have a working custom domain, needs to understand how to setup a domain for the registrar involved.
The end result.
Both the "Name, Label, or Host" - and the "Destination, Target, or Points to" - label triplets are only examples. Other unidentified registrars may use other labels.
Some registrars - such as 1and1 in their instructions 1&1 Help Center - Enter a CNAME for Your Subdomain - do not use a column based display. Neither "Name, Label, or Host" or "Destination, Target, or Points to" is part of the 1and1 instructions.
Considering the Blogger instructions, and the terminology required, Blogger Help Forum: Get Help with an Issue will not soon run out of blog owners, requesting assistance for making their custom domains work.
Some #Blogger blog owners, in the process of setting up their blogs using custom domain publishing, find that labels "Name", "Label", or "Host" - and "Destination", "Points to", or "Target" - are only examples, in the Blogger Help document.
There is no attempt at standardisation, used by the thousands of different Internet registrars, in their dashboards (aka "zone editors").
https://productforums.google.com/forum/#!category-topic/blogger/kMDo0O1xtDM
Custom domain setups continue to confuse blog owners - and lead sometimes to frustration, expressed in Blogger Help Forum: Get Help with an Issue.
When I am trying to set up a custom domain for my new blog, I'm not getting the 2nd CNAME Record, but the settings get saved.
In some cases, the domain may be operational - and other times, the domain will be broken, and no corrective instruction is provided.
The details in the instructions, Blogger Help: How do I use a custom domain name for my blog?, are misleading - and have resulted in broken domains.
The Blogger instructions are confusing.
5. Go to your domain registrar's website and locate the DNS (Domain Name System) settings in the control panel.
Not a lot of details, there.
10. Before you move onto the final step, wait about an hour for your DNS settings to activate. If you attempt the final step before your settings are activated, we'll let you know with a warning message.
All registrars don't use "3600" second TTL.
That's 2 examples of possible problems.
Publishing a blog to a custom domain is so much easier - and produces more reliable results - if you follow basic principles.
- Learn to use your registrar's zone editor.
- Learn to read a Dig log.
- Setup the DNS addresses, for your domain.
- If necessary, add domain ownership verification.
Learn to use your registrar's zone editor.
The registrar dashboard / zone editor is the portion of the registrar's website, that is created to let you, the domain owner, setup your own domain.
The zone editor is unique, for every different registrar - just as every website is different. One of the signs of uniqueness is hinted, by Blogger.
Each CNAME is composed of two parts - Name, Label or Host and Destination, Target or Points to.
These two (only two) terms here refer to the most essential details, in the zone editor, that make your domain operational. The two details have no consistent names - so we use examples.
The first CNAME is the same for everyone, Name being "www" and Destination "ghs.google.com."
That one sentence is the most essential, for all domains. It looks so simple - but it's so easy to get it wrong. Not every blog owner will see "Name" and "Destination" in the zone editor display. This leads to many imaginative - and wrong - alternatives.
Each registrar labels their zone editor, as they see fit. I've seen other terms used, in addition to the 6 implied. Both "Name, Label or Host" and "Destination, Target or Points to" are merely three examples, for each of these two essential elements.
These details are only hinted, by the Blogger instructions.
- Go to your domain registrar's website and locate the DNS (Domain Name System) settings in the control panel.
- Now it's time to enter the CNAMEs. Where it says Name, Label or Host simply enter "www" and list ghs.google.com as the Destination, Target or Points to.
Learning how to look, in the zone editor, is much more reliable than being told what to look for.
Learn to read a Dig log.
Compared to the confusion behind the registrar's zone editor, a Dig log is simplicity.
There are three basic DNS configurations, which produce a reliable domain for publishing a Blogger blog. 99.99% of all blog owners will use only one of the three.
ourdomain.com. 3600 IN A 216.239.32.21
ourdomain.com. 3600 IN A 216.239.34.21
ourdomain.com. 3600 IN A 216.239.36.21
ourdomain.com. 3600 IN A 216.239.38.21
www.ourdomain.com. 3600 IN CNAME ghs.google.com.
This is the asymmetrical DNS address configuration. Excepting one known variation, the asymmetrical configuration - with no options - is most reliable.
Setup the DNS addresses, for your domain.
As long as you have access to the zone editor, and understand the above issues - "Learn to use your registrar's zone editor" and "Learn to read a Dig log" - the rest will fall into place.
Unfortunately, not everybody has zone editor access. Similar to Blogger dashboard access, registrar dashboard access is not always a done deal.
Even having zone editor access, the Blogger instructions can mislead.
- Optional: You can also enter A-records, which links your naked domain (example.com) to an actual site (www.example.com). If you skip this step, visitors who leave off the "www" will see an error page.
- Optional continued: After completing Step 8, enter your domain name in the format example.com, and list the I.P. addresses shown below in the "A" section. You'll need to create four separate A-records which point to four different Google IPs.
Many problems, reported in the forums, indicate that using the domain root properly is (should be indicated as) a necessity.
Once again, the domain root, configured properly, should not be suggested as an option.
- Before you move onto the final step, wait about an hour for your DNS settings to activate. If you attempt the final step before your settings are activated, we'll let you know with a warning message.
All registrars don't use one hour TTL.
Be careful of the TTL setting. Unless you know better, stick with the registrar's TTL setting - and try to understand the effects of TTL latency.
If necessary, add domain ownership verification.
Returning to the Blogger instructions, we see
The second CNAME is particular to your blog and your Google Account, and is therefore different for each person.
Not every blog owner will see the second CNAME - whether or not the domain is properly setup.
The Blogger dashboard Publishing wizard only displays the "Error 12", and the second CNAME, under specific conditions. In some cases, the blog will be published to the domain - and the second CNAME will not be provided.
You may not see the instructions for the second "CNAME", until your base addresses are right. If you need the second "CNAME", the "Error 12" display will provide details - when the base addresses redirect properly. If the blog publishes, a second "CNAME" is not necessary.
That is my suggestion. Get the addresses right, before you start - then publish to the domain URL.
If the blog publishes to the domain, and the addresses are wrong, the domain will be broken - or unreliable.
The bottom line.
It's good to have instructions, they suggest the need for proper domain setup technique. Just don't be surprised if following them blindly gives you a broken domain - and an offline blog.
If you are lucky, the blog will appear offline immediately after using the Publishing wizard - and you will know that there is a problem to be fixed. Other times, you (or some readers) might not realise a problem until months or years later.
In the latter case, we'll see you, one day, in Blogger Help Forum: Get Help with an Issue.
I published my blog to my private domain, last month - and the blog pageviews have been in the crapper, ever since!
The instructions supplied by #Blogger, for setting up a custom domain published blog, can be misleading. Blindly observed, they can lead to an immediately offline blog - or to a blog that is online for some, and intermittently offline for others.
https://productforums.google.com/forum/#!category-topic/blogger/Jv0fT5cws3U
When you setup a Google Custom Domain for your blog, the essential first step is to setup one or more Address referrals. An Address referral will be entered as either an "A" ("Host") or "CNAME" ("Alias") record, and will consist of 2 essential components.- A "from" address.
- A "to" address.
How you enter the "from" and "to" records is an essential issue - and is not universal in nature. Please note that the terms "from" and "to" are not well defined. If you find this confusing, my apologies.
Note that in this article, as throughout my blog, I'll show extracted Dig logs to describe any Address referral.
When I setup my custom domain, "nitecruzr.net", on GoDaddy, I'll use the the GoDaddy Domain Manager. Your DNS host may, or may not, be GoDaddy, and your setup may, or may not, be the same as I describe.
When I setup a "CNAME" referral, I might define a local host "blogging" ("from"), as referred to a distant host "ghs.google.com" ("to"). I'll define host "blogging.nitecruzr.net" by entering "blogging", and the DNS Manager will add the ".nitecruzr.net" for me. We then say that the "from" address is relative to the domain, or is a "relative" address.
blogging.nitecruzr.net. 3600 IN CNAME ghs.google.com.
When I setup an "A" referral, I might define a local host "@" (aka the domain root) ("from"), as referred to a distant host ("to"), using an IP address. If I define the "to" address as "64.233.179.121", this is an "absolute" address - an IP address cannot be relative to a host name. An IP address has to be absolute.
nitecruzr.net. 3600 IN A 64.233.179.121
When I setup a "CNAME" referral, I refer the "to" addresses by host name. I'll enter the "to" address as "ghs.google.com", and the Domain Manager will add a trailing ".", giving my "CNAME" referral an absolute address.
blogging.nitecruzr.net. 3600 IN CNAME ghs.google.com.
Do you see the trailing "."?
GoDaddy adds the trailing ".", in most cases!
That's better!!
Not all DNS Hosts work this way!
With some DNS Hosts, if I enter a "to" address as "ghs.google.com", this will be taken as a relative address. The Domain Manager may then add the domain name on the end.
blogging.nitecruzr.net. 3600 IN CNAME ghs.google.com.nitecruzr.net.
Obviously, I do not mean to define a "to" address as "ghs.google.com.nitecruzr.net". When I setup a "CNAME" referral for these DNS hosts, I then enter the "to" address name as "ghs.google.com.", signifying an absolute address. The DNS Manager then does not add a trailing ".nitecruzr.net", and all's well.
However, I do have to know whether the Domain Manager configures "CNAME" referrals, by default, with absolute, or relative, addresses for the "to" addresses. Knowing this, I can correctly enter a "to" address with, or without, a trailing ".".
Some registrars have large server farms - and lack consistency.
Occasionally, we may encounter registrars where most servers may expect "absolute" addresses - and a few may expect "relative" addresses. Alternately, most servers may expect "relative" addresses - and a few may expect "absolute" addresses.
Such a tiny detail - and so essential. You may need to consult with Customer Support, from time to time.
