BLog: Custom Domains

Showing posts with label Custom Domains. Show all posts

Sunday, February 2, 2020

Deleting Your Google Apps Work Concern Human Relationship Volition Non Cause Your Problems

A few Blogger spider web log owners, trying to resolve their custom domain publishing problem, may run across Google Apps mentioned inwards the diagnosis procedures, as well as travail the creature strength fashion out - deleting the Apps account. Unfortunately, the Google Apps desktop, when (only when) it provides administrative domain control, exactly gives the domain administrator the mightiness to recycle the domain settings.

The Google Apps desktop trace organization human relationship does non comprise whatever powers, or crusade whatever problems, on its own.

There are no settings embedded inwards the Apps desktop account, that larn reset when the Apps trace organization human relationship is deleted. If y'all delete your Apps account, acre y'all are inwards the physical care for of diagnosing or resolving a custom domain publishing problem, you're going to convey to become dorsum as well as setup the account, again.

>> Top

Tuesday, January 28, 2020

Following In Addition To Custom Domain Migration

Many weblog owners, mindful of the diverse ongoing migration of their weblog to a custom domain. Various anxious questions virtually Following, as well as custom domain publishing, are seen from fourth dimension to time, inwards Blogger Help Forum: How Do I?.

Can I setup custom domain publishing, without losing my Followers?

This is 1 trace organization where the perception is much worse than the reality.

The Following concept involves 2 services.

The links betwixt your Followers profiles, as well as your blog.
The newsfeed ("Atom" / "RSS") subscription setup for each of your Followers.

Your Followers profile human relationship is against your blog, using its BlogID. As long every bit yous produce non switch to publishing a unlike weblog (with a novel BlogID), the Followers profile human relationship amongst your weblog volition stay intact. This is the illustration for both a normal renaming of the weblog (BlogSpot to BlogSpot URL change), every bit for a custom domain publishing (BlogSpot to non BlogSpot URL change).

Your Followers subscription human relationship is against the URL of your blog. Since a custom domain publishing involves forwarding of the BlogSpot URL, to the domain URL, the subscription human relationship volition stay intact, subsequently the migration procedure is complete. H5N1 BlogSpot to BlogSpot URL alter may involve some seek yesteryear you to retain the subscription relationship; this does non postulate to last done, for a BlogSpot to domain publishing change.

You volition postulate to banknote the custom domain transition period, which affects Following. There are portions of the Followers database which produce postulate to last separately updated, yesteryear Blogger, subsequently the Transition catamenia is complete. During Transition, yous should facial expression to come across your Followers gadget temporarily unavailable. Shortly subsequently Transition ends, your Followers gadget should last updated, as well as it volition resume functioning - as well as your novel readers volition last able to Follow your blog, amongst no concern.

Other than during the iii to 4 twenty-four hr catamenia Transition period, your Followers should facial expression to come across no problems, inwards whatsoever relationships amongst your blog. As always, I'll only suggest yous to manage the migration, for whatsoever custom domain change.

>> Top

Monday, December 2, 2019

Blogger Magic - Custom Domain Publishing Too Search Engine Reputation

There's a lot of confusion seen inwards Blogger Help Forum: How Do I?, virtually our blogs, together with how they are treated past times the search engines, later on beingness published to a custom domain URL.

Does the Page Rank transfer to the novel domain?

and

Is the weblog automatically indexed later on the change?

and

Will my readers last able to honor my weblog later on the change?

Each of those questions has a elementary answer - but each elementary answer leads to interesting detail.

The basic facts to consider are quite simple.

Search engines index our blogs, together with calculate page rank, past times domain / subdomain URL. Better search engine reputation leads to better search listing placement, together with to a greater extent than traffic.
When you lot give away the weblog to a custom domain, you lot are giving it a novel URL.
With the weblog published to a novel URL, it has no page rank, together with is non indexed.

So, the immediate answer is reasonably simple.

Like a novel blog, together with similar a weblog renamed inside BlogSpot, a weblog newly published to a custom domain has Zero page rank, together with is non indexed.

Now, expect at the details.

