Showing posts with label Custom Domains Purchase. Show all posts
Showing posts with label Custom Domains Purchase. Show all posts

Thursday, April 7, 2016

Search Engine Reputation, And Vanity Domains

One hot Internet topic, these days, involves specialised ("vanity") domains.

The hot names seem to change, by the week. This week, enom is hyping ".family", ".live", ".rocks", and ".social". Other registrars may have other recommendations.

The blog Address (Name) is a key blog identity element, in a well designed blog. It's visible both to people, and to search engine crawlers.

The requirement that addresses must be unique is a supposed benefit of vanity top level domains - but vanity TLDs, alone, will not provide blog uniqueness. There will always be competition for some names, in any useful Top Level Domain.

My suspicion is that the shinier the TLD, the more competition you may see, between people who plan their uniqueness around choosing the perfect name.

Any popular blog / website subject will have name competition.

I could publish this blog as "chucksblog.com" - and that would be a shiny and unique name. Until another "Chuck" registered "chucksblog.us", or maybe "chucksblog.name". How unique would "chucksblog" be, then? How many readers could I expect, if they know "chucksblog" - but can't remember if it is "chucksblog.com", "chucksblog.info", or "chucksblog.name"?

If your blog has a popular subject, you won't have a unique name - unless you register your name, in every possible TLD that might be relevant to your name. And that will be a financial limitation, for many blog owners.


What name would you want your blog to have? For a truly shiny domain, you'll have competition.

Complete uniqueness == No competition == No interest == No readers.



McDonalds, for instance, may be able to register "mcdonalds.com", "mcdonalds.franchises", "mcdonalds.hamburgers", "mcdonalds.smallbusiness", etc (as each hypothetical TLD comes online) - and local domains "mcdonalds.co.uk", "mcdonalds.de", "mcdonalds.us", and so on.

Very few of the readers of this blog will be in a financial position to do all of that.


enom is hyping ".family", ".live", ".rocks", and ".social" - this week.



Your uniqueness strategy should include content.

You will have to develop a "uniqueness" strategy based on content - not solely on the address. You will need to understand that your blog may lose traffic, from people who know the blog "name" - but may not remember if "yourname" is a ".com", ".net", or ".us".

Of course, if you publish only to "blogspot", you will automatically have "yourname.blogspot.com", "yourname.blogspot.co.uk", "yourname.blogspot.de", and so on. You won't have "yourname.com", "yourname.net", and "yourname.us", however - unless you pay for the privilege.

Are you getting a feeling for the complexity of the branding issue? Good. Concentrate on content. The search engines index your blog - and provide you traffic - based on informative, interesting, and unique content.

Google denies the value of vanity domains, for raw SEO.

AdWeek weighs the issue, in What’s in a Name on Social?.

When it comes to vanity domains, Google has long denied that they affect search rankings. Their in-house tech team advised way back that registering a vanity domain for the sheer, hopeful sake of page rankings would be a fool’s errand. But there’s a solid number of marketers that disagree, and they watch these things very closely. Chalk it up to wishful thinking, if you like, but time will tell. And there are only so many .com domains available.

Only time will tell. I suggest that you keep your traffic and uniqueness strategy diverse. Don't depend upon a vanity domain, alone, for search reputation and traffic.

For best results, keep it in perspective.

Consider the name issue, if you want. But keep it in perspective. Blogger blogs will benefit from well written and unique content - as much as from a carefully chosen name / URL.



Some #Blogger blog owners are intent on publishing a blog to a custom domain, using a top level domain that relates to the blog subject. They do this, hoping to have a unique blog name.

They may overlook the idea that Blogger blogs benefit from well written and unique content, as much as from a shiny and unique URL.

Sunday, January 11, 2015

Google Domains Is Not Yet Available, Worldwide

Some would be domain owners are reporting the sad truth about Google Domains.
I tried to use a Google Domains invitation, and got a refusal.
We're sorry. You appear to be in a country where Google Domains is not yet available. You may search for domains, but you will not be able to purchase a domain unless you have a U.S. billing address. Learn more

Get notified when Google Domains is available in your country.
So thanks anyway!
Google Domains is currently a beta product - and as of December 2017, it is available in 14 countries.

This is a normal strategy, used by Google - beta products are typically deployed on a country by country basis.

