A Blog Published To A Custom Domain Has A New URL - And No More

We see occasional signs of naivete, in Blogger Help Forum: How Do I?, about custom domain publishing.

Can I publish to a custom domain - and still use the Blogger dashboard?

and

Can I publish to a custom domain - and keep my comments and posts?

and

Can I publish to a custom domain - and avoid TOS restrictions?

Some blog owners seem to see custom domain publishing as more than it actually is.

When you publish your blog to a non BlogSpot URL (aka custom domain), using a proper setup, your blog now has a new URL.

The BlogSpot URL continues to work - and to direct search engines bots, search query results, and visitors, to the blog.

If your blog uses Google+ Comments, you won't see the comments published to the BlogSpot URL - although the comments will still exist, and be visible, in Google+.

Some accessory gadgets will stop working, temporarily, shortly after the new URL starts working. This is an unavoidable result of the Internet address lookup infrastructure, aka DNS.

Other than those details, you'll have the same blog as before - just with an extra URL, that may be more valuable to the search engines.

• The Blogger blog will still be hosted by Blogger / Google, and will use the Blogger dashboard for maintenance and publishing.
• The blog will be served subject to Auto Pagination.
• The blog will be subject to the same content restrictions - both porn labeling, and malware / spam deletion, will be consequences of any infractions.
• The blog will be subject to the same deletion recovery restrictions.

Just as any time you change the URL of your blog, you'll face changes in external relationships, such as with your readers, and with search engines and other services. Don't do this without careful planning, and methodical execution!

For the few times when your domain fails, see my troubleshooting check list - but prevent problems best, by first setting it up properly, and by observing your own limitations.

>> Top

Custom Redirects, And The Mobile Template Redirect, Are Not Compatible

We've recently seen a few reports about problems with custom redirects, in Blogger Help Forum: Something Is Broken.

I want to redirect my blog URL to a static home page. With a redirect in place, mobile computer users can't access my blog. Mobile browsers display an error, mentioning too many redirects.

This problem is being reported by owners of blogs both published to BlogSpot, and to non BlogSpot domains. When published to a non BlogSpot domain, the problem is present even for domains properly setup.

Some advice, given in the forum, suggests use of forwarding, instead of referral, as a solution. This advice is a problem, for 2 reasons.

• Forwarding cannot be used with blogs published to BlogSpot.
• Forwarding is not a good solution for custom domain publishing.

Right now, there is no solution for this problem - though there is a workaround. Blogger Support is aware of the problem - but it's not certain that a solution will be immediate.

For blogs published to BlogSpot, there are just two choices.

1. Disable the redirected home page, and do without the custom home page.
2. Enable the custom redirected main page, and do without mobile access to the blog.

For blogs published to a custom domain, there are, supposedly, three choices.

1. Disable the redirected home page, and do without the custom home page.
2. Enable the custom redirected main page, and do without mobile access to the blog.
3. Use forwarding, instead of referral, to redirect the domain to the blog.

Forwarding comes in two versions, with differing effects from the two versions. Neither version of forwarding is beneficial, to Blogger blogs.

• DNS forwarding results in the blog being indexed under the BlogSpot URL, by the search engines. The blog's readers will be able to use the (forwarded) domain URL, to access the blog - but all search engine references will mention the BlogSpot URL.
  
  With some access to the blog through the BlogSpot URL, and other access through the domain URL, blog reputation will drop, similar to blogs newly published to a new URL. Both reputation and traffic will do the same.
• Frame forwarding results in the blog being visible within an IFrame. No indexing of the blog, by the search engines, will take place, with blog contents visible inside an iframe. Search engine reputation will drop even worse with DNS forwarding.

Not all registrars offer both versions of forwarding, so you may have to take what they offer - and accept the resulting loss to the blog.

As a workaround, until the problem is fixed, you can return to the previous technique for making a static home page.

Basically, blog owners may have to choose between having a custom home page (for desktop access), and having the blog accessible through mobile browsers (for mobile access) - or using the workaround. And everybody has to wait, patiently, until Blogger Engineering can come up with a better solution - to make custom redirects, and the mobile browser redirect, work together.

>> Top

Is A Custom Domain URL More Valuable Than A BlogSpot URL?

We see the question, about relative value of a custom domain, periodically in Blogger Help Forum: How Do I?.

Does a custom URL actually have value, over a normal BlogSpot URL?

Some people wonder if a custom URL isn't similar to a custom ("vanity") license plate, for your car.

Personally, I can think of 3 reasons why a custom domain might be more valuable, for your Blogger blog.

• Some people believe that having your own domain makes your blog more individual and interesting - and they may be more likely to visit your blog when presented to them, in a search list.
• Since domains are not free, there are less dormant domains than dormant BlogSpot subdomains. It may be easier for you to get the relevant domain of your choice, than the relevant BlogSpot subdomain.
• A properly chosen domain URL may be easier for people to remember, than a BlogSpot URL.

Some people believe that their car is more fun, if it has a license plate that properly reflects their personality.

We know that Blogger blogs, published to a custom domain, have no special qualities. Is the address so special?

Maybe the belief makes the value. People who buy non BlogSpot URLs are not doing so to waste time or money, they do so because they believe that they will benefit. Many people, who read the advice / content of the people who buy non BlogSpot URLs, will also believe that non BlogSpot URLs have value.

Those people will pay more attention to a non BlogSpot URL, than to a BlogSpot URL, when they see a SERP entry that references a non BlogSpot URL - simply because they believe that a non BlogSpot URL has more value than a BlogSpot URL.

Why did Blogger provide the custom domain publishing feature, originally? They did so because:

1. Non BlogSpot URLs are more valuable than BlogSpot URLs.
2. People believe that Non BlogSpot URLs are more valuable than BlogSpot URLs.
3. People who buy Non BlogSpot URLs believe that Non BlogSpot URLs are more valuable than BlogSpot URLs.

Possibly, #3 makes the whole issue self fulfilling.

People believe - therefore, it is true.

That said, a custom URL will have more value if you set it up properly, and if you manage the new URL, aggressively.

>> Top

New Custom Domains Purchased From A Registrar, And Lacking The Transition Period For New Domains