Unlike a completely novel blog, a weblog newly published to a custom domain has reputation, inwards the minds - together with links inwards the blogs - of the readers.
Unlike a completely novel blog, in that location is an existing BlogSpot weblog that is indexed, has search engine reputation, together with right away links to the domain URL.
Unlike a weblog renamed inside BlogSpot, a weblog published to a custom domain has a DNS based redirect, from the BlogSpot URL, to the domain URL.
Unlike a weblog published to BlogSpot, a weblog published to a custom domain may bring closed to value precisely because of the non BlogSpot URL.

And hither is where the magic starts.

When you lot combine the assets, held past times the BlogSpot URL

Links, inwards our readers blogs.
Reputation, inwards our readers minds.
Reputation, inwards the search engines.

with the DNS based redirect - applied against a properly setup domain, together with using a proper complement of sitemaps - you lot instruct a weblog which acquires indexing together with page rank from the existing reputation of the erstwhile BlogSpot URL, every bit that BlogSpot URL, together with our readers blogs, are beingness re indexed. And, there is the magic.

>> Top

Wednesday, November 20, 2019

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.

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

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.

Custom Domain Publishing As Well As Abandoned Blogs

We've been exploring the issues of Custom Domain Publishing for many years. The work of custom domain database corruption, equally good known as

Another weblog is already hosted at this address.

is i of the nigh ordinarily observed symptoms, alongside custom domain publishing problems.

The nigh mutual crusade of the "Another weblog ..." symptom is broken database pointers. In the past, the broken pointers bring been associated alongside diverse Google Apps controlled services.

Ad Services.
Google Sites.
Start Page.

Now that Custom Domain Publishing is a mature characteristic inward Blogger, there's a newly seen trend, inward problems reported inward Blogger Help Forum: Something Is Broken.

Blogger Blogs.

Ever since nosotros started systematically diagnosing problems alongside custom domain publishing, as well as learned how to assail the nigh mutual problem, the "Another weblog ..." symptom, we've learned to piece of work an HTTP trace, as well as noted the many redirects to diverse services, inward the domain database, that are controlled past times Google Apps.

Now that Blogger has been using custom domain publishing for many years, we're starting to run across a novel tendency inward broken database pointers - Blogger blogs. Just equally abandoned Blogger blogs are becoming a normal observation inward general, as well as hence are abandoned Blogger blogs, published to custom domains.

Abandoned Blogger blogs are slowly plenty to diagnose - as well as similarly easy plenty to treat.

Blogger accounts, as well as BlogSpot addresses, create non expire.

The solution is simple.

Pick around other BlogSpot URL, as well as expose to that URL.

Custom domain URLs, however, should non endure treated that way.

If yous purchase a domain - whether using "Buy a domain", or straight from a registrar of your pick - yous facial expression that yous should endure able to piece of work that domain alongside whatsoever Blogger weblog that yous may already ain - regardless of whether around other Blogger weblog possessor has previously used that domain alongside around other Blogger blog. If yous ain a weblog which is instantly broken, because of a Google database work - as well as yous are stressed plenty over the URL alter - how create yous bargain alongside the domain existence broken, earlier yous tin laissez passer on notice fifty-fifty showtime to get the weblog re indexed?

Unfortunately, differing from Ad Services, Sites, as well as Start Page, at that spot is no Google Apps desktop sorcerer that lets yous reset your registered domain, as well as clear a previously published - as well as abandoned - Blogger weblog redirection.

As Blogger blogs - as well as custom domain publishing - becomes a to a greater extent than ordinarily used as well as abandoned service, this is going to expire a progressively to a greater extent than mutual scenario.

My custom domain is already published - to around other Blogger blog! Help!

And a to a greater extent than immediate as well as reliable solution needs to endure developed, than submitting a "Magical" Custom Domain Reset request.

(Update 2012/09/18): Blogger has provided domain ownership verification, equally business office of the domain setup. This solution has, predictably, provided new frustrations.

>> Top

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

Tuesday, November 19, 2019

Buying A Custom Domain Requires A Working Banking Corporation Issued Credit Card

As Blogger inwards general, together with custom domain publishing inwards particular, becomes to a greater extent than pop inwards Asia together with Africa, nosotros are seeing to a greater extent than problems alongside the Blogger / Google domain buy process. The basic problem, inwards Blogger Help Forum: Something Is Broken, volition hold upward expressed hence simply.

