Deletion Is Seldom The Answer

Many imaginative weblog owners are finding out, from fourth dimension to time, that deletion is non the mode to proceed - or to commence over.

I deleted my blog, in addition to forthwith I can't recreate it!

and

My domain is offline, in addition to the registrar refuses to assistance me!

or even

I deleted my post, in addition to forthwith I larn a weird URL!

Each of these complaints are examples of people who tried to delete something to larn something done, to a Blogger blog. In the showtime 2 cases, they were trying to transfer command (a blog, to a unlike Blogger work organization human relationship / a domain, to a unlike domain registration); inwards the latter case, they were trying to clear out unwanted content from a weblog post.

In neither of these cases did the weblog possessor gain the attempted goal.

For many years, nosotros accept been trying to learn people that yous cannot delete a blog, every bit role of transfer command of a weblog URL to just about other Blogger account. To transfer command of a weblog URL, yous accept to usage the weblog ownership / permission wizard, properly. Since Blogger has grown tired of dealing amongst people who deleted their blogs, entirely to run across subsequently that spammers had picked upwardly the URL, in addition to were forthwith using their difficult run (and accumulated search engine reputation), Blogger volition lock URLs of deleted blogs to the work organization human relationship doing the deletion. The URL Lock is reported, inwards just about cases, to hold upwardly bypassed after ninety days - but this appears to hold upwardly inconsistently the case.

Recently, we've seen hopeful domain owners, envious of the benefits of domains purchased using "Buy a domain", who accept tried to transfer command of their domains past times deleting them. This, too, is an crusade jump to fail. You tin transfer command of a domain from 1 registrar to just about other - but the transfer is real formal, in addition to discipline to timing restrictions. You cannot transfer command of a domain, to the particular eNom / GoDaddy / Google hosting.

And finally, for just about time, nosotros accept been instructing people that deleting a post, to but clear out the content earlier re using the ship title, is likewise a bad idea. Influenza A virus subtype H5N1 post, 1 time deleted, cannot hold upwardly recreated nether that same Title in addition to URL.

In all 3 of these attempts, the destination of deletion is non accomplished. In the latter case, it's possible to recreate the deleted post, to it's exact set down earlier deletion - but leaving the weblog possessor precisely where he started, no farther. In the erstwhile case, the weblog possessor is left inwards an indeterminate state, unable to become backwards or forwards. In no instance is anything ameliorate than a waste matter of fourth dimension the result.

>> Top

The Simplicity Of A Custom Domain Setup

Custom domain publishing is a rattling elementary means to give your Blogger spider web log a non BlogSpot URL - when y'all follow the recommended procedure.

Along amongst the simplicity, you'll abide by rather stiff requirements, when any alternative procedure is used.

Too many spider web log owners, unfamiliar amongst the complexity of the custom domain infrastructure, endeavour to "fly past times the topographic point of their pants", when they meet a requirement that they don't understand.

Improper domain setup, caused past times bad decisions, is how many custom domain publishing problems start.

First, empathise some of the close mutual mistakes, made past times equally good many spider web log owners. Blog owners inward the USA may use Google Domains, though others must buy direct from a registrar.

That reality does non modify whatsoever of the necessities of proper domain setup, however. Substituting for "Buy a domain", Blogger offers instructions, inward How gain I purpose a custom domain cite for my blog?.

There are 3 - as well as entirely 3 - supported DNS Models.

To empathise the significance of the mistakes that are usually made, starting fourth dimension empathise the iii basic DNS models, involved inward custom domain publishing.

1. Published To Domain Root - Symmetrical DNS Configuration. The close obvious configuration uses a symmetrical DNS structure - dual "CNAME" referrals.
   

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

2. Published To Domain Root - Asymmetrical DNS Configuration, aka "Google Apps". If y'all receive got a domain amongst email, FTP, as well as other possible auxiliary services, y'all purpose an asymmetrical structure, which use Google Apps to allow y'all add together auxiliary services, amongst quadruple DNS server redundancy.
   

   mydomain.com.  3600 IN H5N1 216.239.32.21 mydomain.com.  3600 IN H5N1 216.239.34.21 mydomain.com.  3600 IN H5N1 216.239.36.21 mydomain.com.  3600 IN H5N1 216.239.38.21 www.mydomain.com. 3600 IN CNAME ghs.google.com.

3. Published To Non Root Virtual Host. If y'all wishing to add together an additional spider web log to the domain, perhaps to add your Blogger spider web log to your spider web site, y'all setup an additional virtual host.
   

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

The "Buy a domain" magician produces an Asymmetrical Configuration. Choice of whatsoever 1 of the iii inward a higher house models determines what URL y'all may let on the blog.

The published URL, when setup wrong, produces close symptoms.

The published URL is 1 of the close frequent causes of problems. Do non brand whatsoever of these mistakes.

• Only let on to a URL defined past times "CNAME" referral to "ghs.google.com".
  The referral target, spelled properly, is essential.
  
  
  • Only ghs.google.com
  • Not ghs.l.google.com
  • Not www.ghs.google.com
  • Not ghs.blogger.com
  • Not ghs.blogspot.com
  • Not ghs.gogle.com
  • Not ghs.gooogle.com
  • Not whatsoever of a myriad other variations inward spelling.
• Do non let on to a URL defined past times "A" referral to the "216.239.nn.21" servers.
• The "CNAME" referral must target "ghs.google.com", absolutely.
  • Only ghs.google.com
  • Not ghs.google.com.yourdomain.com
  Understand how to define an absolute referral target.
• The "CNAME" referral must target "ghs.google.com", directly.
  • Only ghs.google.com
  • Not yourdomain.com
  Do non target the domain root, or whatsoever other indirect address.
• Understand how to define a referral host.
• Only let on to a referral host using lower illustration letters.

The domain root, inward an asymmetrical DNS model, is similarly crucial.

If y'all purpose an asymmetrical DNS addressing, target entirely the 4 Google servers, equally "A" referrals.

 216.239.32.21 216.239.34.21 216.239.36.21 216.239.38.21 

Use of these 4 servers is rattling specific. Do non brand these mistakes.