We've known about the Transition period, which has applied to domains purchased through Blogger, for a few years.

Under Transition, domains purchased using "Buy a Domain" were only partially published, immediately after the domain purchase - with the publishing process completed, several days later. The Transition period allowed for the domain, newly setup by "Buy a Domain", to become fully visible on the Internet, before blogs subject to Transition were re published.

The Transition period was originally applied to blogs re published using "Buy a Domain", to delay redirection of the BlogSpot URL to the domain URL, until after a new domain was fully visible, to all Internet DNS servers.

Transition was designed to apply to new domains, purchased using "Buy a Domain", with the hope that domains purchased outside "Buy a Domain" would not need Transition.

When "Buy a Domain" was active, most blogs being published to domains not just purchased using "Buy a Domain" did not require Transition.

• Blogs published to domains, purchased directly from a registrar, would be owned by people with experience setting up domains. People with experience would be able to cope better with the DNS Latency, and inherent instability, involved with new domains.
• Some blogs would be published to mature domains, which would not need Transition at all.

With the ending of the "Buy a Domain" feature, we now have every new domain owner, experienced and not, purchasing domains directly from registrars.

In many cases, Transition is not needed for newly purchased domains, when the owner is not experienced. Inexperienced domain owners make mistakes, when setting up their domains. The domain setup process creates its own limited length "Transition" period, for inexperienced domain owners.

Recently, some domain owners have reported a new symptom, when using the Publishing wizard, to publish their blogs to their newly purchased domains.

This operation failed. Try again later. If the problem persist, please file a post on the help forum.

This new symptom may be replacing the long dreaded "Another blog or Google Site is already using this address.".

Most domain owners, seeing "This operation failed.", have domains with bad DNS addresses. They are generally instructed

You need to correct your DNS addresses.

Those not instructed to correct their DNS addresses should probably be advised

Your DNS addresses are righteous. You now need to wait 24 to 48 hours, for the newly purchased domain to be visible, everywhere on the Internet.

The latter advice will be necessary, simply because the domain was properly setup, immediately - even with the domain not fully visible across the entire Internet.

What happens with gadgets, which need updating, is yet to be observed.

>> Top

Blog Owners Reporting Custom Domain Setup Showing "This operation failed."

This week, we're seeing a few reports, in Blogger Help Forum: Something Is Broken from blog owners, trying to publish their blogs to custom domains.

I'm trying to use the Publishing wizard - and I'm seeing a new error.

This operation failed. Try again later. If the problem persist, please file a post on the help forum.

What has Blogger changed, recently?

It appears that we are now seeing a new phrasing of the well known error

Another blog is already hosted at this address

The majority of the domains showing this error, when checked, have bogus or missing DNS addresses. We see the usual demurrals.

I just got off the phone with the registrar. They say everything is fine on their end.

This is simply more of the same - registrars that still do not understand the importance of using referral, as opposed to forwarding, for custom domain publishing.

Once again, I cannot over emphasise the importance of righteous DNS addresses, when setting up a custom domain. It appears that, contrary to current instructions from Blogger Help, there is still just one working DNS address model, for custom domain publishing.

If you try to publish your blog to a custom domain, and the domain has any DNS addresses defined, the addresses must be righteous. If the defined addresses do not match the one known DNS model, expect now to see a new monolithic error.

This operation failed.

In some cases, it's possible that newly purchased domains, not subject to the Transition period earlier provided by "Buy a Domain", may display this error because of DNS propagation latency. New domain owners, even when they are able to setup a domain properly, may see this error because the new domain is simply not visible to all Internet DNS servers.

>> Top

Why Do We Need Four DNS Servers?

Occasionally, we see a perplexed blog owner asking a popular question about custom domain setup.

Does my domain really need four servers?

Some even seem to think that newer domains, with less readers, can get by with less - even one - servers.

Won't one server do - at least, for newer blogs? Theoretically, yes. But not one server is going to be 100% reliable, or last forever. Every computer ever made, like every human born, will die, one day.

Your blog (and your domain) depends upon DNS, to resolve its address. Address resolution is an essential part of helping your computer connect with the computer where your blog is stored.

If you specify just one server for your domain, and that one server goes down, your domain will be out of service - to the people depending upon that one server.

The named DNS server "ghs.google.com" is a redundant server array.

www.mydomain.com. 3600 IN CNAME ghs.google.com.

We use a "CNAME" to reference "ghs.google.com" - and we can't always use a "CNAME". Most registrars will not let you use a "CNAME" to resolve the domain root.

Google provides the 4 x "A" addressed server set, to resolve the domain root - when you wish to simply redirect the domain root to one of the aliases. Most domain owners will redirect the root to the "www" alias - though you are allowed to redirect to any one alias, at your discretion.

Google provides four mutually redundant individual servers, each responding to a specific IP address, for custom domain clients to access in a round robin sequence.

If any one server in the array of four becomes overloaded or goes out of service, and doesn't respond to a DNS query, the DNS resolver, on any client computer, will try the next server defined - if there is another server provided. If your domain provides just one server to resolve its address, and that one server goes down, your domain goes out of service. Your readers will see, yet again

404 Server Not Found

But wait - - there's more. Since Google provides four servers, and only one is out of service, they won't regard that as a major emergency. They still have three servers online - and nobody is losing sleep. Except, of course, you.

Google will repair or replace their one down server, when it is convenient to them. Maybe that will be next week, when their DNS server technician gets back from vacation.

Is that not convenient to you? Sorry.

With an asymmetrical configuration, you may not publish to the domain root. Your only valid choice is to publish to "www.mydomain.com", and select "Redirect mydomain.com to www.mydomain.com". If you publish to "mydomain.com", you will eventually see

Another blog is already hosted at this address.

or

Blogs may not be hosted at naked domains.

If you want to publish your blog to a custom domain using an ASymmetrical configuration, always publish to "www.mydomain.com", not to "mydomain.com". If you want to publish to "mydomain.com", you'll have to use a Symmetrical DNS configuration, and risk losing services hosted by your registrar. If you go with the first option, you will need all 4 servers - if you want a reliable and supported custom domain.