My spider web log is showing an off-site redirect.
You're most to hold upward redirected.

The spider web log that used to hold upward hither is directly at http://www.mydomain.com.
Do you lot wishing to hold upward redirected?
What produce I produce now?

Some fourth dimension ago, this written report would convey been diagnosed equally spurious DNS addresses - together with nosotros would indicate out the necessities of proper custom domain DNS addressing, when setting upward the domain yourself. Nowadays, an increasingly mutual diagnosis, for this problem, is an unsuccessfully purchased domain, using the Blogger / Google "Buy a domain" or Google Apps buy process.

Some spider web log owners, preparing to buy their domain, confuse the required banking concern issued credit bill of fare alongside an choice - the banking concern issued debit card. When purchasing products inwards stores, a "debit card" looks together with plant the same equally a "credit card". Apparently, non every "debit card" may travel the same, alongside the Blogger / Google Apps "Buy a domain" process. It appears that inwards precisely about countries, notably inwards Africa together with Asia, debit cards are becoming a pop choice to credit cards.

In precisely about cases, the spider web log possessor volition cheque alongside his bank, together with volition notice a token accuse of $1 (or the local currency equivalent minimum buy amount) posted to the concern human relationship - but the $10 (or local currency equivalent) accuse volition non hold upward found. Possibly, Google Checkout volition present the notation

Payment declined : No argue provided

The "Buy a domain" procedure volition appear to work, together with the Blogger spider web log "mybloggerblog.blogspot.com" volition hold upward re published - inwards Transition - equally "www.mydomain.com". The spider web log possessor volition notice out later on - after Transition expires together with the republishing is completed - that the BlogSpot URL directly shows an "off site redirect", because the domain was never registered.

The spider web log possessor may have electronic mail mentioning a problem.

Your service mightiness hold upward suspended.

Please pay your total due, $10.00.
You convey no valid forms of payment available for automatic charging.
Your banking concern or credit establishment has declined an automatic payment alongside your Visa ...XXXX together with provided the next reason: No argue provided. This course of pedagogy of payment can't hold upward used. Please contact your banking concern for to a greater extent than information, together with hence click the "Re-enable course of pedagogy of payment" link.

Apparently, banking concern issued credit cards travel differently from debit cards, inwards the "Buy a domain" process. The bottom business is that, alongside the "Buy a domain" procedure mentioning "credit card", you lot volition bespeak to render precisely that - together with a "debit card" may non render a reliable alternative. The reference Google Checkout: Troubleshooting Payments may render insight here.

>> Top

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.

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

When Using Purchase A Domain, Foreclose Interruptions

One of the saddest problems reports, seen inwards custom domain purchase process, starts with

I had a occupation amongst my credit card, too had to larn my depository fiscal establishment to allow my purchase. But now, I see
We establish an existing social club for this domain. Please contact support.

or maybe

I had to respond the telephone later I started my purchase, too at nowadays the domain that I wanted isn't available. How produce I larn the domain that should endure mine?

These occupation reports are from people who did non empathize how uncomplicated the domain purchase procedure is.

Select an available domain.
Provide registration too payment information.

That simplicity is based on a monolithic restriction.

The purchase procedure does non allow for interruption.

It is to your advantage, when purchasing your domain, to complete the purchase, quickly.

The domain purchase procedure is like to the spider web log setup process, equally y'all choose an available spider web log name. When y'all position an available too useful URL (or domain name), y'all ask to select (or pay for) that URL (domain name) immediately. As y'all purchase the domain mention of your dreams, retrieve that in that place are, at whatever time, upward to three groups of people looking for a domain.

You.
Other Blogger spider web log owners, looking to purchase a domain for their Blogger blog.
People exterior Blogger / Google, looking to setup a website.

Unfortunately, only i of y'all tin get got the domain name of your dreams.

Look again, how uncomplicated "Buy a domain" is.

Select an available domain.
Provide payment information.
Done. Get to work, planning the migration process.

The longer y'all take, betwixt starting Step #1 too completing Step #2, the greater the direct a opportunity that y'all may see