• Do non render these servers equally "nameservers", equally y'all setup your domain. If your registrar is demanding "nameservers", y'all request to check your annotation / receipt, as well as ensure that y'all did non but pay for "Name Registration", instead of for "DNS Hosting".
  
  You request your ain "DNS Hosting", equally Google does non render DNS hosting for somebody domains. If necessary, purpose a (free) third political party DNS hosting service.
• Do non let on to the URL referred to the 4 servers. Those servers may entirely hold out used to redirect the secondary URL to the published URL.
• Do non include a server provided past times your registrar - either substituted for whatsoever 1 of the four, or inward improver to the four.
• Do non include whatsoever of the three before used Google servers.
  

  mydomain.com. 3600 IN H5N1 64.233.179.121
  mydomain.com. 3600 IN H5N1 66.249.81.121
  mydomain.com. 3600 IN H5N1 72.14.207.121

  Those servers are offline - gain non include them inward your DNS addresses.
• For best results, always include all 4 servers.
• Understand how to properly define a referral host.
• Though the domain origin must hold out setup, properly, for a stable custom domain.

The "CNAME" to "ghs.google.com" is sufficient, for the published URL.

If y'all purpose "CNAME" referral for whatsoever host, entirely purpose 1 "CNAME" referral - gain non add together a complementary "A" or "CNAME" address, for that host.

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

This is all that is needed.

• A mo "CNAME" referral is non helpful - as well as is not supported past times many registrars.

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

  This is non helpful.
• An additional "A" referral is non helpful - as well as is non supported past times many registrars.

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

  This is non helpful.
• You will, however, in all probability request a mo "CNAME" for domain ownership verification. You cannot bypass this requirement - when it is required.

If y'all must setup the domain yourself, instead of using "Buy a domain", learn the rules - none of them are optional. If y'all follow the rules, y'all receive got a much improve run a hazard of having a reliable as well as working domain - instead of eventually seeing the good known "Another blog ..." or "404 Server Not Found".

After Setting Upwards Your Custom Domain Dns Addresses, Ever Verify Your Work

So many problems alongside custom domain publishing showtime alongside incorrectly setup DNS addresses. Sometimes the problems showtime alongside misunderstanding almost the stiff requirements of DNS addresses, other times misunderstanding almost how to purpose the Domain Manager tools provided - as well as sometimes the registrar gets involved, as well as causes problems.

Many times, I'll offering advice inward Blogger Help Forum: Something Is Broken, as well as the reply volition signal the confusion.

Here's a screenshot of my settings - I can't run into a problem!

or

I but got my registrar to setup the DNS addresses, every bit you lot gave me. Surely, they are right?

But nosotros diagnose the problem, as well as honour that the addresses are even as well as thus wrong.

In business, nosotros larn of the importance of using good known, touchstone testing procedures. People setting upwards a custom domain would produce good to larn this concept, also.

I accept a various assortment of online tools, which I purpose for diagnosing custom domain publishing problems. Here are 3 (as always, inward alphabetical order), which I purpose to examine as well as verify DNS addresses.

• Kloth Dig.
• Name.com Dig / Who.Is Lookup.
• WebMaster Toolkit Dig.

Each tool complements the other ii - none of them are a replacement for the other two.

Kloth Dig

• Lets you lot re-create as well as glue the output, easily.
• Lets you lot Dig the domain root, or whatsoever specific aliases.
• Lets you lot choose what host to perform the Dig.

Name.com Dig / Who.Is Lookup

• Lets you lot cheque results promptly, non waiting for TTL to expire.
• Lets you lot reference the outcome using an included URL.
• Lets you lot produce a Who Is lookup, to complement the Dig.

WebMaster Toolkit Dig

• Lets you lot re-create as well as glue the output, easily.
• Lets you lot Dig the domain root, or whatsoever specific aliases.
• Lets you lot reference the outcome using an included URL.

Prompt Verification Is Essential.
When you lot brand changes to the DNS addresses, you lot volition desire to cheque your results, promptly - waiting for DNS cache to expire, varying according to TTL, causes confusion. The Name.com Dig accesses the domain master copy server, as well as thus you lot tin strength out by as well as large run into results promptly. To cross cheque the Name.com Dig, you lot tin strength out purpose the Kloth Dig - as well as reference the domain master copy server, explicitly.

All Domain Hosts Must Be Verified.
When you lot brand changes to a Non Root Virtual Host, you'll demand to Dig the results. Both Kloth as well as WebMaster Toolkit allow you lot specify the host name, to target inward the Dig, as well as thus you lot tin strength out target whatsoever host - non but the domain source as well as "www" aliases.

Ability To Copy And Paste Results Is Useful.
It is useful to re-create as well as glue the results from whatsoever Dig transaction. Both Kloth as well as WebMaster Toolkit Digs render results that are non tabular array bound, as well as tin strength out hold out easily copied as well as pasted.

Ability To Reference The Result In The URL Is Useful.
It is useful to salvage a i click link to cheque Dig results, to avoid having to repeatedly glue or type a domain URL to hold out checked. Both Name.com as well as WebMaster Toolkit render results that tin strength out hold out checked past times clicking on a link, which you lot tin strength out bookmark.

A WhoIs Lookup Is Useful
Many times, the domain status, examined using a WhoIs lookup, provides an essential clue. Both when a domain buy is unsuccessful, as well as when a domain registration has expired, a Name.com Who.Is Lookup volition atomic number 82 to the occupation diagnosis.

Each of these tools render vital details as well as features, that the others produce non provide. And each of these tools, used properly, tin strength out assist individual to avoid posting inward Blogger Help Forum: Something Is Broken, frantically hollo for for help.

>> Top

Before Publishing Dorsum To Blogspot, Become The Dns Addresses Right

One problem, occasionally seen inwards Blogger Help Forum: Something Is Broken, involves spider web log owners preparing to re role their custom domain for publishing their website - together with who instantly involve to issue their Blogger spider web log dorsum to BlogSpot.

I involve to reuse my domain for my website - only when I travail to re issue my blog, I hold seeing

Another spider web log is already hosted at this address.

How tin I larn my spider web log dorsum online?

When nosotros expect at the domain, together with the DNS addresses, nosotros run into the domain pointing to the website, already. And this is where many custom domain publishing problems start.