Google Domains offers distinct advantages, over "Buy a domain" and registrar direct domain purchases.

  • They will control the purchase - and offer a more stable bank payment process.
  • They will control the DNS infrastructure - and offer a more stable setup process, and ongoing blog access.
  • They provide excellent real time support, 7 x 24 basis.

Google Domains are available in a few countries - with more being added, periodically.



As of March 2018, Google Domains may be available in 15 countries - Australia, Brazil, Canada, France, India, Indonesia, Italy, Japan, Mexico, Netherlands, Spain, Thailand, UK, USA, and Vietnam. If you live in any of the other 180+ countries, you have to use GoDaddy - or another third party registrar.

Deploying a bank payment network, and a DNS infrastructure (to name two details), on a world wide basis, won't happen immediately.

It's all too easy to overlook the international issues, when dealing with Blogger and Google. My apology to those of you who were unduly excited, for nothing.

Have patience, your time will come.

Wednesday, January 7, 2015

Google Domains DNS Addresses Setup

After too many years of Blogger blog owners struggling with setting up their custom domains, Google is now selling domains - though right now, in a select number of countries.

Having ended "Buy a domain", and its problems - and now dealing with blog owners setting up domains purchased through numerous registrars, and those problems - Blogger / Google has cleaned up the domain purchase and setup process.

This year, we see Google Domains - where Google actually registers domains, and can control the DNS hosting. And, they have developed a clean and lean dashboard / zone editor, for maintaining their domains.

I setup a Google Domain, several months ago.

Adding DNS addresses to a recently purchased Google Domain is quite simple. Start by logging in to Google Domains.

Once you login, you have the Google Domains dashboard Home page. Find your domain, in the list - and select the "DNS" icon,for your domain.

That gives you the "DNS" dashboard, for your domain. This is also known as the "Zone Editor", in some instructions. Scroll to the bottom of the "DNS" dashboard, and "Custom resource records".

There are the 4 x "A" + "CNAME" entries. You will have a different domain - but your address entries will be otherwise similar to what you see (with either "ghs.google.com.", or "ghs.googlehosted.com.").


Add the first address entry. Paste "216.239.32.21" into the box labeled "IPv4 address", and hit "Add".

Add 3 more addresses - "216.239.34.21", "216.239.36.21", "216.239.38.21" - in the same way. Then, change "@" to "www", select "CNAME" in place of "A" in the pull down menu, enter either "ghs.google.com.", or "ghs.googlehosted.com." into the address box, and hit "Add" for a 5th time.

Checkout the zone editor, for your domain. It should be similar to what you see, above. This is the well known "asymmetrical" DNS configuration, provided by "Buy a domain", not so long ago.

I don't think manual DNS address setup could be much simpler.

With the new domain properly addressed, wait 24 to 48 hours hours for the domain to propagate, then go to the Settings - Basic page of the Blogger dashboard.


Select "Setup a Google Domains URL for your blog", and follow instructions.



Use the "Setup a Google Domains URL for your blog" link in the Publishing wizard, in Settings - Basic to connect the blog to the domain.

Then get to work, publishing more content in your newly addressed blog.

Saturday, April 14, 2012

The Simplicity Of A Custom Domain Setup

Custom domain publishing is a very simple way to give your Blogger blog a non BlogSpot URL - when you follow the recommended procedure.

Along with the simplicity, you'll find rather rigid requirements, when any alternative procedure is used.

Too many blog owners, unfamiliar with the complexity of the custom domain infrastructure, try to "fly by the seat of their pants", when they see a requirement that they don't understand.

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

First, understand some of the most common mistakes, made by too many blog owners. Blog owners in the USA may use Google Domains, though others must purchase directly from a registrar.

That reality does not change any of the necessities of proper domain setup, however. Substituting for "Buy a domain", Blogger offers instructions, in How do I use a custom domain name for my blog?.

There are 3 - and only 3 - supported DNS Models.