Sorry, this domain is non available.

as y'all consummate Step #2.

In or then cases, too when y'all specifically see

We establish an existing social club for this domain. Please contact support.

we tin offering y'all an alternative.

Clear cache, cookies, too sessions (all 3!), restart the browser, too drive again.
Wait 48 to 72 hours, too drive again.

This choice allows y'all to "try again". It does non guarantee that the domain that y'all chose volition yet endure waiting for you, when y'all drive again. Influenza A virus subtype H5N1 pop domain name, based on or then major cultural intelligence event, may endure gone inwards a affair of minutes. Wait 48 to 72 hours - too your gauge is equally practiced equally mine.

Maybe, nosotros should rewrite the purchase process.

Prepare.
- Call your bank, too larn your credit carte cleared for the purchase.
- Get a loving cup of coffee.
- Unplug the phone.
- Close the door of your office.
Select an available domain.
Provide payment information.
Done. Plug the telephone dorsum in, too rinse out the java cup.

Take xv minutes out of your busy schedule, too larn the purchase done. Then, provide to normal life.

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

Identify the domain authorization servers, typically using a Who Is lookup.
Dig each domain address (typically "naked domain" in addition to "www" aliases), from each of the identified domain authorization servers.
Extract in addition to aggregate each Dig log.
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.

Provide the "naked domain" in addition to "www" aliases.
Select "A" for "Type" ("A" / "CNAME" / "NS" lookups).
Select "Authoritative" for "Nameservers".
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

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:

>> Top

Custom Domain Publishing, Together With 403 Forbidden

Next to its immediate cousin error

Another spider web log is already hosted at this address

I don't know of likewise many to a greater extent than frustrating Blogger mistake states than seeing

403 Forbidden

Most cases of "403 Forbidden", seen in addition to discussed lately inwards have geographical affinity - in addition to are typically transient - in addition to utilise to blogs published to "blogspot.com".

Some cases of "403 Forbidden" however, volition involve custom domain publishing, where the spider web log possessor should - but nearly probable volition non - see

Another spider web log is already hosted at this address

When publishing the spider web log to the domain.

In simply about cases, when publishing a spider web log to an incorrectly setup custom domain, the custom domain publishing sorcerer volition neglect to discovery the wrong DNS addresses. Instead of the spider web log owner, seeing immediately

Another spider web log is already hosted at this address.

The possessor volition see

Your spider web log has been published.

Later, the spider web log possessor - in addition to all potential spider web log readers - run into the secondary symptom

403 Forbidden

Here, nosotros accept an splendid instance of the problem - diagnosis, in addition to treatment.

Let's get-go hold off at a Dig log extract.

jubileeventure.org.uk.    86400    IN    Influenza A virus subtype H5N1    94.136.40.75 www.jubileeventure.org.uk. 86400 IN    Influenza A virus subtype H5N1    94.136.40.75

Now, an HTTP draw extract, showing unsuccessful access to the domain.

Sending request:  GET / HTTP/1.1 Host: www.jubileeventure.org.uk User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20100101 Firefox/13.0.1 Referer: http://www.rexswain.com/httpview.html Connection: unopen  • Finding host IP address... • Host IP address = 94.136.40.75 • Finding TCP protocol... • Binding to local socket... • Connecting to host... • Sending request... • Waiting for response... Receiving Header: HTTP/1.1·403·Forbidden(CR)(LF)

The solution to this work involves a touchstone misconfigured domain diagnosis (excerpted here), in addition to requires DNS address correction.

Here's what you lot have:

jubileeventure.org.uk. 86400 IN Influenza A virus subtype H5N1 94.136.40.75
www.jubileeventure.org.uk. 86400 IN Influenza A virus subtype H5N1 94.136.40.75

Google custom domain publishing requires properly setup referrals to Google servers. "94.136.40.75" is non a Google server.

Here's what you lot need:

jubileeventure.org.uk. 86400 IN Influenza A virus subtype H5N1 216.239.32.21
jubileeventure.org.uk. 86400 IN Influenza A virus subtype H5N1 216.239.34.21
jubileeventure.org.uk. 86400 IN Influenza A virus subtype H5N1 216.239.36.21
jubileeventure.org.uk. 86400 IN Influenza A virus subtype H5N1 216.239.38.21
www.jubileeventure.org.uk. 86400 IN CNAME ghs.google.com.