Any fourth dimension yous brand whatever alter to a blog, that involves custom domain publishing, the changes volition become much to a greater extent than smoothly amongst the domain properly pointing to the blog.

Whether yous are setting upwards a novel custom domain publishing, changing a custom domain publishing, or perhaps removing a custom domain publishing, the publishing procedure plant much meliorate amongst the domain properly redirected to the Google database.

One of the causes of the mysterious message

Another spider web log is already hosted at this address

comes from the domain non beingness properly redirected to the Google servers. When the Blogger re publishing procedure can't conk on because the domain DNS addresses are non correct, the procedure terminates amongst an error. Whenever whatever database alter terminates amongst an error, it's e'er possible that the procedure may non build clean upwards afterward itself earlier ending - together with artifacts (aka broken pointers) volition live on left behind inwards the database.

The side past times side fourth dimension that yous travail to re issue the spider web log - or when yous (or your readers) travail to stance the spider web log - yous (or they) volition see, notwithstanding again

Another spider web log is already hosted at this address.

or an alternate

Server Not Found Error 404

When that happens, yous accept alone 1 alternative - recycle the domain settings - together with pray to the deity of your choice.

The latter processes are non known to live on 100% effective. The best way to bargain amongst them is to never bargain amongst them - to non start past times causing a problem. That agency to e'er hold the domain DNS addresses righteous, whenever maintaining a custom domain published blog.

If yous are going to role your domain for a non Blogger website, e'er publish your Blogger spider web log dorsum to BlogSpot, first. Then, verify the condition of the blog. Finally, together with amongst no problems discovered, alter the DNS addresses.

Confusion Over Custom Domains Using Adsense For Domains Dns Servers

I've been alert people for years nearly the lack of exceptional provided past times Google, inwards their instructions nearly setting upwards a custom domain, amongst the domain registration purchased straight from a registrar

.... yous alone bespeak to acquire the domain name; yous don't bring to pay extra for hosting service.

That was an observation, that I made, v years ago.

The Google provided instructions were lately changed - unfortunately, non to satisfy every novel domain owner's bespeak for detail. Recently, we're seeing novel bear witness of confusion - which appears to maiden of all amongst Google instructions, again.

As I bring written repeatedly, when yous setup a someone domain, to purpose inwards publishing a Blogger blog, Google does non supply DNS hosting for your someone domain. Recently, I learned nearly the AdSense for Domains DNS servers.

• ns1.googleghs.com
• ns2.googleghs.com
• ns3.googleghs.com
• ns4.googleghs.com

Apparently, closed to people bring been able to purpose the AFD DNS servers to supply DNS hosting for their someone domains.

This week, we're seeing reports inwards a Who.Is lookup of "mydomain.com" (in this example), nosotros see:

http://who.is/whois/mydomain.com/  REGISTRY WHOIS FOR MYDOMAIN.COM  Registrar: MY REGISTRAR, INC Whois Server: whois.myregistrar.com Referral URL: http://www.myregistrar.com/ Status: clientTransferProhibited  Expiration Date: 2014-03-21 Creation Date: 2012-03-21 Last Update Date: 2012-04-07  Name Servers:     ns1.googleghs.com     ns2.googleghs.com     ns3.googleghs.com     ns4.googleghs.com 

And at that spot nosotros see, equally mentioned above:
ns1.googleghs.com
ns2.googleghs.com
ns3.googleghs.com
ns4.googleghs.com

In this example, "mydomain.com" was, apparently, setup originally to purpose "ns1.googleghs.com" (x 4) for domain DNS addressing. Apparently, until this week, the addressing worked - as well as Google was willing to host DNS addressing for closed to someone domains.

Now, it doesn't.

Looking at the content of AdSense Help: Pointing your domains to Google's servers, nosotros run across the warning

Hosted domains has gone away. AdSense stopped supporting Hosted domains on Apr 18, 2012.

Apparently, "gone away" way that the AFD DNS servers "ns1.googleghs.com" (x 4) are instantly offline.

Opening a Command Window inwards Windows, nosotros acquire confirmation

C:\>ping ns1.googleghs.com  Pinging ns1.googleghs.com [216.239.32.18] amongst 32 bytes of data:  Request timed out. Request timed out. Request timed out. Request timed out.  Ping statistics for 216.239.32.18:     Packets: Sent = 4, Received = 0, Lost = four (100% loss) 

So, at that spot yous bring it - "ns1.googleghs.com" (x 4) is land offline. Once again, at that spot is no gratis lunch. Read - as well as head - the fine print.

If your domain was using those servers to serve DNS addresses, you're going to bring to become dorsum to your registrar, as well as inquire them for their DNS servers. If this involves changing your "Name Registration" service to "DNS Hosting", you're going to bring to comport the cost.

>> Top

New Custom Domains Inwards Transition As Well As Diverse Weblog Gadgets

About a twelvemonth afterward Blogger introduced custom domain publishing, they segmented the custom domain publishing process.

In social club to avoid database corruption, which was a frequent drive of the "Another spider web log ..." problem, they introduced a delay period, which we telephone weep upward "Transition". Transition lets them delay telephone substitution spider web log updates - until the the world broad DNS infrastructure has a jeopardy to reliably update amongst information almost whatsoever novel Google custom domains.

In the beginning, Transition lasted almost precisely 72 hours, in addition to delayed creation of the "301 Moved Permanently" redirect from the BlogSpot to domain URL. Later, when Following became a fixture on most blogs, nosotros observed that the Followers gadget was every bit good beingness updated on a Transition based delay.

The Followers gadget is non the solely accessory that references the spider web log URL - in addition to recently, nosotros observed that to a greater extent than features are dependent area to Transition based update delays.

Recently, nosotros observed diverse XML gadgets, similar Followers, that incorporate references to the spider web log URL, are every bit good dependent area to Transition scheduling.

• Blog Feeds.
• BlogLists.
• LinkLists.

All of these gadgets purpose XML code, in addition to appears to live dependent area to a Transition based update delay.

If you lot just republished your blog, using "Buy a domain", to a non BlogSpot URL, you lot may live seeing the Transition symptoms.

We're sorry...
This gadget is configured incorrectly.