If your registrar or hosting service does not support 4 x "A" DNS addresses setup, you may want to use a (free) third party DNS host. Now, here's hoping that your registrar allows easy configuration of third party DNS service.

>> Top

Custom Domain Instability Caused By Using Unacceptable Servers

A few blog owners become confused by the necessary configuration of the domain root, when setting up their custom domains.

Some blog owners, who do not have a good understanding of DNS principles, make mistakes when setting up the domain root (aka "naked" domain). From good intentions (trying to ensure that the domain performs better or differently), their naivete may actually make the domain perform worse - or not at all.

With more blog owners unable to buy a domain through Blogger, and forced to setup their own DNS addresses, this will become an increasingly critical issue.

Blogger designed the custom domain feature to use "A" / "CNAME" referral, instead of DNS / frame forwarding.

The most obvious referral configuration - dual "CNAME" aka "symmetrical" DNS - is not supported by all registrars. Some registrars refuse to allow "CNAME" definition of the domain root, by policy.

To make custom domain publishing more globally usable, Blogger provided an alternative to dual "CNAME" referral - a hybrid configuration which uses 4 x "A" referral, for the domain root. This configuration is also known as "asymmetrical" DNS.

Asymmetrical DNS uses 4 Google servers, accessed in a round robin sequence, to define the domain root.

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.

Round robin DNS is pretty simple. Each server in the set is queried by the DNS client on the readers computer, in sequence, until one server responds. The first responding server is required to provide a suitable answer. If the first responding server provides an unsuitable answer, the DNS client has no alternative but to display yet another version of

Server Not Found
Error 404

Google uses the 4 servers to provide quadruple redundancy. One server is designed to handle the entire workload, at any time - with 4 servers, and each server running at 25% of full load. If any one server has to be temporarily taken out of service, they still have 3 servers - with each server running at 33% of full load.

During scheduled maintenance - and with triple redundancy, even two simultaneous emergencies (with 2 servers out of service, unscheduled) will not cause an immediate, major problem. This allows Google Engineers to schedule routine network maintenance as mutually convenient for everybody in their group - even considering the global need for Blogger services, on a 3600 x 24 x 7 x 56 basis.

There is one weakness of round robin DNS. All servers, in the set, have to be equally capable of performing reliably. A naive blog owner, including any additional or different server, in the set, risks having one server, responding to the round robin access - but providing an unsuitable answer.

mydomain.com.  3600 IN A 50.63.202.39
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.

What is 50.63.202.39?

ip-50-63-202-39.ip.secureserver.net (50.63.202.39)

50.62.0.0 - 50.63.255.255
GoDaddy.com, LLC GO-DADDY-COM-LLC (NET-160-153-0-0-1) 160.153.0.0 - 160.153.255.255

GoDaddy uses forwarding - not referral - to direct traffic. Here, some (not all, and not always) prospective blog readers see

Server Not Found
Error 404

Some blog owners make a second mistake - which compounds the first mistake.

mydomain.com.  3600 IN A 50.63.202.39
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 mydomain.com.

Here we see the "www" alias - which is what 95% of your direct traffic accesses - using the domain root for obtaining the address. Add to that the bogus server (in this example, "50.63.202.39"), and you will get a lot of complaints about sporadic connectivity problems.

Server Not Found
Error 404

This is so simple - if you only believe.

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.

>> Top

Custom Domains Purchase - "Buy a domain" Lacks The "Check Availability" Option

We're seeing a few reports from confused blog owners, in Blogger Help Forum: Something Is Broken, who want a non BlogSpot URL for their blog.

I have tried to follow the guide, but my page does not say the same as the guide.

Several blog owners, in trying to use "Add a custom domain" to buy a domain, are observing that there is no "Check Availability" sequence.

Right now, the "Add a custom domain" link in the Publishing wizard simply goes straight to the "Advanced settings" option. This conflicts with Blogger supplied instructions.

In Blogger, locate the Publishing area under the Settings tab. Settings to Publishing.

Then, click the link to add a custom domain name, enter the domain name you'd like, and click Check Availability.

Clicking on "Add a custom domain", we are immediately presented with "Advanced settings".

Right now, we're getting very terse advice from Blogger Support.

Blogger still supports custom domain hosting, though no longer offer an option to purchase domains within the product. To purchase a custom domain, please visit a third party registrar such as GoDaddy or eNom.

Until we hear more, I'll suggest use of eNom or GoDaddy, as advised. If you choose GoDaddy, you may be able to use the Blogger / GoDaddy DNS Setup wizard, to approximate the convenience of "Buy a domain". If you can't use the GoDaddy wizard, please note that the normal rules remain in full effect.

>> Top

Adding Ownership Verification For Your Custom Domain? Examine The Error Display

Sometimes, you have to step outside the box, to complete a Blogger blog task.

The task of adding domain ownership verification, to a custom domain purchased using "Buy a domain", is one example of stepping outside the box. I advise people that tweaking DNS settings, in general, is a task best undertaken by someone with "Advanced" experience with Blogger custom domain publishing.

Unfortunately, domains purchased using "Buy a domain" are occasionally subject to incomplete setup - and correction of an incomplete setup involves republishing the domain. And republishing the domain requires verification of domain ownership.

To a first time domain owner, the task of verifying domain ownership is surely a bit scary.

We have not been able to verify your authority to this domain.

This initial accusation is followed by the instructions

On your domain registrar's website, locate your Domain Name System (DNS) settings and enter the following two CNAMEs:

The challenge, for many, is getting to the Domain Name System (DNS) settings, aka the Zone Editor.

1. Login to Google Apps.
2. Find the instructions for logging in to the registrar's website.
3. Login to the registrar's website.
4. Find the registrar's Zone Editor wizard.

Having completed Steps #1 - #4, adding the "CNAME" is almost an anticlimax. See the instructions?

On your domain registrar's website, locate your Domain Name System (DNS) settings and enter the following two CNAMEs:

  Name, Label, or Host field    Destination, Target, or Points To field

  www                           ghs.google.com

  i7vgls457wxc                  gv-fbz2zptam3ucji.dv.googlehosted.com

Once you have access to the Zone Editor, look for "www", added by "Buy a domain". See how it's formatted, in the display?