>> Top

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

Custom Domain Publishing Does Non Purpose Post Feed Redirect

One of the benefits of custom domain publishing, for a properly setup domain, is that the BlogSpot URL is automatically redirected to the domain.

Not all weblog owners realise that the BlogSpot to domain URL redirect includes the weblog feed - 1 time the Transition period ends, in addition to the weblog is republished to the domain.

Some weblog owners intend that the Post Feed Redirect setting needs to live on used when re publishing their weblog to a custom domain. This is non true, however. Use of the custom domain redirect, addition the post feed redirect, tin solely number inwards 1 of 2 problems.

A feed redirect loop.
A feed URL that points to invalid content.

In neither illustration volition whatever newsfeed client, such every bit a Dynamic Template, Google Reader, Reading List, or whatever 3rd political party feed service, honor a feed that tin live on used.

The Post Feed Redirect setting is used to redirect feed references, to a separately existing feed file.

The Post Feed Redirect is non used where it is non needed - in addition to amongst a weblog published to a properly setup custom domain, it's non needed.

Let's await at an HTTP trace, showing the weblog feed for a custom domain published blog, that uses a post feed redirect - inwards this case, nosotros stimulate got the feed for "mybloggerblog.blogspot.com" redirected to "mybloggerblog.com".

Start amongst the BlogSpot based feed URL, for "mybloggerblog.blogspot.com".

Sending request:

GET /feeds/posts/default HTTP/1.1
Host: mybloggerblog.blogspot.com
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20100101 Firefox/14.0.1
Referer: http://www.rexswain.com/httpview.html
Connection: close

• Finding host IP address...
• Host IP address = 74.125.224.106
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...

Receiving Header:
HTTP/1.1·301·Moved·Permanently(CR)(LF)
Content-Type:·text/html;·charset=UTF-8(CR)(LF)
Location:·http://www.mybloggerblog.com/feeds/posts/default(CR)(LF)

With a properly setup custom domain, in addition to no PFR setting used, the adjacent display would live on the XML file, for the feed. Here, the PFR was develop to "http://mybloggerblog.com/".

Sending request:

GET /feeds/posts/default HTTP/1.1
Host: www.mybloggerblog.com
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20100101 Firefox/14.0.1
Referer: http://www.rexswain.com/httpview.html
Connection: close

• Finding host IP address...
• Host IP address = 74.125.127.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)
Location:·http://mybloggerblog.com/(CR)(LF)

Now, nosotros are looking at a typical custom domain rootage to "www" alias redirect.

Sending request:

GET / HTTP/1.1
Host: mybloggerblog.com
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20100101 Firefox/14.0.1
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·301·Moved·Permanently(CR)(LF)
Location:·http://www.mybloggerblog.com/(CR)(LF)

And now, nosotros are looking at the formatted weblog contents - non the newsfeed.

Sending request:

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

• Finding host IP address...
• Host IP address = 74.125.127.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)

Unfortunately, the weblog itself is non a proper XML file (required for a feed), it's HTML / XML.

<!DOCTYPE·html·PUBLIC·"-//W3C//DTD·XHTML·1.0·Strict//EN"·"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">(LF)
<html·dir='ltr'·xmlns='http://www.w3.org/1999/xhtml'·xmlns:b='http://www.google.com/2005/gml/b'·xmlns:data='http://www.google.com/2005/gml/data'·xmlns:expr='http://www.google.com/2005/gml/expr'>(LF)
<head>(LF)

...