or alternately, just a blank infinite where 1 or to a greater extent than gadgets used to live seen.

Another alter late observed is that the quondam 72 sixty minutes Transition is directly 96 to 120 hours, for roughly gadgets.

As frustrating every bit these peccadilloes may be, they are however less frustrating than spider web log owners seeing the old

Another spider web log is already hosted at this address.

or worse, having their readers report

Error 404
Server non found

when trying to sentiment a custom domain published blog.

And of the (progressively rarer) reports of "Another spider web log ..." seen inwards DNS address mistakes, instead of suggesting

Try recycling the domain settings, inwards Google Apps.

Now that Blogger has discontinued the "Buy a Domain" feature, nosotros hit got non yet observed when Transition is applied.

Research Custom Domain Problems From The Foremost Of The Purchase

Sometimes, researching a problem, alongside a custom domain published blog, involves a Who Is lookup, to hit upwards one's hear fundamental domain details - similar DNS server namess, buy date, registrar name, too others. Starting alongside the properly spelled domain cite is essential, to getting a useful Who Is lookup. In cases where the weblog / domain possessor can't piece the domain cite consistently, you lot tin sack kickoff fifty-fifty to a greater extent than basically.

To hit upwards one's hear the details nearly a domain purchase, when you lot convey whatever doubt, inquire for a re-create of the account or receipt. If the transaction was conducted electronically, re-create too glue of the fundamental data is most useful. If the transaction involved a newspaper trail, convey the receipt scanned, too a motion painting posted somewhere that you lot tin sack view.

The account or receipt, for whatever domain purchase, volition deal position - too confirm or deny - fundamental details.

• Correct domain cite - spelling.
• Purchase date.
• Name of registrar.

All of these details are useful, inward researching a employment alongside a custom domain published blog.

Starting alongside the domain name, verified from the account or receipt, you lot tin sack purpose whatever of several similar Who Is lookup tools.

• DomainTools.
• MXToolbox.
• Name ("who.is").
• Network-Tools.

Having multiple complementary tools tin sack survive useful, many times - both every bit backup (in illustration i is offline, for or too then reason) - too to confirm or deny unexpected results.

>> Top

Custom Domain Diagnoses - Put Dns Address Inconsistencies

One of the to a greater extent than intriguing causes of intermittent custom domain problems starts amongst inconsistent DNS server configuration. Recently, eNom, i of the "partners" inwards "Buy a domain", has been serving inconsistent DNS configurations, from fourth dimension to fourth dimension - including i rattling blatant episode the afternoon of 6/18/2012, which was reported past times several dozen angry weblog owners.

Detecting, in addition to diagnosing, the inconsistencies is typically a complicated process.

1. Identify the domain authorization servers, typically using a Who Is lookup.
2. Dig each domain address (typically "naked domain" in addition to "www" aliases), from each of the identified domain authorization servers.
3. Extract in addition to aggregate each Dig log.
4. Compare aggregated Dig snippets.

This was non a project for the faint of heart, or tech challenged, weblog owner.

Recently, I was given a handy tool which does all of this, inwards i quick GUI transaction.

The Dig Web Interface, nevertheless roughly other gratis online tool, provides us the mightiness to diagnose inconsistent DNS servers - such every bit the work eNom seems to have, inwards a thirty bit transaction.

1. Provide the "naked domain" in addition to "www" aliases.
2. Select "A" for "Type" ("A" / "CNAME" / "NS" lookups).
3. Select "Authoritative" for "Nameservers".
4. Hit "Dig".

Finally, but re-create the log produced, for examination.

It's non a fancy tool, but it does the chore - rattling well. Here, nosotros meet the log for this domain, "nitecruzr.net".

nitecruzr.net@ns11.domaincontrol.com.: nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.36.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.32.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.34.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.38.21 nitecruzr.net.  3600 IN NS ns54.domaincontrol.com. nitecruzr.net.  3600 IN NS ns53.domaincontrol.com. nitecruzr.net.  3600 IN NS ns12.domaincontrol.com. nitecruzr.net.  3600 IN NS ns11.domaincontrol.com. 
 nitecruzr.net@ns12.domaincontrol.com.: nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.36.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.32.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.34.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.38.21 nitecruzr.net.  3600 IN NS ns54.domaincontrol.com. nitecruzr.net.  3600 IN NS ns53.domaincontrol.com. nitecruzr.net.  3600 IN NS ns12.domaincontrol.com. nitecruzr.net.  3600 IN NS ns11.domaincontrol.com. 
 nitecruzr.net@ns53.domaincontrol.com.: nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.36.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.34.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.38.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.32.21 nitecruzr.net.  3600 IN NS ns54.domaincontrol.com. nitecruzr.net.  3600 IN NS ns53.domaincontrol.com. nitecruzr.net.  3600 IN NS ns12.domaincontrol.com. nitecruzr.net.  3600 IN NS ns11.domaincontrol.com. 
 nitecruzr.net@ns54.domaincontrol.com.: nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.36.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.34.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.38.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.32.21 nitecruzr.net.  3600 IN NS ns54.domaincontrol.com. nitecruzr.net.  3600 IN NS ns53.domaincontrol.com. nitecruzr.net.  3600 IN NS ns12.domaincontrol.com. nitecruzr.net.  3600 IN NS ns11.domaincontrol.com. 
 www.nitecruzr.net@ns11.domaincontrol.com.: www.nitecruzr.net. 3600 IN CNAME ghs.google.com. 
 www.nitecruzr.net@ns12.domaincontrol.com.: www.nitecruzr.net. 3600 IN CNAME ghs.google.com. 
 www.nitecruzr.net@ns53.domaincontrol.com.: www.nitecruzr.net. 3600 IN CNAME ghs.google.com. 
 www.nitecruzr.net@ns54.domaincontrol.com.: www.nitecruzr.net. 3600 IN CNAME ghs.google.com. 

The log is non complicated, to parse. For each URL, each authorization server is identified, in addition to Dug. In the representative of this domain, hosted on GoDaddy, nosotros meet each URL, Dug from each of four authorization servers, i past times one.