To understand the significance of the mistakes that are commonly made, first understand the three basic DNS models, involved in custom domain publishing.

  1. Published To Domain Root - Symmetrical DNS Configuration. The most 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 you have a domain with email, FTP, and other possible auxiliary services, you use an asymmetrical structure, which use Google Apps to let you add auxiliary services, with quadruple DNS server redundancy.
    mydomain.com.  3600 IN A 216.239.32.21
    mydomain.com. 3600 IN A 216.239.34.21
    mydomain.com. 3600 IN A 216.239.36.21
    mydomain.com. 3600 IN A 216.239.38.21
    www.mydomain.com. 3600 IN CNAME ghs.google.com.
  3. Published To Non Root Virtual Host. If you wish to add an additional blog to the domain, maybe to add your Blogger blog to your web site, you setup an additional virtual host.
    blog.mydomain.com. 3600 IN CNAME ghs.google.com.

The "Buy a domain" wizard produces an Asymmetrical Configuration. Choice of any one of the three above models determines what URL you may publish the blog.

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

The published URL is one of the most frequent causes of problems. Do not make any of these mistakes.
  • Only publish to a URL defined by "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 any of a myriad other variations in spelling.
  • Do not publish to a URL defined by "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 not target the domain root, or any other indirect address.
  • Understand how to define a referral host.
  • Only publish to a referral host using lower case letters.

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

If you use an asymmetrical DNS addressing, target only the four Google servers, as "A" referrals.


216.239.32.21
216.239.34.21
216.239.36.21
216.239.38.21

Use of these four servers is very specific. Do not make these mistakes.


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

If you use "CNAME" referral for any host, only use one "CNAME" referral - do not add 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 second "CNAME" referral is not helpful - and is not supported by many registrars.
    www.mydomain.com. 3600 IN CNAME ghs.google.com.
    www.mydomain.com. 3600 IN CNAME ns1.googleghs.com.
    This is not helpful.
  • An additional "A" referral is not helpful - and is not supported by many registrars.
    www.mydomain.com. 3600 IN CNAME ghs.google.com.
    www.mydomain.com. 3600 IN A 64.233.179.121
    This is not helpful.
  • You will, however, probably need a second "CNAME" for domain ownership verification. You cannot bypass this requirement - when it is required.

If you must setup the domain yourself, instead of using "Buy a domain", learn the rules - none of them are optional. If you follow the rules, you have a much better chance of having a reliable and working domain - instead of eventually seeing the well known "Another blog ..." or "404 Server Not Found".

Saturday, April 7, 2012

Confusion Over Domain Expiration Dates Caused By "Buy a domain" Renewal

We're seeing some reports of panic, from a few Blogger blog owners who recently renewed registration of their "Buy a domain" purchased custom domains, with Google Apps informing them that their domain registration is now renewed - but with a back dated expiry. This appears to be a known Google Apps issue.

Roberto of "robertosblogs.net", in Another Google Stuff-up, shows us the confirmation letter, that he recently received from Google Apps.
This message confirms we have renewed your domain registration for robertosblogs.net with GoDaddy.com . Your credit card has been charged $10 and your domain registration is valid until April 5, 2011 .
Some people, reporting this scenario in Blogger Help Forum: Something Is Broken have been rather panicked, and fearful either that they had just wasted $10 - or that their domain now needs an additional payment (for 2 years?).

Fortunately, an online lookup service such as the Name.com Who.Is display can provide the necessary detail, and help set the concerned owner straight.
REGISTRY WHOIS FOR ROBERTOSBLOGS.NET
Domain Name: robertosblogs.net
Updated: 2 seconds ago - Refresh

Registrar: GODADDY.COM, LLC
Whois Server: whois.godaddy.com
Referral URL: http://registrar.godaddy.com
Status: clientDeleteProhibited, clientRenewProhibited, clientTransferProhibited, clientUpdateProhibited

Expiration Date: 2013-04-06
Creation Date: 2008-04-06
Last Update Date: 2012-03-15
Relax a bit, Bob, and enjoy a cuppa.

>> Top

Thursday, April 5, 2012

Confusion Over Domains Purchased From Registrars

Blogger / Google offers the optional ability to publish a Blogger blog to any available non BlogSpot URL, aka "Custom Domain Publishing".

The process of setting up a custom domain is so simple - when we use the "Buy a domain" wizard. As simple as "Buy a domain" is, it involves details that are unbelievably complex - and too many blog owners, avoiding use of "Buy a domain", will find out about these details the hard way.

