Enom: Fix Your Dns Servers!

For over 2 months, we've been seeing reports from spider web log owners who published their blogs to custom domains, amongst domain DNS hosted yesteryear eNom, inwards Blogger Help Forum: Something Is Broken.

I bought my domain cite through Blogger,last week. It is beingness hosted yesteryear eNom. Ever since I bought it roughly of my followers, together with sometimes myself, can't access my site. There is either a DNS search or a "Ooops, Google Chrome can't find..."

I tried contacting eNom, together with they said they tin run across my site together with that all of my settings are correct. They enjoin it must live Google's problem.

The keyword hither is "sometimes".

Ever since I bought it roughly of my followers, together with sometimes myself, can't access my site.

Influenza A virus subtype H5N1 uncomplicated Dig, purchased using "Buy a domain", volition live asymmetrical aka "Google Apps".

enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.32.21 enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.34.21 enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.36.21 enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.38.21 www.enomhosteddomain.com. 1800 IN CNAME ghs.google.com. 

The problem, which non together with then many people appreciate, is that eNom uses multiple DNS servers, mayhap geographically separated. This is normal DNS hosting technique, together with guarantees redundancy if 1 information middle goes offline.

However, for redundancy to work, all DNS servers accept to live kept consistently synchronised. If nosotros attempt out the five eNom DNS servers individually, we volition oftentimes run across discrepancies.

enomhosteddomain.com @ dns1.name-services.com.:  enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.32.21 enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.34.21 enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.36.21 enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.38.21 enomhosteddomain.com. 3600 IN NS dns1.name-services.com. enomhosteddomain.com. 3600 IN NS dns2.name-services.com. enomhosteddomain.com. 3600 IN NS dns3.name-services.com. enomhosteddomain.com. 3600 IN NS dns4.name-services.com. enomhosteddomain.com. 3600 IN NS dns5.name-services.com.  enomhosteddomain.com @ dns2.name-services.com.:  enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.34.21 enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.38.21 enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.32.21 enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.36.21  enomhosteddomain.com @ dns3.name-services.com.:  com.   3601 IN SOA dns1.name-services.com. info.name-services.com. 2010 10001 1801 604801 181  enomhosteddomain.com @ dns4.name-services.com.:  enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.32.21 enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.36.21 enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.34.21 enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.38.21  enomhosteddomain.com @ dns5.name-services.com.:  enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.32.21 enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.34.21 enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.36.21 enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.38.21 enomhosteddomain.com. 3600 IN NS dns1.name-services.com. enomhosteddomain.com. 3600 IN NS dns2.name-services.com. enomhosteddomain.com. 3600 IN NS dns3.name-services.com. enomhosteddomain.com. 3600 IN NS dns4.name-services.com. enomhosteddomain.com. 3600 IN NS dns5.name-services.com.   www.enomhosteddomain.com @ dns1.name-services.com.:  www.enomhosteddomain.com. 1800 IN CNAME ghs.google.com.  www.enomhosteddomain.com @ dns2.name-services.com.:  www.enomhosteddomain.com. 1800 IN CNAME ghs.google.com.  www.enomhosteddomain.com @ dns3.name-services.com.:  com.   3601 IN SOA dns1.name-services.com. info.name-services.com. 2010 10001 1801 604801 181  www.enomhosteddomain.com @ dns4.name-services.com.:  www.enomhosteddomain.com. 1800 IN CNAME ghs.google.com.  www.enomhosteddomain.com @ dns5.name-services.com.:  www.enomhosteddomain.com. 1800 IN CNAME ghs.google.com.  

This is 1 of the to a greater extent than subtle discrepancies, which I accept observed, inwards the yesteryear distich months - alone DNS Server #3 is out of synch, inwards this case. But that's enough, to brand the domain unreliable.

The work is intermittent. All all of a abrupt my site loads, only 10 minutes agone it didn't.

That's one eNom customer, out of over a dozen, which I accept documented. And that's 1 eNom customer, who should live complaining, to someone to a higher house eNom Customer Service.

eNom: cook your servers!

---

(Update 2012/07/03): Suspicion that the work is related to Anycast DNS led me to a bud, who is a immature homo TC, together with a network skillful inwards India, together with who provided an intriguing spider web log post, neatly diagnosing the underlying problem. It appears that eNom server monitoring policies may live a fleck superficial.

---

---

Use these links, for convenient reference:

• Discrepancy suspected.
• Discrepancy confirmed.

---

>> Top

Ownership Verification Is Non A Measure Process

With the latterly restored custom domain publishing feature, as well as the novel domain ownership verification requirement, comes diverse queries from spider web log owners unable to verify domain ownership, as well as to expose their spider web log to their custom domain.

Can I role a "TXT" file, instead of a "CNAME"? My registrar suggests this every bit an alternative.

and