• Add the second "CNAME", mirroring the format and syntax of the first.
• Note the example of the second, shown here as "i7vgls457wxc" - though when you setup your domain, you will surely see different values for both "i7vgls457wxc" and "gv-fbz2zptam3ucji.dv.googlehosted.com")
• Refresh the Zone Editor list, and compare the "www" and "i7vgls457wxc" entries.
• If you added the new entry properly, the format and syntax, of the two entries, will be identical.

Having successfully added your new "CNAME", go back to the Blogger Publishing wizard, and publish the blog to the domain. Finally, wait a few days for Transition to expire - and while you wait, plan what to do, next.

>> Top

The Task Of Forwarding A Domain Requires Experience, Persistence, And Research

I constantly advise Blogger blog owners to avoid forwarding, when setting up custom domain publishing.

In the rare cases where forwarding is actually required, not every blog owner reports success.

My blog now displays a non Google search page!

or worse

My blog now displays

404 Not Found

What did I do wrong??

Depending upon what setup work was done by the blog / domain owner, and what effort is required by the registrar, one may expect to see, quite predictably, either of the above errors.

When you just publish your blog to the primary domain, you're using the Blogger Publishing wizard.

When you forward a secondary domain to the primary domain, you're using the DNS Manager wizard provided by the registrar, for that secondary domain. Frequently, this is a 2 step process.

1. You use the DNS Manager for the secondary domain, and designate the primary domain as the forwarding target for this domain.
2. You setup a DNS address for the secondary domain URL, and target the redirection server - as provided by the DNS host.

Some wizards will handle both steps for you automatically, while others will require that you do both steps separately. I have had both experiences, when forwarding different domains using the GoDaddy DNS manager. You may need to experiment, here - or ask an experienced technician at the registrar, for advice.

If your registrar requires that you perform both steps separately, and you only do the first, your domain gets redirected to the redirection server. If you don't define a redirection target, you have a parked domain, similar to an expired domain - and your domain will serve the ads display page provided by the registrar.

If your registrar requires that you perform both steps separately, and you only do the second, your domain will be properly redirected from the redirection server - but the redirection server will not be defined, for your domain. If the redirection server isn't defined, the domain will be "404".

If your registrar does not provide explicit instructions - or if you use the domain manager wizard and get either of the above results, it may be time to contact a customer service representative. Using a third party registrar, or a third party DNS hosting service, you may have to improvise.

Forwarding a domain - when you must serve two domains (or more) from one blog - is simply not a task for the inexperienced.

>> Top

Confusion About Advice "If you bought your domain name from Blogger, you won't need to create a CNAME record."

To Blogger blog owners who want their new non BlogSpot URLs to display their blogs, this conflicting bit of advice provides only confusion and doubt.

If you bought your domain name from Blogger, you won't need to create a CNAME record.

That advice was written to advise the use of the Blogger "Buy a domain" wizard, which provides non BlogSpot URLs for Blogger blogs, through a simple 15 minute purchase process. In September 2012, that simple process changed, slightly.

If you are trying to re publish your blog to a non BlogSpot URL - and you are seeing an "Error 12" / "Error 32", or similar message in the Publishing wizard display - you need to add a second "CNAME" address to your domain.

The new "CNAME", added in September 2012, allows you to verify ownership of the domain to the Publishing wizard. Any time you re publish your blog to a non BlogSpot URL, you have to verify ownership. This prevents people who are not you from deviously publishing their Blogger blog to your domain.

If you are reading this, and you are the owner of any website which provides advice on how easy it is to purchase a non BlogSpot URL for a Blogger blog - and part of your advice mentions

If you bought your domain name from Blogger, you won't need to create a CNAME record.

Please, edit your instructions to reflect the reality of domain ownership verification.

If you are reading this, and you know of a blog or website which provides the confusing advice

If you bought your domain name from Blogger, you won't need to create a CNAME record.

let us know, below.

Try and reduce the confusion, when people have to re publish their blog, after using the Blogger Publishing wizard - or possibly after buying directly from a registrar. Help us, to help you.

>> Top

eNom Hosted Custom Domains Again Showing Intermittent Connectivity Issues

This week, we have a few reports in Blogger Help Forum: Something Is Broken, about active and mature domains, suddenly stopped working.

I have used my domain with no problems, since last year. Today, it suddenly stopped working, and the browser reports

Oops! Google Chrome could not find www.mydomain.com.

I asked my friends about my domain - and they tell me that my blog is inaccessible to them, also. I didn't change any settings - and it was fine, until last night.

As we reported last year, the Google partner registrar eNom occasionally has a problem with their DNS server complement. Right now, one of their DNS servers appears consistently bad.

Using a comprehensive Dig tool, we can observe a given domain, and compare the DNS addresses being served by all authoritative name servers for a given domain, in a single transaction.

Here's a hypothetical example, of what we're seeing right now, for several eNom hosted domains.

mycustomdomain.com@dns1.name-services.com.:

mycustomdomain.com.  1800 IN A 216.239.36.21
mycustomdomain.com.  1800 IN A 216.239.34.21
mycustomdomain.com.  1800 IN A 216.239.38.21
mycustomdomain.com.  1800 IN A 216.239.32.21

mycustomdomain.com@dns2.name-services.com.:

mycustomdomain.com.  1800 IN A 216.239.36.21
mycustomdomain.com.  1800 IN A 216.239.34.21
mycustomdomain.com.  1800 IN A 216.239.32.21
mycustomdomain.com.  1800 IN A 216.239.38.21

mycustomdomain.com@dns3.name-services.com.:

mycustomdomain.com.  1800 IN A 216.239.36.21
mycustomdomain.com.  1800 IN A 216.239.32.21
mycustomdomain.com.  1800 IN A 216.239.34.21
mycustomdomain.com.  1800 IN A 216.239.38.21

mycustomdomain.com@dns4.name-services.com.:

mycustomdomain.com.  1800 IN A 216.239.36.21
mycustomdomain.com.  1800 IN A 216.239.34.21
mycustomdomain.com.  1800 IN A 216.239.32.21
mycustomdomain.com.  1800 IN A 216.239.38.21

mycustomdomain.com@dns5.name-services.com.:

org.   3601 IN
 SOA dns1.name-services.com. info.name-services.com. 2010 10800 3600 604800 3600


www.mycustomdomain.com@dns1.name-services.com.:

www.mycustomdomain.com.  1800 IN CNAME ghs.google.com.

www.mycustomdomain.com@dns2.name-services.com.:

www.mycustomdomain.com.  1800 IN CNAME ghs.google.com.

www.mycustomdomain.com@dns3.name-services.com.:

www.mycustomdomain.com.  1800 IN CNAME ghs.google.com.

www.mycustomdomain.com@dns4.name-services.com.:

www.mycustomdomain.com.  1800 IN CNAME ghs.google.com.

www.mycustomdomain.com@dns5.name-services.com.:

org.   3601 IN
 SOA dns1.name-services.com. info.name-services.com. 2010 10800 3600 604800 3600

Right now, it appears that server "dns5" is consistently broken.

It's possible that this problem will affect more eNom customers, as the day progresses, cached DNS addresses expire, and readers of various eNom hosted domains request DNS addresses. I hope that eNom Customer Service can react to this problem more promptly than they have reacted to the immediately previous problem.

>> Top

How To Unmap Google Sites To Solve "Another blog or Google Site is already using this address."

The literal cause of the error "Another blog or Google Site is already using this address." is that the Google Sites service is mapped to the address in question, in the Google domain services mapping database.

Some help articles published on the Internet imply that Sites mappings are the only cause of this error. This misconception creates some of the confusion associated with the error. Sites is not the only service in the services mapping database - but it is the only service with web address mappings.

The Sites service contains both service address, and web address, mappings - and both mappings can cause this problem. This oddity creates complexity, and makes a linear check list impossible, when using Google Apps to clear the error - as well as diagnosing the error, in a typical dialogue in Blogger Help Forum: Something Is Broken.

When the Sites service is suspected as the cause of "Another blog or Google Site is already using this address.", one must check both the Service Address Mapping, and the Web Address Mappings, in the Sites service.

Note that the presence of the mappings is not directly affected by the presence of the service wizards, on the desktop of the Google Apps account which you are using. Neither deleting the Apps account, nor uninstalling a given service wizard from the desktop, will immediately reset the mappings for that service, from the database.

If not present on the desktop, the Sites service must be first installed and activated, using the dashboard "Get more apps and services" link.

The Sites service address mapping, like all other services, can be examined and reset using the CustomURL form in Google Apps, as well as "Change URL" in the "General" tab, in the Sites Settings menu. The web address mappings can only be examined and reset using the "Web Address Mapping" tab, in the Sites Settings menu.

1. Select the "Web Address Mapping" tab, in the Sites Settings menu.
2. Select all addresses mapped, and click on "Delete Mapping(s)".
3. Click on "Yes" in the "Are you sure" popup.

A Sites service address mapping, like other service address mappings, can sometimes be diagnosed in a simple "302 Moved Temporarily" redirect, in a typical HTTP trace.

Sending request:

GET / HTTP/1.1
Host: www.letthykingdomcome.com
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:18.0)
 Gecko/20100101 Firefox/18.0
Referer: http://www.rexswain.com/httpview.html
Connection: close

• Finding host IP address...
• Host IP address = 74.125.129.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)
Content-Type:·text/html;·charset=UTF-8(CR)(LF)
Location:·http://sites.google.com/a/letthykingdomcome.com/
 sites/system/app/pages/meta/domainWelcome(CR)(LF)

A Sites web address mapping is not always so easy to diagnose - and may be the reason behind the fact that some HTTP traces end with the blog owner reporting "Another blog or Google Site is already using this address.", and an HTTP trace simply showing the generic 404 Not Found.

Sending request:

GET / HTTP/1.1
Host: www.markhamdesign.co.uk
User-Agent: Mozilla/5.0
 (Windows NT 5.1; rv:19.0) Gecko/20100101 Firefox/19.0
Referer: http://www.rexswain.com/httpview.html
Connection: close

• Finding host IP address...
• Host IP address = 216.239.32.21
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...
Receiving Header:
HTTP/1.1·404·Not·Found(CR)(LF)

A Sites "Web Address Mapping" can include an address which is mapped outside Google Apps. This creates a mapping which can't be managed using Google Apps.

If you own a domain and have access to change the CNAME record, you can map any site created in Google Sites outside of Google Apps (for example, sites.google.com/site) to a custom URL

Sending request:

GET / HTTP/1.1
Host: www.medtechpedia.com
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:19.0) Gecko/20100101 Firefox/19.0
Referer: http://www.rexswain.com/httpview.html
Connection: close

• Finding host IP address...
• Host IP address = 74.125.129.121
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...
Receiving Header:
HTTP/1.1·200·OK(CR)(LF)

<body·xmlns="http://www.google.com/ns/jotspot"·id="body"·class="·en············">(LF)
<script·src="//www.gstatic.com/caja/5246m/caja.js">·</script>(LF)
<script·src="http://www.gstatic.com/sites/p/926884/system/js/jot_caja.js">·</script>(LF)
<div·id="sites-page-toolbar"·class="sites-header-divider">(LF)
<div·xmlns="http://www.w3.org/1999/xhtml"·id="sites-status"·class="sites-status"·style="display:none;"><div·id="sites-notice"·class="sites-notice"·role="status"·aria-live="assertive">·</div></div>(LF)
</div>(LF)
<div·id="sites-chrome-everything-scrollbar">(LF)
<div·id="sites-chrome-everything">(LF)
<div·id="sites-chrome-page-wrapper"·style="direction:·ltr">(LF)
<div·id="sites-chrome-page-wrapper-inside">(LF)
<div·xmlns="http://www.w3.org/1999/xhtml"·id="sites-chrome-header-wrapper"·style="">(LF)
<table·id="sites-chrome-header"·class="sites-layout-hbox"·cellspacing="0"·style="">(LF)
<tr·class="sites-header-primary-row"·id="sites-chrome-userheader">(LF)
<td·id="sites-header-title"·class=""><div·class="sites-header-cell-buffer-wrapper"><h2>
  <a·href="http://sites.google.com/site/medtechpedia/"·dir="ltr"·id="sites-chrome-userheader-title">MedTechPedia</a></h2></div></td><td·class="sites-layout-searchbox·"><div·class="sites-header-cell-buffer-wrapper"><form·id="sites-searchbox-form"·action="/system/app/pages/search"><input·type="hidden"·id="sites-searchbox-scope"·name="scope"·value="search-site"·/><input·type="text"·id="jot-ui-searchInput"·name="q"·size="20"·value=""·aria-label="Search·this·site"·autocomplete="off"·/><div·id="sites-searchbox-button-set"·class="goog-inline-block"><div·role="button"·id="sites-searchbox-search-button"·class="goog-inline-block·jfk-button·jfk-button-standard"·tabindex="0">Search·this·site</div></div></form></div></td>(LF)