One important detail about custom domain publishing involves the level of service, as purchased from the registrar. There are three basic levels of service, offered by many registrars.
  1. Name registration, only.
  2. DNS hosting / Name registration.
  3. Content hosting / DNS hosting / Name registration.
Choose the wrong service level, and you'll waste either time - or money. And, we all know that "time is money".

Too many blog owners, anxious to setup and show off their new, non BlogSpot URL, make the wrong choice of service.

Blog owners, unsure how to purchase their domain, become more forum noise.

They end up in Blogger Help Forum: Something Is Broken, anxiously asking

What are the nameservers used for Blogger?

or

How do I publish my blog, using the registrar's Site Builder wizard?

The mistake of purchasing the wrong service is always a possibility, when buying directly from a registrar.

Please, only purchase "DNS Hosting" - not "Name Registration"!

Since custom domain publishing was first offered as an option, I've been advising people to

Please, check the invoice or receipt from the registrar. If you purchased "Name Registration", instead of "DNS Hosting", you need to go back immediately, and upgrade your service.

GoDaddy, for instance, offers "Bring your own DNS", where they register the domain on your behalf, and you provide the nameservers. If you understand DNS, you are entitled to try this option - just please don't publish your blog and try to advertise it in Blogger Help Forum: Something Is Broken as a solution.

GoDaddy "Bring your own DNS" is not an acceptable choice.

"Bring your own DNS" is simply not an advisable option, for 99.99% of all Blogger blog owners - and we do not need people suggesting it, as an immediate choice.

The sad thing is that Blogger, in even their current tutorial (which is, itself, subject to change), makes no canonical distinction between the three levels of service that the various registrars may offer. Long ago, they simply advised

... you only need to get the domain name; you don't have to pay extra for hosting service.

With that history, is it any wonder that we should expect to occasionally see the confusion

What are the primary and secondary DNS servers?

And having purchased "DNS Hosting", the blog owner must then setup the DNS addressing.

Friday, January 13, 2012

When You Search For Important Email, Search Carefully

Many Blogger / Google procedures involve email communications, with you needing to read - and respond to - email from Blogger / Google.

Some email systems automatically sort incoming email, and put important (and not so important) email into different folders. Many times, email from Blogger / Google may be sorted into a folder where you would not always normally look - or may be sent to an email address that you might not think of, immediately.

It's to your personal advantage, to find any email that is being sent to you - even stuff in Bulk / Spam.

One of the best known folders, besides Inbox, where email may be found would be "Bulk" / "Spam".

"False Positive" filter effects are unavoidable.

All email systems may occasionally put important email into either "Bulk" or "Spam". Any time when you are awaiting important email from Blogger / Google, such as when you are trying to recover access to your blog, or when you make (or maybe, need to make) an important purchase, always look in both the "Inbox" and "Bulk" / "Spam" folders.

If your email system provides an "Incoming" mail log, it's never a bad idea to scan the log, periodically.

Consider all possible email accounts that you might own.

Besides checking the multiple sections of any one email account, you should also consider the complex interactions between Blogger accounts, email clients, and Google accounts, and examine any possible email addresses - both GMail and non GMail addresses - current and past, with similar persistence.

Consider all individual email accounts, that may be combined automatically.

If you use GMail, or any email delivery service which provides ability to manage and use multiple email accounts from a single email desktop, you should check settings in every such email system, for multiple account setup.

Your Blogger account needs to be based on an active email account (GMail, or non GMail). If you are intentionally obscuring your Blogger account, you're going to have a problem here. There are various reasons why you may not see every key email message, in your Inbox, at first glance.

Diligent searching may reduce time spent in online forums.

Searching for incoming email, carefully, may reduce the amount of time you spend in Blogger Help Forum: Something Is Broken, asking for help retrieving your account name or email address from Blogger records, or asking why your non BlogSpot URL now redirects your readers to a page full of advertisements.

Prevent disappointment and future regret - check your "Bulk" / "Spam" folders, for all possible email accounts and clients which you use, periodically. And consider possible spoof filtering effects.

Sunday, January 1, 2012

Choose Your Registrar, When Buying A Domain