Why create I involve this? My domain was working, precisely fine, earlier I had to re expose the blog!

Not all spider web log owners sympathize the historical involve for verifying domain ownership.

The minute "CNAME" won't locomote required, inwards all cases.

If you lot don't run into instructions for adding a minute "CNAME", focus your efforts on getting the domain working, amongst righteous base of operations DNS addresses.

Ownership verification, allowing 1 to setup a given human relationship betwixt diverse Internet resources, varies according to the involve of the application which uses the Internet resources inwards question.

Domain ownership verification, to supply urgently needed custom domain security, is but 1 illustration of ownership verification, inwards general.

• If you lot convey file / folder command of a spider web site, you lot may locomote able to add together a specific named file, to the website. The application inwards inquiry tin banking concern gibe for the presence of the required file (possibly 1 amongst a complex name).
• Some applications such every bit Webmaster Tools can, alternatively, role a meta tag inwards the spider web log header, to verify spider web log ownership. Again, the tag volition convey a complex advert / value.
• To verify domain ownership, Blogger requires you lot to install a unique "CNAME" every bit a DNS address into your domain. The "CNAME" volition incorporate 2 complex values, provided entirely to the spider web log / domain owner.

In either case, the complex values supply an encrypted certificate, which is specific to the application as well as to the spider web log / website, which is provided entirely to the possessor of the spider web log / domain / website.

The named file is a elementary solution - both to setup as well as to verify - but using it requires that the spider web log / website possessor convey the might to setup a specific named file, inwards a specific folder, containing the certificate. Blogger does non supply file / folder control, as well as therefore that solution is out - for whatever application which is to locomote used amongst Blogger blogs.

Applications (such every bit Webmaster Tools) which locomote amongst Blogger blogs, as well as similar websites, tin role meta tag verification. This requires that the spider web log possessor add together a meta tag inwards the spider web log header, amongst a complex tag advert / value. The tag advert / value contains the certificate inwards question.

Blogger blogs tin role neither a named file, nor meta tags, for domain ownership verification. There is no domain header, where meta tags could locomote installed - as well as again, Blogger does non supply file / folder control.

To verify domain ownership, Blogger requires the domain ownership certificate to locomote installed every bit a unique "CNAME" DNS address. The complex values inwards the "Name" as well as "Destination" values of the "CNAME" incorporate the encrypted ownership certificate. Since the specific certificate values, for each unlike domain, are provided to the spider web log possessor (in the "settings instructions" document) - as well as the "CNAME" tin entirely locomote installed past times the domain possessor - when the proper "CNAME" exists, the spider web log possessor as well as domain possessor are certified to locomote 1 person.

The unfortunate work amongst "CNAME" based domain ownership verification is that not all registrars tin supply the required "CNAME"s, as well as tin supply "CNAME"s amongst long "Name" or "Destination" values. This does non hateful that the Blogger solution, for domain ownership verification, is faulty.

It's possible that Blogger Engineering has considered a minute choice for domain ownership verification, which volition locomote added when - or later on - the "Buy a domain" magician is updated to back upward automatic domain ownership verification. It's too possible that spider web log owners, who role specific registrars which are unable to supply the required "CNAME", volition locomote forced to abandon their electrical flow registrar.

Whatever the case, it's probable that the "CNAME" based domain ownership certificate was the best possible solution, to solve the urgent safety problem, as well as permit custom domain publishing to locomote restored concluding week.

No Immediate Solution For 1And1 Customers Amongst Unverifiable Custom Domains

Since Blogger restored Custom Domain Publishing concluding month, with the novel domain ownership verification requirement, at that topographic point convey been a few complaints from customers of closed to registrars who only can't render the required DNS address record for ownership verification.

My registrar says that I can't convey ii "CNAME" records inwards the same subdomain.

and

My registrar's domain director magician displays an fault maxim "Address also long.", when I crusade to add together the "CNAME".

Blog owners contacting the registrar, in addition to scream for for help, are by in addition to large told

That's Blogger's problem!

---

(Update 2012/11): Blogger Engineering has provided a workaround for this problem, alongside whatever uncooperative registrar, such equally 1And1 - use of a (free) 3rd political party DNS host.

---

What non all spider web log owners realise is that the novel "CNAME" must live on only that - at that topographic point is no substitute here.

Some of the to a greater extent than patient spider web log owners convey made diverse suggestions, to teach us moving towards a solution.

1. Blogger Support needs to run alongside the employment registrars, in addition to convince them to better their service.
2. Blogger Support needs to render an alternate ownership verification physical care for - perhaps equivalent to the Google Webmaster Tools meta tag verification procedure.
3. Blogger Support needs to build clean upwardly their "CNAME" setup instructions, in addition to take away scream of the employment registrars - hence hereafter spider web log owners won't select these registrars to host their domains.