<link·href='http://www.mybloggerblog.com/'·rel='canonical'/>(LF)
<link·rel="alternate"·type="application/atom+xml"·title="Custom Domain Publishing Does Not Use Post Feed Redirect"·href="http://www.mybloggerblog.com/feeds/posts/default"·/>(LF)
<link·rel="alternate"·type="application/rss+xml"·title="Custom Domain Publishing Does Not Use Post Feed Redirect"·href="http://www.mybloggerblog.com/feeds/posts/default?alt=rss"·/>(LF)
<link·rel="service.post"·type="application/atom+xml"·title="Custom Domain Publishing Does Not Use Post Feed Redirect"·href="http://www.blogger.com/feeds/2302596229887627781/posts/default"·/>(LF)
<link·rel="EditURI"·type="application/rsd+xml"·title="Custom Domain Publishing Does Not Use Post Feed Redirect"·href="http://www.blogger.com/rsd.g?blogID=2302596229887627781"·/>(LF)
<link·rel="me"·href="http://www.blogger.com/profile/12619425977406185402"·/>(LF)
<link·rel="openid.server"·href="http://www.blogger.com/openid-server.g"·/>(LF)
<link·rel="openid.delegate"·href="http://www.mybloggerblog.com/"·/>(LF)

And if the feed customer is, for instance, a dynamic template, the would live on reader is looking at the former spinning gears. Until he gets bored, closes the browser, in addition to emails you

Your weblog is downwards - again.

If you lot stimulate got made this mistake, merely clear the Post Feed Redirect.

Blogger Does Non Bring An Ftp Server

One sign of confusion, seen occasionally inwards Blogger Help Forum: How Do I?, involves the purpose of FTP - too options for updating our blogs.

How exercise I position out my posts using an FTP desktop program?

and

How exercise I upload a custom abode page (sitemap, .htaccess, etc)?

People who are used to publishing a website encounter these options equally a normal characteristic inwards whatsoever website maintenance process.

Blogger, however, is a blogging platform - too provides none of these options.

Until several years ago, Blogger used FTP equally a publishing procedure - for externally hosted blogs. Having developed Custom Domain Publishing equally a characteristic to replace FTP Publishing, Blogger after discontinued FTP Publishing.

Blogger does non render for custom files, such equally an uploadable abode page, sitemap, or .htaccess file. The Blogger infrastructure makes those features irrelevant. Nor does Blogger provide an FTP server for uploading custom files - or fifty-fifty posts, for publication.

Blogger provides us the Posts Editor (for editing too publishing posts), the Template Editor (for choosing too editing the template), too a host of miscellaneous dashboard utilities (for making diverse settings changes). And, nosotros bring Google Webmaster Tools, for publishing a sitemap too other search engine related adjustments.

Everything that nosotros need, nosotros tin respect from our dashboard, at http://www.blogger.com - or from using recognised tertiary political party desktop programs similar Windows Live Writer.

>> Top

The Onetime Simply About Other Weblog ... Work - Volition It E'er Live On Fixed?

The mightiness to order out a Blogger weblog to a non BlogSpot URL - likewise known equally "Custom Domain Publishing" - has been a Blogger selection for over v years. We have, similarly, observed the work which is collectively described equally "Another weblog ..." for almost that long.

Every week, nosotros meet the signs of frustration inward many different causes.

One of the challenges of dealing amongst "Another blog" starts amongst the different problems which campaign this symptom - in addition to amongst the different parties involved inward the problems.

The most mutual campaign of the symptom, originally - which contradicted the wording of the message - came from the domain DNS addresses existence improperly setup yesteryear the weblog owner. There are many ways to suspension the DNS addressing.

With domains purchased through the Blogger / Google "Buy a domain" wizard, a work amongst the buy procedure tin campaign wrong / missing DNS. Trying to purpose an unsuitable banking concern work concern human relationship volition campaign payment refused yesteryear the bank.

With the domain properly purchased in addition to setup, in addition to pointing to the proper Google servers, the diverse mappings inside the Google database, which connect the diverse services to non Google domain URLs, tin campaign problems. Services similar AdService, Google Sites, in addition to Start Page, similar Blogger, tin hold upwards mapped to a non Google domain. An existing database pointer to whatsoever such service, for the domain, volition campaign the Blogger Publishing magician to study "Another weblog ...".

Influenza A virus subtype H5N1 lately observed variation on the existing database pointer involves the domain, previously used yesteryear or in addition to thence other Blogger weblog owner, who merely stopped paying for the domain registration. The domain expired (which is how the domain was precisely re published) - but existing Blogger / Google mappings remain.