When you purchase a domain - either as part of the "Buy a domain" wizard, or when you purchase directly from a registrar - you are free to use any registrar that you wish, for the purchase. The "Buy a domain" wizard (which should be your preferred method of purchase) lets you use either eNom or GoDaddy - and which registrar you use is your choice - though the choice is not made obvious, by the wizard layout.

The selection of which registrar to use, in "Buy a domain", is always your decision - though the selection process is somewhat obscure. Just go slowly, and look carefully for the right link.

Start from the Good News display. Find the tiny link at the bottom - "Learn more", next to the name of the chosen registrar.


And, there it is. If you don't like the choice made for you, pick the other.



The choice is right there - you just have to know where to look.

>> Top

Monday, March 22, 2010

The "Buy a domain for your blog" Wizard Is Broken

Sometimes, you have to tell people something twice, before they will listen to you. This month, the "Buy A Domain" wizard has that problem.

As always, start from Settings - Publishing, and select "Switch to: • Custom Domain". If you were buying "mydomain.net", for "What address would you like your blog to have?" you should simply enter "mydomain", select ".net", then hit "Check Availability". This month, if you do that, you will see
There was an error processing this form. Please try again.

URL should end in a valid domain extension, such as .com or .net.


In this case, you must enter "mydomain.net", then select ".net". The ".net" bit is validated, too. If you enter "mydomain.com", then select ".net", you'll get the same error.

Strange, but true.

>> Top

Thursday, March 18, 2010

Setting Up A Custom Domain

Having written my referential guide Troubleshooting Your Custom Domain Problems, I have seen more than a few questions in Blogger Help Forum: Something Is Broken that are solved by use of the guide. Maybe you can avoid use of that guide, if you plan ahead of time.

The vast majority of all bloggers, when seeking to publish their blog to a custom domain, will do quite well to use the "Buy A Domain For Your Blog" wizard.
  1. Have a major bank issued credit card, for an account that's in good standing, in hand.
  2. Pick an available domain.
  3. Provide the credit card information.
  4. Get the email from Google Apps.
  5. Setup your new Google Apps account.
  6. Get to work planning and managing the transition to the new URL.
  7. If you just completed step #6, please skip to the end of the article, now. What's below is not your concern.


As of 2013/06/23, "Buy a domain" is no longer offered, as part of "Add a custom domain".
Maybe you can't use "Buy A Domain", for your purchase.If you're in this group, I suggest that you plan the setup process, and similarly, the domain renewal options. Save yourself (and us) a lot of headache, by considering the details, before you purchase.
  1. Choose a registrar that will provide the proper DNS services, and the required support. Even if you cannot use "Buy A Domain", you may do well to use eNom or GoDaddy as your registrar, if possible.
    • We are more familiar with their procedures and wizards. We can provide corrections, for well known problems.
    • Their CSRs are becoming increasingly familiar with needs of Google Custom Domains.
    • We are reasonably certain that they are able to provide the necessary services.
    • As a GoDaddy customer, you can use the Blogger / GoDaddy "Update your DNS records" wizard, to setup your DNS, after your domain is registered by GoDaddy.
    It's your choice, but you can make it easier for yourself, and for us.
  2. Setup the DNS addresses properly, using one of three models. For details, please see:
  3. Re publish the blog to the new domain. Select the "Redirect" option (if desired). Note that even if you do not (or cannot) redirect one URL to another, using one of the three models is seriously recommended.
  4. Setup a new Google Apps account (if necessary).
  5. Get to work planning and managing the transition to the new URL.

This is simple advice, but it will be worth your while to understand the requirements, and to execute the details, religiously. Custom domains are very simple, in concept - but if you set one up wrong, you can have all sorts of problems.

Get it right, from the start. Make it easier, for everybody.

>> Top

Friday, August 29, 2008

Blogger Is Not Defrauding Anybody

With the current state of Custom Domain Publishing, and the bX codes that have become so common as of late, we're seeing some unhappy bloggers.
People are getting ripped off it seems like.
BLOGGER WHAT IS GOING ON!
and
I bought my domain from GoDaddy and it doesn't work! I want my money back!!


But, as has been mentioned before, once you buy the domain registration, it's yours, and you don't get your money back.

If you buy the domain using the "Buy A Domain" wizard, the domain is registered to you, and you get email from Google Apps, it's your domain. If the Blogger script doesn't succeed in connecting the domain URL to your Blogger blog (BlogSpot URL), the domain is still yours. Ditto if you buy the domain from GoDaddy and the DNS isn't setup for you.