About 3/4 of the employment reports convey come upwardly from customers of 1And1. Using that registrar equally a starting point, I contacted Blogger Support in addition to suggested the 3 alternatives, outlined above. The Blogger Engineer responding seemed to mean value that exclusively proposition #3 - cleanup of the per registrar "CNAME" improver instructions was straight off possible.

It's possible, then, that nosotros volition eventually run into less employment reports from 1And1 customers - in addition to hopefully others - equally Blogger Engineering cleans upwardly their domain setup instructions. The electrical current customers of uncooperative registrars, unfortunately, are unlikely to run into relief, for the close future.

This is an unfortunate province of affairs for these 1And1 customers. The best solution for them is to movement domain registration to another, to a greater extent than helpful, registrar. Unfortunately, most registrars don't permit domain registration transfers straight off subsequently initial buy - waiting periods of 30, or fifty-fifty threescore - days are normal. And domain registration fees are non refunded.

This leaves novel 1And1 customers, in addition to similar victims, alongside several options - none of them good. First, publish the spider web log dorsum to BlogSpot, hence the spider web log tin live on accessed past times existing readers.

• Wait thirty - threescore days, alongside the domain dead, hence transfer domain registration to a to a greater extent than helpful registrar in addition to activate.
• Purchase a minute domain, from a to a greater extent than helpful registrar.
• Forget virtually custom domain publishing.

The latter alternative has motivated several victims to select a quaternary alternative.

• Move their spider web log hosting to a different service.

None of this tin live on expert for Blogger's reputation.

>> Top

Use 3Rd Political Party Dns Servers, For 1And1 Domains

Not all registrars are able to back upwards the novel Blogger domain ownership verification requirement.

Some registrars won't permit a minute "CNAME" inwards the same subdomain - together with others can't handgrip the excessively long target address. Ever since Blogger added domain ownership verification, we've been seeing complaints from around spider web log owners, who direct maintain purchased domains direct from registrars who can't supply the required DNS addresses on their servers.

Even though non all registrars direct maintain DNS servers that volition supply the correct DNS address entries, almost registrars volition permit us to piece of work 3rd political party DNS servers. The piece of work of publicly available DNS servers, which tin give the sack supply the required DNS addresses, volition eliminate the necessitate to transfer domain registration - when the registrar is unable to supply the correct DNS addresses, using their ain servers.

If you're trying to setup your domain, purchased from 1And1 or a like registrar, y'all necessitate exclusively to setup a suitable 3rd political party DNS server.

If your registrar limits their services, piece of work a 3rd political party DNS host.

Use of a 3rd political party DNS host volition also help victims of the eNom DNS Infrastructure problem - together with those who purchased Name Registration, direct from the registrar.

An explanation of the solution is provided, past times Blogger Engineers.

Marc Ridey, of Blogger Engineering, provides How to setup your Blogger spider web log amongst a custom domain from 1and1.com, together with adds iii elementary steps to the normal 3rd political party registrar domain setup process.

1. Setup a (free) ClouDNS account.
2. Setup your normal DNS addresses (plus the domain ownership verification "CNAME", if required) inwards ClouDNS, using the ClouDNS Domain Manager wizard.
3. Setup your domain, using your registrar's domain managing director wizard, pointing to the ClouDNS DNS servers.

Do each step, ane at a fourth dimension - together with banking venture gibe your work.

When y'all update DNS addresses, such equally adding additional hosts, together with ownership verification, y'all piece of work the ClouDNS Domain Manager wizard.

Note the caveat, for advanced domain owners.

If y'all are using your 3rd political party registrar because y'all direct maintain non Blogger services (a spider web site, email, files, or other service) hosted past times the registrar, delight banking venture complaint the alert past times Marc!

Warning: If y'all are using 1and1 hosting services to display a website equally good equally a Blogger blog, these instructions volition disable the website. Please post a comment amongst your website address together with I'll banking venture gibe how these instructions must last updated. If you're using eMail, scream back to consummate the optional eMail step.

Note that ClouDNS, when setup, may offering the choice to redirect the domain origin (aka "naked domain") to the "www" alias (or whatever DNS address y'all may setup). For best results, ignore that option, together with piece of work the Blogger or Google Apps redirect.

There are yet exclusively three acceptable DNS models - piece of work of ClouDNS, or whatever like 3rd political party DNS host, volition non alter that.

This may non last a perfect solution - merely it volition create a stable domain.

This may non last an ideal solution for the work - it introduces a combat of complexity into the domain setup process. This volition permit owners of newly purchased domains from 1And1, Network Solutions, together with others to get their domains verified, together with instruct their blogs online again.

Since this starts amongst spider web log owners who elected to buy their domain direct from a registrar - together with setup the domain themselves - perchance it's non also much, technically.

---

/search?q=how-to-setup-your-blogger-blog-with Use Third Party DNS Servers, For Domains Registered By 1And1, And Similar Registrars