If a DNS inconsistency existed, the inwards a higher house log would exhibit the differing DNS addresses - such every bit eNom hosted domains show, from fourth dimension to time. Given this tool, it may endure easier to await for DNS inconsistencies, when problems amongst custom domains are reported, inwards Blogger Help Forum: Something Is Broken.

>> Top

Research Custom Domain Advert Changes, First

As custom domain publishing becomes exactly 1 to a greater extent than characteristic to add together to your Blogger blog, about weblog owners create upwards one's take away heed that the domain that they are using, correct now, is non to their liking.

Fortunately, alongside a Blogger blog, the physical care for of changing your domain to another is non complicated - hoping that you lot accept the correct tools, in addition to brand the correct decisions.

• Buy (as required), in addition to setup, a novel domain URL.
• Publish the weblog dorsum to BlogSpot.
• Publish the weblog to the novel domain.

All that considered, in that place is a 4th stride which many weblog owners larn by to overlook - until long later on they accept completed the third.

One of the features of custom domain publishing is to increase page rank / reputation / visibility.

Try to retain reputation from the erstwhile domain.

When publishing the weblog to a non BlogSpot URL, the vast bulk of all Blogger weblog owners, when changing the weblog from 1 custom domain to another, volition produce good to plan a 3rd step.

• Forward the electrical flow domain to the novel published URL.

Too many times nosotros run across the plaintive shout out inwards Blogger Help Forum: Something Is Broken.

I exactly bought a novel domain for my weblog - but the previous URL is at 1 time 404!

This is a mutual complaint, for about weblog owners who produce non intend the physical care for through, earlier starting the domain swap.

Retaining reputation, acquired to date, is non going to last easy.

For besides many weblog owners, the 3rd stride is not, at all, obvious.

But how produce I frontward the domain?

Too many custom domain owners don't know how to purpose the Domain Manager sorcerer provided past times the registrar - or (in the illustration of "Buy a domain" customers) accept non fifty-fifty setup the Google Apps domain director desktop account, which provides access to the Enom or GoDaddy Domain Manager.

For these weblog owners - in addition to whatever weblog owners contemplating a domain modify - I'll add together a 4th stride to the process.

You'll require to purpose tools provided past times the registrar.

• Do about basic query - abide by out how to access, in addition to how to use, the Domain Manager wizard.

And produce this novel First Step earlier you lot require to report

I exactly bought a novel domain for my weblog - but the previous URL - in addition to all my search engine hits - are at 1 time 404!

in addition to preferably earlier starting

• Publish the weblog dorsum to BlogSpot.
• Use "Buy a domain" (if possible), in addition to position out the weblog to the novel domain.

Influenza A virus subtype H5N1 "301 Moved Permanently" redirect - which is what you lot volition need - is setup differently, for unlike registrars. Some registrars, such every bit GoDaddy, fifty-fifty accept unlike nameservers which are setup differently - in addition to which require redirection to last setup differently.

Try to larn the proper instructions from your registrar - then the private post URLs are properly redirected - if your registrar volition back upwards such redirection.

You're going to lose search reputation - at least, temporarily.

After you lot properly consummate the higher upwards procedures, don't await to run across an immediate transfer of page rank, reputation, in addition to visibility to the novel published URL.

You require to excogitation ahead, in addition to visit the issues, when changing domains - exactly every bit you lot would plan the rename of the blog, in addition to every bit you lot would plan the custom domain migration. You'll abide by that changing the custom domain published URL involves issues from both of the latter changes.

---

Too many #Blogger weblog owners, alongside blogs published to custom domains, create upwards one's take away heed that a unlike domain cite would last meliorate for the blog. They purchase the novel domain, in addition to rename the blog, without doing whatever planning for the change.

They abide by that the erstwhile domain URL is all the same referenced, later on the modify - in addition to the weblog is non beingness re indexed, nether the novel domain URL, apace enough. As search seat drops, they discovery that they failed to excogitation the URL change.

Before Changing Your Custom Domain Published Blog, To Another Custom Domain, Do Some Research
/search?q=
Research Custom Domain Name Changes, First

You Cannot Purchase A Domain From Blogger

One of the odder examples of naivete, seen occasionally inwards Blogger Help Forum: How Do I?, involves the custom domain purchase.

How hit I purchase a domain from Blogger?

or alternately

How hit I accept Google host my domain?

The immediate answer, properly stated, is simple.

You cannot purchase a domain from Blogger. Neither Blogger, nor Google, is a registrar.

The sum answer, however, is a fighting to a greater extent than complex.

Blogger / Google provides the "Buy a domain for your blog" wizard, which simplifies the purchase too setup of non BlogSpot URLs, for our Blogger blogs - when nosotros are able to brand sure enough concessions inwards the purchase process. The "Buy a domain" sorcerer is simple, alongside roughly subtle restrictions.

• The "Buy a domain" sorcerer should non last interrupted, equally it cannot last restarted.
• A major banking concern issued credit card, inwards working order, is required.
• Only specific generic Top Level domains are offered.
  • .biz
  • .com
  • .info
  • .net
  • .org
  No province Top Level domains are offered.
• The "Buy a domain" sorcerer uses partner registrars eNom too GoDaddy, selectable at purchase.
• If yous already accept an describe of piece of occupation organisation human relationship alongside eNom or GoDaddy, yous volition destination upward alongside a minute account. There is no chance to purchase using an existing account.
• "Buy a domain", when used, produces 1 too alone 1 of the three measure domain models.

If yous are able to alive alongside the restrictions - too yous are the 1 shout out for the master copy question

How hit I purchase a domain from Blogger?

chances are that you, Blogger / Google, too your readers volition all last improve off alongside yous using "Buy a domain". Just please, excogitation the blog migration, earlier starting.

>> Top

Enabling Blogger For Your Somebody Domain

This summary is not available. Please click here to view the post.

Custom Domain Publishing Is Dorsum - Too Amongst A Novel Detail

After restored the custom domain publishing option.

Last calendar week nosotros encountered an lawsuit that could behave upon Blogger users inwards the procedure of configuring a custom domain, during the verification of ownership of domains betwixt the provider as well as Blogger. Blogs amongst previously configured custom domains were non affected.