You take your Google Apps email, sign into eNom or GoDaddy, and correct the DNS. Once the DNS is setup, you can publish any web site that pleases you to your domain. Maybe you can't publish a Blogger blog to your domain, until Blogger fixes their problems, but you didn't pay anything for that.

You paid $10 USD (probably) for domain registration and DNS hosting. There's no fraudulent acceptance of funds for a non working service. You got what you paid for.


Here, I paid $10 USD to GoDaddy. You may pay GoDaddy, or maybe eNom, or possibly a third party ISP, independently. Nobody pays anything to Google.


And when I purchased my latest domain, I "signed" a Go Daddy Domain Name Registration and Services Agreement.

But, do let Blogger know about the bX code that affected you, or any other problem. Just don't expect overnight resolution.

>> Top

Monday, March 24, 2008

Using The "Buy A Domain For Your Blog" Wizard

The Blogger "Google Custom Domain" product, which gives bloggers a much requested ability to use a non-BlogSpot URL with a Layouts template, was first offered over a year ago, in January, 2007. I've been writing about Custom Domains ever since - the basic procedure of setting one up, and about the problems involved, and even about the many improvements that it's received.

One of the many improvements noted was the "Buy A Domain For Your Blog" Wizard, which replaces (and greatly simplifies) the painfully tedious, and needlessly technical, setup process for many bloggers. Yet all of my writing about the wizard was purely from observation, and from analysis of the problem reports in the forums. Until today, I didn't actually setup a domain, using the wizard.

So, let's cut to the chase, Chuck. What's it like?

It started with a bit of apprehension. I decided to do this, as I do many things, based upon a practical goal. A goal of having my own personal domain - "nitecruzr.net". And the apprehension was two fold.
  1. Maybe the wizard will hose my domain, as it has so many others.
  2. Maybe I won't even be able to setup my domain. What if "nitecruzr.net" is already taken? Oh no, my own personal episode of "That URL is already taken.".
Ever mindful of the "Domibot" issue, I decided to not even check for availability, until I was ready to actually buy the domain, if available.

So this morning, I gathered myself together, and tackled the wizard. With credit card in hand, and disappointment in mind, I approached Settings - Publishing - "Switch to: • Custom Domain".


Select "Switch to: • Custom Domain".



Enter the domain name, and select the Top Level Domain. For TLD, we have the choice of "com", "net", "info", "org", or "biz".



Go for it. Check Availability.



Hooray! It's available. So, take it!



Of course, it's not free, like the rest of Blogger is.



Place The Order, Chuck. Note here, you need a working, major credit card, before starting the purchase process.



Yay! We have "nitecruzr.net".



Oh no! Not that!!


Fortunately, all is not lost. Simply recycle the domain settings, using Google Apps.

Maybe the latter test result is what motivated Blogger to now put newly setup custom domains into a three day "In Transition" period. Anyway, having setup the base custom domain, I am now able to add virtual hosts, and construct my domain cluster, Nitecruzr Dot Net, and include all of my blogs into one web site.

Note that use of the "Buy a domain" wizard is simply one alternative of three, in proper custom domain setup. And note the complementary activities, which you need to perform, during the three day Transition period, that starts when you successfully purchase the domain.

>> Top

Friday, March 14, 2008

You Buy It, You're Stuck With It

When you buy a new automobile in the USA, there's a consumer protection clause in most finance plans.

This protection is called "right of recession". When invoked properly, it gives you, the consumer, the choice of terminating the purchase up to 3 days following your signing on the bottom line.

Many retail stores give you the choice of returning some (not all) items purchased in their store, when accompanied by the right contents and documentation, for full or partial refund of purchase price.

When you purchase a Custom Domain, whether using a Google Partner purchase or a separate contract, that may not be the case.

Generally, once you hit the "Purchase This Domain" button, you're stuck with the purchase.

When you purchase a domain, you generally pay just over $10 USD for a one year term. If you decide later that you needed a different name, just buy a second name.

When the one year runs out on the first name, just let it go. Buy 2 less coffees at Starsmucks this year, and move on.

Navigate» Become author for this Blog