The causes of the offset ii problems (DNS addressing errors, in addition to domain registration payment) are completely the responsibleness of the weblog / domain owner.

In or in addition to thence cases, the latter ii problems (AdServices / Sites / Start Page / previously published Blogger blog) tin hold upwards reset yesteryear submitting recycling domain settings, using Google Apps.

Both the Custom Domain Reset request, in addition to the Google Apps based domain settings recycling process, tin campaign problems. We were, long ago, advised yesteryear Blogger Support that not all mappings tin hold upwards cleared yesteryear purpose of the form. And the complexity in addition to lack of construction inward the recycling process, tin motivate or in addition to thence weblog owners to endeavour other, inappropriate solutions.

The bottom trace is that the "Another blog" "problem" - fifty-fifty amongst magicians volition advise unilateral solutions, which volition satisfy specific weblog owners - but a universal solution is highly unlikely.

>> Top

The Sometime Only About Other Spider Web Log ... Occupation - The Domain Settings Inward Google Apps

The role of Google Apps, for resetting the domain settings, oft requires much repetition - yet seldom produces consistent results. Some weblog owners are able to disable a unmarried service to acquire their domain working, others must recycle the service settings repeatedly - in addition to nevertheless others must pass fourth dimension anxiously recycling 1 service after another, in addition to hence looking for more, unnamed services to recycle.

Some weblog owners expect for shortcuts inwards the recommended procedure - such equally deleting the Apps account, which only wastes time. Unfortunately, rattling few shortcuts, when identified, are consistently effective for other weblog owners later. This lack of consistency leads to diverse comments mentioning lack of useful advice, inwards the forum discussions.

There are basically iv levels of complexity involved, inwards the procedure of resolving "Another weblog ...".

Disable 1 named service.
Recycle 1 named service.
Disable multiple services, 1 past times one.
Recycle multiple services, 1 past times one.

When the weblog possessor is able to depict a Sites page display - or nosotros tin role an HTTP delineate to position a Sites redirect, nosotros tin amongst roughly confidence propose the possessor to only disable the Sites service. If only disabling Sites (or whatever named service - AdServices, Start Page, what convey you) is non effective, nosotros in addition to hence propose recycle the settings, against the named service.

The close basic domain work study starts amongst a simple

I continue seeing
Another weblog or Google Site is already using this address.
when I essay to divulge my blog.

Problem reports submitted amongst this lack of detail, on the other hand, will, close likely, need the possessor to recycle multiple service, 1 past times one.

Besides the confusion resulting from the multiple levels of complexity, non all weblog owners setup a Google Apps desktop concern human relationship to administer the domain - fifty-fifty when they purchased the domain using "Buy a domain", in addition to got the "Welcome to Google Apps" e-mail upon purchasing. Influenza A virus subtype H5N1 weblog possessor who used "Buy a domain", in addition to neglected to setup the provided Apps account, volition last unable to role Apps - in addition to volition last unable to access the eNom or GoDaddy Domain Manager, when necessary.

When the domain is purchased direct from a registrar, the weblog possessor is nevertheless less probable to proactively setup the Google Apps account. Fortunately, amongst the domain purchased direct from the registrar, in addition to having exactly setup the DNS addresses to divulge the weblog to the domain, the weblog possessor volition convey immediate access to the registrar's Domain Manager wizard.

Another origin of frustration, involving the service recycling, is that recycling may need showtime repairing bogus DNS addresses. Having learned the procedure of correcting improper DNS addresses, the weblog possessor must adjacent larn the intricacies of setting upward the Apps account, in addition to hence of recycling multiple service settings, repeatedly.

The solution, recommended past times Blogger Support, is to submit a reset asking using the "Custom Domain Reset" form. This is not a universally effective solution, unfortunately.

Like many services provided past times Blogger Support, in that place is no laid schedule for actioning Domain Reset requests.
We are never certain what direct feedback volition last provided, to the weblog owner, upon completion of a reset request.
We convey been advised past times Blogger Support that non all instances of "Another blog" volition last consistently resolved past times role of the reset asking form.

Considering all of these concerns, it's understandable that many weblog owners acquire frustrated, in addition to are occasionally observed stating their intention to render their blogs to BlogSpot hosting.

>> Top