With the argue for disabling custom domain publishing existence security, Blogger Engineering has added a stride inwards the publishing process, to add together a random token every bit a "CNAME", as well as verify your correct to issue to your domain, from Blogger. You acquire the random token from the "settings instructions" document, "How compass I utilization a custom domain refer for my blog?".

See the URL of this (hypothetical) settings instructions document?

http://www.blogger.com/custom-domain-instructions.g?cnameVerificationToken=VPTRE6SUB6JM+gv-G47P6DIR6KFENZUFIFYWSQJJPDYFZK4SQMUUIUFLYLCQD4OIGDFA.domainverify.googlehosted.com.&domain=www.hotspotshield.com

This is an example. If you're registering a domain other than "www.hotspotshield.com", you're going to bring a dissimilar token - which should move a purpose of the BlogSpot as well as domain URLs. You'll too authorities annotation unopen to other instance sensitivity lawsuit - "www.hotspotshield.com" as well as "www.HotSpotShield.com" volition compass completely dissimilar tokens.
Now, it's an out of appointment example.

http://www.blogger.com/custom-domain-instructions.g?cnameVerificationToken=GKBPLXBRMT5M+gv-H5FFOYEKYNXE46EE4A3PLAK6HCDIELS27KQUR5OBKHFKXRKMCTDA.domainverify.googlehosted.com.&domain=www.hotspotshield.com

That's what you lot get, for "www.hotspotshield.com", today. We'll banking corporation fit again, tomorrow. Also, nosotros postulate to know when "today" ends.

If you lot purchase a domain using "Buy a domain" later today, Google Apps should setup the domain for you lot - including the mo "CNAME". If you lot bought the domain straight from a registrar, you're going to bring to click on "settings instructions", as well as acquire the token for your domain. Note that a "CNAME" is required - a "TXT" won't render the same verification. Also authorities annotation the diverse registrar entry conventions, which volition behave upon your utilization of their domain managing director forms.

We are learning a lot of details nigh the domain verification process, unopen to of which were known inwards custom domain setup inwards full general - as well as which are absolutely critical to the process. You volition desire to read the [FAQ] Why is my domain withal inwards "12" / "404" State?, to acquire all of the details. The FAQ has been updated several times, as well as thus re read it often..

This will, hopefully, render a solution for the Abandoned Domains problem, as well as allow everybody to issue to their domain, regardless of whether the domain was previously used for Blogger / Google custom domain publishing yesteryear unopen to other blog.

On the other hand, if you lot purchased your domain using "Buy a domain", as well as you lot always postulate to recycle the publishing settings, you're belike going to bring to add together this novel "CNAME" to your domain, earlier you lot tin forcefulness out re publish. This volition maybe include everybody who purchased their domain, earlier the Publishing choice was disabled - if the domain is non operational correct directly - as well as possibly, weblog owners who postulate to un delete a domain published blog.

>> Top

Custom Domain Setup Similar A Shot Lacks The Purchase A Domain Wizard

As nosotros sift through the wreckage of the blogs damaged yesteryear the recent Blogger custom domain safety issue, nosotros complaint a pregnant omission. The "Buy a Domain For Your Blog" magician is conspicuous inward its absence.

When I click on the Settings - Publishing options, I don't fifty-fifty bring the choice to banking concern gibe availability or buy a domain name. Where is the "Buy a domain" display?

Right now, it appears that "Buy a domain" was sacrificed, in addition to thus that the full general custom domain publishing characteristic could live on restored to a greater extent than promptly (though not promptly enough, for many weblog owners). There are several tasks that must live on completed yesteryear "Buy a domain", which are complex - in addition to the necessary coding merely could non live on completed yesteryear Tuesday of this week. I saw i message of hope.

We volition live on restoring the might to buy a custom domain from Blogger soon.

We'll merely bring to bring faith, that they are working on this characteristic equally nosotros lament its electrical flow absence - in addition to that its absence is brief..

In the hateful time, roughly wanta live on domain owners bring establish a domain buy magician provided yesteryear Google Apps - though that's non "Buy a domain". Google Apps has two unlike wizards providing domain buy options, each amongst a widely unlike address in addition to Top Level Domain menus.

---

(Update 2012/10/09): "Buy a domain for your blog" is i time once to a greater extent than exercise of the Publishing wizard.

---

>> Top

What Is This Novel Cname, Anyway?

Ever since Blogger in conclusion restored the custom domain publishing feature, weblog owners convey been call for virtually the add-on to the domain setup procedure - the novel "CNAME".

Do I actually demand this? My onetime blogs don't convey it, together with they are fine.

and

My registrar won't permit me add together a instant "CNAME" - they allow 1 "CNAME" / domain (my "www").

and

My registrar won't allow long addresses, such equally what y'all convey for "Destination" / "Target" / "Points To".

And nosotros are learning that this requirement is going to survive a problem for weblog owners using or hence registrars, who can't supply this "CNAME" inwards their customers domains.

In technical terms, the novel "CNAME" is an ownership certificate, provided inwards a one means encryption.

If y'all convey WiFi inwards your habitation (likely) - together with are using encryption (hopefully), y'all convey a similar 1 means encrypted certificate - the WPA / WPA2 cardinal / passphrase. For an allegorical (easy to read) give-and-take virtually certificate encryption, run into Designing an Authentication System.

Only the weblog / domain possessor know the values together with tin install the certificate.