</tr>(LF)
<tr·class="sites-header-secondary-row"·id="sites-chrome-horizontal-nav">(LF)
<td·colspan="2"·id="sites-chrome-header-horizontal-nav-container">(LF)
<div·class="sites-header-nav"><ul·class="sites-header-nav-container-tabs"><li·class="current"><a·class="sites-navigation-link·current"·href="/home">Home</a></li><li·class="unselected"><a·class="sites-navigation-link·unselected"·href="/introduction-to-medical-technology">Introduction·to·Medical·Technology</a></li></ul><div·style="clear:·both;"></div></div>(LF)
</td>(LF)
</tr>(LF)
</table>·(LF)
</div>·

>> Top

How To Solve "Another blog or Google Site is already using this address."

Of all of the problems that are typically reported, in Blogger Help Forum: Something Is Broken, surely the most frustrating has to be

Another blog or Google Site is already using this address.

One of the reasons for the frustration is that this is not a descriptive error - it's more of a symptom - and this symptom has a number of causes. Since many Blogger blog owners don't understand the principles of problem solving, the solutions for this error may not be obvious.

The monolithic message "Another blog or Google Site is already using this address." is actually a symptom of a number of possible problems.

Some time ago, I identified three categories of problems, which cause the message to be displayed.

1. The URL in question is actually in use, with another blog already published to that domain URL.
2. The DNS addresses are improperly setup, and not pointing to the correct Google servers.
3. There are broken / duplicate pointers, which affect the domain, in the Google internal database.

Check For A Blog Already Published To The Address

If there is a blog already published to the URL, and you control both blogs, make a simple decision - which blog to publish, to the URL in question. If necessary, a second blog can be published to a different host in the domain, and setup a domain cluster. In some cases, a previous domain owner may have published a blog, which you won't control, to the domain.

Check The DNS Address Setup

Having eliminated or solved the possibility of multiple blogs, check and - if necessary - correct the DNS addresses setup for the domain. There are three DNS address models - with one, asymmetrical, being involved with over 99% of the blogs reported with this problem. There is simply no alternative to "CNAME" forwarding, when publishing a blog to a custom domain.

Check For Service Redirections

With the DNS addresses corrected - and DNS propagation latency allowed for - diagnose the problem using a series of HTTP traces. Here, we'll generally see a number of possible redirections.

1. Calendar.
2. Drive and Docs.
3. Email.
4. Sites.
5. Start Page.

If the HTTP traces do not indicate a specific service, you may have an indeterminate case of database corruption.

When dealing with service redirections, start by establishing access to the Google Apps domain administrator desktop. If the domain was purchased in 2013 or later, you'll have use of a basic function Apps account. You'll use two Apps desktop wizards - "Organization & users" and "Settings".

1. Use "Organization & users", to install and activate any service.
2. Use "Settings" to disable mappings, and to uninstall any service.

Named Service Redirection

For a named service redirection:

1. If necessary, install and activate the service.
2. Delete the mappings for the service.
3. Uninstall the service.

Database Corruption Or Unknown Service Redirection

If a specific service is not identified in the HTTP traces, check the "Change URLs for multiple services" display, which is accessible from any "Change URL" service wizard.

1. Select any service, in the "Settings" wizard, and the "Change URL" link for that service.
2. Click on "Change URLs for all domain services".
3. Examine the "Change URLs for multiple services" display, and select the custom mapping, for any service with the default mapping (top) address selected. If any service entry is changed, click "Continue".
4. For each service with mapping which was just changed:
   • If necessary, install and activate the service.
   • Uninstall the service.

Just read about the details, take it one step at a time - and allow time to complete the entire task, carefully.

>> Top

How To Use Google Apps To Solve "Another blog or Google Site is already using this address."

The Google domain services database lets one or more Blogger blogs, and / or various Google services, be packaged as part of a domain - giving your organisation its own virtual web server.

Google Apps is used to manage this virtual web server, as you install and un install various domain services. Sometimes a domain, newly setup in Google after the domain has been purchased from a registrar, will have one or more addresses unexpectedly mapped to various Google services. This will be inconvenient to the blog owner, who may wish to use a given URL for a Blogger blog.

The most common cause of the error "Another blog or Google Site is already using this address." involves unexpected mappings, in the Google domain database.

When your domain has unwanted mappings, you'll need to use the Google Apps domain administrator desktop, and various utilities there, to remove the mappings and reset the services. To start, you'll need access to the Google Apps desktop for the domain administrator. For domains recently purchased using Blogger or Google wizards, you'll have a limited function domain administrator desktop.

You'll use two Apps desktop wizards - "Organization & users" and "Settings".

• Use "Organization & users", to install and activate a service.
• Use "Settings" to disable / remove mappings, and to disable / uninstall a service.

Install And Activate Services

Use "Organization & users" - "Services", to activate the various services.

• To install a service, click on "Dashboard", find "Common tasks" at the bottom left, and click on "Get more apps and services". Click on "Add it now", for the needed service.
• To activate a service, go to "Organization & users" - "Services", and look under "Core Google Services" or "Additional Services", for the service in question - and click on the coloured toggle switch as necessary. Then click on "Save changes".

Remove Mappings

Use the Settings wizard, for the service in question - to add and remove address mappings, and to deactivate services. Each different service, listed in Settings, has a different set of menus, and different options.