Only you, the weblog possessor (and anybody who y'all trust, on your behalf), are able to install the certificate for your domain, into your domain DNS addresses. Only y'all convey access to both

• The Blogger dashboard Publishing wizard.
• The zone editor sorcerer provided yesteryear the registrar.

This helps Blogger assistance y'all kicking the bucket along your domain nether your command - equally long equally y'all pay the yearly registration fee for your domain.

The certificate contains 3 unique values.

The domain ownership certificate has 3 keys.

1. A individual key, which Blogger appears to modify regularly (some say daily) - together with 1 which they control.
2. The BlogSpot URL.
3. The domain URL (entered inwards "Advanced settings").

It has 2 pregnant values.

1. "Name" / "Label" / "Host". This is at in 1 lawsuit known equally the "short token".
2. "Destination" / "Target" / "Points To". This is at in 1 lawsuit known equally the "long token".

Note the 3 labels used to position each "value" - which reverberate the multifariousness of the registrars which may supply DNS hosting for our domains (when they are able to fulfill our specific needs). When y'all expect at the Domain Manager sorcerer for your domain, you may run into whatever of the three (possibly, others) used - equally at that spot is no authoritative label for these 2 DNS address components.

Compare the 2 "CNAME"s, inwards construction together with value.

Let's expect at the 2 "CNAME"s, together, hence y'all tin compare the similar structure. Note the demand to get the syntax, which tin vary yesteryear registrar, absolutely correct.

This is the start "CNAME" - the "www" alias DNS address. This "CNAME" is identical for all Blogger blogs, using the asymmetrical DNS address convention.

1. "Name" / "Label" / "Host". www
2. "Destination" / "Target" / "Points To". ghs.google.com

This is the instant "CNAME" - the domain ownership certificate. This "CNAME" volition vary, for each dissimilar domain. Here nosotros run into the master copy event (which has since changed).

1. The "short token". vptre6sub6jm
2. The "long token". gv-g47p6dir6kfenz.dv.googlehosted.com

See the concluding period, at the halt of the "Destination" / "Target" / "Points To" address, below? It's non inwards the example, above. Be real careful here, or hence registrar's volition automatically insert the "." for y'all - together with if y'all insert it also, you'll convey a problem. Other registrars volition demand y'all to add together it - together with if omitted, you'll convey a problem. Regardless, its presence, inwards the concluding product, is essential.

gv-g47p6dir6kfenz.dv.googlehosted.com.

You tin verify specific certificate values.

If y'all know the value for the brusk token, y'all tin Dig together with extract the long token - when the instant "CNAME" is properly setup.

Once y'all supply the higher upwards examples to the Domain Manager, the next 2 DNS addresses are generated together with added to the domain server. The "3600" represents the TTL, a setting provided yesteryear the registrar. The "IN" is business office of the Dig log extract syntax.

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

and

vptre6sub6jm.mydomain.com. 3600 IN CNAME gv-g47p6dir6kfenz.dv.googlehosted.com.

Both "CNAME"s bespeak to specific Google servers. The instant "CNAME" is alone slightly obscure. Both "CNAME"s are essential (when required - but only when required).

1. The start lets you, together with your readers, sentiment your blog.
2. The instant lets Google verify that y'all ain the domain, together with y'all should survive allowed to pose out your weblog to the domain URL.

Nobody but you, the weblog owner, volition e'er know the values of the tokens. Nobody but you, the domain owner, tin install that "CNAME" into the domain DNS addresses. If DNS resolution of the brusk token address points dorsum to the right Google server, together with hence you, the possessor of the blog, together with the possessor of the domain are verified equally the same person. And the ownership certificate is "decrypted", using DNS elevate resolution.

• Short token. vptre6sub6jm
• Long token. gv-g47p6dir6kfenz.dv.googlehosted.com

Some certificate values are temporary.

Since the individual Blogger cardinal changes regularly, if anybody learns what tokens y'all used, inwards the brusk 3 pace domain verification process, the values volition convey probable changed, together with their fourth dimension volition convey been wasted. Your weblog together with domain stay your weblog together with domain.

So, create third political party DNS hosting.

1. Get the brusk token together with long token values, for your unique weblog / domain.
2. Add the novel "CNAME" to your domain.
3. Publish the weblog to the domain URL.

That's it (subject to observed timing issues). You are at in 1 lawsuit done amongst the domain ownership verification process, together with amongst these encrypted values. Start planning the migration - this volition compass off faster than y'all think. And it is your responsibility, to acquire this done.

---

The Novel Cname Needs To Live On Added, As Well As Used, Promptly

One oddity, observed past times a few weblog owners, is that fifty-fifty later adding the "CNAME" to verify domain ownership, non every weblog possessor is able to run into theirs successfully verified.

I added both "CNAME"s - as well as I'm notwithstanding getting "Error 12" when I endeavour to publish.

There are domain director address entry convention.Even amongst these rules observed, in that place are notwithstanding a modest handful of unsuccessful weblog owners, seeing "Error 12" - or "Error 32".

One of the possible reasons for these terminal few stand upward for outs, I believe, relates to timing.

Let's consider the "CNAME" setup process.

1. Get the "Name" / "Label" / "Host" as well as "Destination" / "Target" / "Points To" values, for your unique weblog / domain.
2. Add the novel "CNAME" to your domain.
3. Publish the weblog to the domain URL.

In the "settings instructions" document, How create I purpose a custom domain cite for my blog?, nosotros are instructed to

wait virtually an hr for your DNS settings to activate

In diverse other instructions, y'all volition typically see

Wait for upward to a day, for settings to live on updated

or similar miscellaneous waiting instructions.

Besides the waiting factor, there's a "negative waiting" factor. Several weblog owners accept observed that the "Name" / "Label" / "Host" as well as "Destination" / "Target" / "Points To" values, for their unique weblog / domain, seems to change, from twenty-four hours to day. This tells me that the ownership verification "certificate" (which is what the "Name" / "Label" / "Host" as well as "Destination" / "Target" / "Points To" values provide), similar most safety certificates, has a express purpose period.

If y'all larn the certificate inwards Step #1 above, y'all accept to purpose the certificate inwards Step #3 reasonably promptly later doing so. If the certificate for your domain expires inside a 24 hr period, as well as hence y'all have, at most, 24 hours betwixt Steps #1 as well as #3. In other words, y'all larn 24 hours to re let on your domain - later y'all add together the novel "CNAME" - as well as that's including the catamenia that you

wait virtually an hr for your DNS settings to activate

It's alternatively possible that the death is based on an arbitrary fourth dimension of twenty-four hours - non 24 hours later existence issued.

Whatever the nature of the death (absolute as well as arbitrary - or relative to fourth dimension of issuance) the existence of an death fourth dimension is normal, for a good designed safety certificate. By giving the certificate a temporary lifetime, it becomes less useful to would live on hijackers as well as similar miscreants.

So, y'all may non actually create goodness from waiting a twenty-four hours to re let on your domain - unless y'all similar seeing "Error 12" (possibly "Error 32"), repeatedly, when y'all endeavour to publish. Personally, I would expression an hr at the most, later Step #2, earlier trying Step #3. I would as well as hence retry Step #3 hourly, until successful. If y'all accept to a greater extent than patience than I, fine.

>> Top

You Produce Convey To Add Together A Instant Cname

We're seeing bear witness of confusion, inwards Blogger Help Forums, from weblog owners who read the out of appointment instructions, most using "Buy a domain".

We come across considerable confusion, where people using that characteristic insist that they don't stimulate got to add together a "CNAME". In other cases, people using the Blogger / GoDaddy DNS Configuration sorcerer volition mean value that the instant "CNAME" is beingness added for them.

---

(Update 2013/09): The instant "CNAME" won't last required, inwards all cases. If y'all don't come across instructions for adding a instant "CNAME", focus your efforts on getting the domain working, amongst righteous base of operations DNS addresses,

---

Right now, everybody has to add together their ain domain ownership verification token - aka the instant "CNAME".

We're hoping that the (currently offline) "Buy a domain" sorcerer volition automatically add together the domain ownership verification - simply equally it adds the other DNS addresses - but we'll come across that, when nosotros come across it. The Blogger / GoDaddy wizard should, likewise, stimulate got aid of this, on your behalf - but correct now, it doesn't. The bottom line? If y'all become to the Publishing wizard, together with see

Error 12

or a variant, afterwards typing the domain URL into "Advanced settings", amend get busy.

What non all weblog owners realise is that the novel "CNAME" must last simply that. Blogger is non beingness arbitrary, or pedantic, inwards requiring precision.

• It must last a "CNAME". Influenza A virus subtype H5N1 "TXT" volition non work.
• The "Name" value must last specified exactly equally supplied (Plus or minus the trailing period!).
• The "Destination" value must last specified exactly equally supplied (Plus or minus the trailing period!).

You cannot wing yesteryear the spot of your pants, together with attempt what seems similar it powerfulness work, equally a "substitute". Webmaster Tools provides a weblog ownership verification procedure - which may, or may non help.

If the registrar for your domain does non let the add-on of this "CNAME", y'all volition ask to setup a 3rd political party DNS host for your domain. You produce stimulate got to add together this instant "CNAME" - fifty-fifty if this may conflict amongst older Blogger Help instructions.

>> 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.

Custom Domain Purchase - Getting Past Times Without Purchase A Domain

Now that custom domain publishing is once ane time to a greater extent than available, though without the alternative to purchase a domain through Blogger, also many anxious Blogger weblog owners are bespeak the obvious question

How create I purchase a domain?

Not a lot of weblog owners desire to hold upward told

Contact the registrar of your choice.

The backup to "Buy a domain" would hold upward to buy a domain straight from a registrar - however, this presents also many challenges to the casual weblog owner.

---

(Update 2012/10/09): "Buy a domain for your blog" is ane time once to a greater extent than component subdivision of the Publishing wizard.

---

Fortunately, at that topographic point is a substitute to "Buy a domain", available through Google. Google Apps - which is the back upward organisation for "Buy a domain" itself - provides the alternative to purchase a domain, along amongst the Google Apps Dashboard. Google Apps does non utilization slow to hollo upward URLs, unfortunately.

To utilization the Google Apps equivalent of "Buy a domain", you lot showtime from the "Home Page" for Google Apps.

http://google.com/a/domain

This currently redirects to

https://www.google.com/a/cpanel/standard/new3

which is titled

Get started amongst Google Apps for free

From here, you lot discovery the all of import advice

Don't convey a domain yet?
No Problem. You tin register a novel domain starting from $8 a year.

accompanied past times the push clit "Find domain".

Hitting the "Find domain" button, you lot larn a display that's like inwards functionality to "Buy a domain" - except the pulldown listing of available Top Level Domains is currently a chip dissimilar from the selections offered past times "Buy a domain".

To larn a ameliorate selection of Top Level Domains, you'll convey to larn to

https://www.google.com/a/signup/?hl=en&source=gafb-globalnav-en

Here you lot volition convey to fill upward out the "You as well as your business" form, as well as striking "Next". The side past times side display volition showtime amongst "Check Availability" - as well as volition render a much longer TLD selection list.

>> Top

Schizophrenia As Well As Custom Domain Urls - October 2012

Now that the custom domain publishing characteristic is dorsum online again, in that place remains 1 characteristic of custom domain publishing to live on restored to the Blogger dashboard.

The real pop Blogger dashboard choice to redirect the domain root (aka "naked domain"), to the "www" alias, may non live on reliable - or fifty-fifty available.

Too many people report

I can't redirect the naked domain - I tin direct the option, but the adjacent fourth dimension I look, the box volition live on un checked.

and

My "www" alias industrial plant simply fine - but the domain origin straightaway returns a "404".

Fortunately, in that place are alternative solutions to render the naked domain redirect.

There are iii ways to redirect the domain origin to the primary ("www" - or whatever alternate selection) alias.

• Registrar Domain Manager forwarding.
• Blogger Publishing redirect.
• Google Apps "Domain settings" redirect.

Registrar Domain Manager

The Registrar Domain Manager provides, for roughly weblog owners, the currently almost obvious alternative to the Blogger Publishing redirect - but it is non the simplest to use. Depending upon the registrar, as well as the nature of the domain managing director / DNS servers, this physical care for may non fifty-fifty work.

Some registrars volition recommend unproblematic DNS or frame forwarding to the BlogSpot URL - as well as this "solution", nosotros know from experience, will non function at all. One work hither volition live on spurious spam classification, caused past times what looks similar an offsite redirect of the domain root.

Blogger Publishing

The Blogger Publishing redirect option is the almost obvious alternative. This is the preferred option, inwards custom domain publishing - as well as re publishing - procedures.

Google Apps "Domain settings"

H5N1 less obvious option, the Google Apps "Domain settings" redirect option, is a 3rd solution.

For whatever newly purchased domain - also every bit for domains purchased straight from a registrar, it's possible (though currently, with roughly effort) to setup a Google Apps domain administrator account. Next, role the "Change how your naked domain is redirected" screen, as well as change or recycle the domain origin redirect.

Which e'er alternative you lot chose - or made to work, the domain origin should straightaway redirect to the alias of your choice.

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