We currently know of 5 services which can be mapped to a domain, which may interfere with publication of a Blogger blog to a domain address. Any problem service, currently mapped to the default (top) address, will need to be changed to map to the custom (bottom) address.

1. Calendar.
2. Drive and Docs.
3. Email.
4. Sites.
5. Start Page.

To remove address mappings for Calendar:

1. Click on "Calendar", then the "General" tab, then "Change URL" for "Web address".
2. If necessary, select the custom mapping (bottom) address, and click "Continue".
3. If you change the Calender mapping, remember to uninstall Calender.

To remove address mappings for Drive and Docs:

1. Click on "Drive and Docs", then the "General" tab, then "Change URL" for "Web address".
2. If necessary, select the custom mapping (bottom) address, and click "Continue".
3. If you change the Drive and Docs mapping, remember to uninstall Drive and Docs.

To remove address mappings for Email:

1. Click on "Email", then the "General Settings" tab, then "Change URL" for "Web address".
2. If necessary, select the custom mapping (bottom) address, and click "Continue".
3. If you change the Email mapping, remember to uninstall Email.

To remove address mappings for Sites, some extra effort may be required:

1. Click on "Sites", then the "General" tab, then "Change URL" for "Web address".
2. If necessary, select the custom mapping (bottom) address, and click "Continue".
3. Select the "Web Address Mapping" tab.
4. Select all addresses mapped, and click on "Delete Mapping(s)".
5. Some Sites mappings can only be diagnosed, and reset, outside Google Apps.
6. If you change any Sites mapping, remember to uninstall Sites.

To remove address mappings for Start Page:

1. Click on "Start Page", then "Change URL" for "Web address".
2. If necessary, select the custom mapping (bottom) address, and click "Continue".
3. If you change the Start Page mapping, remember to uninstall Start Page.

The CustomURL Wizard

Besides the multiple Sites mappings (in "Web Address Mapping"), it may be possible to use the "CustomURL" wizard, which will list all active services and current mappings. The CustomURL wizard is accessed from any "Change URL" wizard.

1. Click on "Change URLs for all domain services".
2. Examine the "Change URLs for multiple services" display, and disable any references to the default mapping. Select the custom mapping (bottom) address, for any service with the default mapping (top) address selected. If any service entry was changed, click "Continue".
3. For each service with mapping which was changed:
   • If necessary, install and activate the service.
   • Uninstall the service.

Disable / Uninstall Services After Changing Mapping

If you did change or delete any mappings, whether using CustomURL ("Change URLs for multiple services") or an individual service wizard ("Change URL" / "Web Address Mapping"), the final step is to disable or uninstall each service for which you changed or deleted mappings. If you do intend to use any named service, re install it later - after you get your custom domain working.

To uninstall Calendar, click on "Calendar", then the "General" tab. Click on "Uninstall Calendar", next to "Uninstall service".

To uninstall Drive and Docs, click on "Drive and Docs", then the "General" tab. Click on "Uninstall Drive and Docs", next to "Uninstall service".

To uninstall Email, click on "Email", then the "General Settings" tab. Click on "Uninstall Email", next to "Uninstall service".

To uninstall Sites, click on "Sites", then the "General" tab. Click on "Uninstall Sites", next to "Uninstall service".

To disable Start Page, click on "Start Page", then on "Disable Start Page", next to "Disable service".

>> Top

When You Publish Your Blog To A Custom Domain, Almost Always Publish To The "www" Alias

Of all of the known problems with Blogger, in general - and of the known problems with Blogger / Google Custom Domain Publishing, specifically - surely the most frustrating single problem starts with the well known monolithic error

Another blog or Google Site is already using this address.

The most frequently seen solution to this problem, contrary to the opinions expressed in some blogs and websites, starts with correction of the domain DNS addresses. But even after careful DNS address correction, some blog owners still report the well known "Another blog ..." error.

Maybe 99.99% of the custom domain published blogs use what I call an asymmetrical DNS address configuration.

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.

Note the restriction with the asymmetrical configuration, sometimes overlooked.

With an asymmetrical configuration, you may not publish to the domain root. Your only valid choice is to publish to "www.mydomain.com", and select "Redirect mydomain.com to www.mydomain.com". If you publish to "mydomain.com", you will eventually see

Blogs may not be hosted at naked domains.

or maybe a well known monolithic error

Another blog or Google Site is already using this address.

The conclusion is simple. Unless you intentionally created a symmetrical or non root virtual host address configuration, always publish to the "www" alias.

>> Top

Adding The Domain Ownership Verification "CNAME", For A Non Root Virtual Host

Now that the new required custom domain publishing ownership verification feature has been out for several months, we are seeing it used in domains with multiple virtual hosts.

A few blog owners are even publishing their blogs to non root virtual hosts - and here we are seeing a new reason for a persistent Error 12 / 32, which just can't be solved.

I have followed all of the instructions, and I am still seeing Error 12. Help!

The "Advanced settings" Error 12 instructions - now provided on screen instead of requiring the blog owner to open an external "Settings instructions" document - require careful examination.

We have to look very closely at this variation on the publishing instructions, when publishing to a non root virtual host.

Advanced settings

http://www.blog.mydomain.com

We have not been able to verify your authority to this domain. Error 12.
On your domain registrar's website, locate your Domain Name System (DNS) settings and enter the following CNAMEs:

  Name, Label, or Host field    Destination, Target, or Points To field

  www                           ghs.google.com

  xxxxxxxxxxxx               gv-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.domainverify.googlehosted.com.

See our detailed instructions on providing CNAMEs for various registrars or see the full settings instructions for more details.

Taking these instructions at face value, and adding a "CNAME" record of relative Name value "xxxxxxxxxxxx" to verify the publishing address of "www", the blog owner is going to continue to see an "Error 12" or "Error 32" for a long time.

We have to look, very carefully, at the "Advanced settings" publishing address - in this case

www.blog.mydomain.com

In the registrar's Zone Editor (aka "Domain Manager" wizard), we see the Name value entered as an address relative to the domain root.

• With "www" entered for the Name, this provides a published address of "www.mydomain.com".
• With "www.blog" entered, this provides a published address of "www.blog.mydomain.com".

The Name value, for both "CNAME"s, as specified in the "Advanced settings" instructions, is relative to the domain root.

• A Name of "www", to provide a published address of "www.blog.mydomain.com", should be entered as "www.blog" in the Zone Editor.
• Similarly, a Name of "xxxxxxxxxxxx", to provide a published address of "www.blog.mydomain.com", should be entered as "xxxxxxxxxxxx.blog" in the Zone Editor.

Entering the domain ownership verification "CNAME" relative to the published URL allows non root virtual hosts to be used, in the domain, without chance of conflict.

• To publish to "blog.mydomain.com", we add a domain ownership verification "CNAME" of "xxxxxxxxxxxx.mydomain.com" (with the proper value of "xxxxxxxxxxxx").
• To publish to "www.mydomain.com", we add a domain ownership verification "CNAME" of "xxxxxxxxxxxx.mydomain.com" (with the proper value of "xxxxxxxxxxxx").
• To publish to "www.blog.mydomain.com", we add a domain ownership verification "CNAME" of "xxxxxxxxxxxx.blog.mydomain.com" (with the proper value of "xxxxxxxxxxxx").

We simply have to read the "Advanced settings" instructions, and enter the Name values in the Zone Editor, considering the context of the instructions.

>> Top

After You Publish Your Blog To A Custom Domain, Should You Update Internal Links?

One interesting question, which comes up from time to time in Blogger Help Forum: How Do I?, is about Custom Domain Publishing - and what to do, after Transition completes.

Now that my blog is successfully transitioned to the domain URL, should I update the internal blog links, in the post contents?

This is a question that deserves some thought. From an aesthetic sense, it makes sense to do this - hoping that you will be paying for the domain, for eternity. But, is it worth the effort?

There are several issues, which may be relevant, when asking the question, phrased above.

Remember that updating the internal links is a manual effort - this has to be done on a post by post basis.

• How much time do you have to spend, updating the link URLs?
• How much effort will this take? How many old posts do you have, with how many internal links?
• How likely are you to go ever back to the BlogSpot URL?

Remember that one of the features of custom domain publishing is the DNS Based redirect, of the BlogSpot URL, to the domain published URL. This is an automatic feature, it's total and immediate - and it will continue to work, only as long as the domain continues to work.

As you continue to publish posts in your blog, your new internal links will use the domain URL - unless you manually convert each one, as you edit each post. If you ever opt to publish back to BlogSpot, all of the links, pointing to the domain URL, will be problems - when the domain stops redirecting. If you spend time manually updating each link now, that's the same amount of time that you'll have to spend reverting the updated links, when you publish back to BlogSpot.

Remember that your BlogSpot URL continues to operate, forever - regardless of the domain published URL.

From what I can tell of the DNS infrastructure used by custom domain published blogs, the domain DNS settings are cached locally, for all readers of any given custom domain. If the BlogSpot to domain redirect is similarly cached, it's unlikely that there are any reader experienced performance issues, from people reading blogs and clicking on BlogSpot targeted internal links, that redirect to custom domain URLs.

As far as I can tell, when thinking about this carefully, there is no real reason - other than esthetics - to ever update the BlogSpot based internal links, to directly point to the domain URL. Spend your time, after Transition has completed, profitably. Work on the blog, and get it re indexed, under the new URL.

>> Top

To Republish A Custom Domain, You Do Have To Add A Second "CNAME"

One of the challenges of using Blogger involves following the instructions.

Blogger / Google personnel provide Help instructions which are not always updated - sometimes they simply write a new Help instructions document, leaving the old Help instructions in place.

The policy of leaving old Help instructions in place - and sometimes conflicting with new displays and procedures - occasionally causes confusion. One scenario where this causes a problem is in publishing or re publishing a blog to a custom domain.

I've seen instructions that when you buy a domain from Blogger / Google, using "Buy a domain", you won't need to create a CNAME record.

One of the advantages of using "Buy a domain" is the ease of setup. If you use "Buy a domain", you don't have to bother with any of the details. This is generally - but not always - true.

Sometimes, even using the "Buy a domain" wizard can later present a problem.

One of the known problems with "Buy a domain" results in a partially setup domain - and with a partially setup domain, you may have to re publish the blog to the domain, to get the new domain to work completely.

To re publish the blog, you have to verify your ownership of the domain - even if you previously used "Buy a domain". And the additional step of adding a second "CNAME" overrides the old Blogger Help instruction

If you bought your domain name from Blogger, you won't need to create a CNAME record.

When you are instructed to re publish the blog using "Advanced settings", that 's what you must do. And, when "Advanced settings" contains instruction to add a second "CNAME", then please - add a second "CNAME".

>> Top

Blog Owners Seeing "Error 14" Or Similar Symptom, When Attempting To Publish To A Custom Domain URL

We're seeing a small but steady flood of reports, in Blogger Help Forum: Something Is Broken, from blog owners attempting to publish their blogs using a custom domain URL.

I am not able to redirect my blog from blogspot to my own domain! Blogger is giving me the error

We have not been able to verify your authority to this domain. Error 14.

This specific problem has been observed numerous times in the past, ever since Blogger added the domain ownership verification process to the custom domain publishing feature. Problem reports require careful diagnosis, involving examination of the basic DNS addresses setup with the registrar, to verify the "Error 14" as the primary problem.

Because careful diagnosis is required, for each case reported, we're not adding a Rollup Discussion in the forum. Instead, we request that each blog owner, observing this problem, post her / his problem report in a topic started for that purpose, by himself / herself only. This will allow us to inventory this problem properly, and assist Blogger Engineering in isolating and fixing this problem promptly, so the blog owners can get on with the after publishing process.

Reports of this problem appear to have started in volume late Saturday, 11/17, Pacific time - though some reports, examined in detail, mention the problem initially observed several days ago. The initial volume of the problem appeared to come from SouthEast Asia - but as additional reports were posted, we see Europe and the Americas apparently represented.

Blogger Engineering is now aware of the problem, and will investigate. We'll continue to monitor the forum topics, and to post an initial advisory FAQ, as a response to the reports observed - when reports contain clear evidence of the "Error 14" being a primary symptom. Please monitor that FAQ, and this post, for any ongoing updates.

>> Top