Skip to main content

Your Custom Domain, And Your Google Apps Account

Spam - unwanted advertising - is everywhere, and we can't get away from it.

Whether we read an advertising funded paper based tabloid (some time ago, called a "newspaper"), watch an advertising funded electronically broadcast audio / video entertainment service (some time ago, called "television"), or even pay bills using an advertising funded public bill delivery service (some time ago, called "postal mail" delivery), we are rudely subjected to endless onslaughts of unwanted and annoying advertisements.

When you bought a non Blog*Spot address for your blog, using the "Buy a domain" wizard, or possibly using Google Apps, you may have gotten an unexpected email message from Google.
  • In some cases, you may have glanced at this message, and filed it under "Bulk" / "Spam".
  • In other cases, your email delivery program may have already filed it under "Bulk" / "Spam", automatically.
  • Possibly, you simply left it in "Inbox", with thousands of other messages.
In either case, you were doing yourself a disservice. That message, unexpected and maybe looking like advertising, was not spam.

If you care anything about the future, and usability, of your custom domain, you'll now want to go dig out that mysterious message, and read it with care.

Whether you want to ensure that the domain can be renewed properly next year, setup email services for your new domain, or publish more blogs to your domain, reset the domain DNS addresses (using the Blogger / GoDaddy DNS Setup wizard), or even transfer the domain to another registrar, that email from Google Apps is the most important email message that you got, the day that you purchased your domain.

Both your ability to control your domain in Google, and to access the registrar's Domain Manager wizard, is based upon access to your Google Apps desktop. And your access to Google Apps starts with the email message, and clicking on the link to setup the Google Apps account.

It's possible that you can simply reset the Apps account password, using the new integrated Google login screen - or alternatively using the new Google administrative login screen - and not have to worry about these details. Alternately, maybe Google Help: Domain Registration through Blogger will help you.

All of this, unfortunately, requires that your Blogger account that owns the blog involved in the domain purchase, uses an active and valid email address. This is one more reason why uncontrolled anonymity is not a good idea.

Go now, and look in your Inbox, and your "Bulk" / "Spam" folder, for any email from "google-apps-do-not-reply", for the day that you bought your domain. If you don't remember the exact date, find the statement from your bank, with the $10 USD charge, and verify the date. Then find the email, open it, and setup your Google Apps account. Alternately, look in your Google Wallet Log, and find the entry for the domain purchase.

Now that Google Apps does not provide free accounts, you should be able to use the limited access Google Apps account, that came with the domain purchase, if you purchased the domain after November 2012. This would be best done using two browsers.

Enter the complete Google Apps account name, in the Google account reset screen. Some people, right now, won't be able to use the Google account reset, successfully. This is a known problem.

>> Top

Comments

Great info! I wish I found this earlier during my many google searches to find out how to set up my email account.
erinpassons said…
What if you deleted that email?
Nitecruzr said…
Erin,

Generally, you can use Google Wallet to find the original purchase - and there should be a link in there.

The folks in the Google Apps Support forum may be able to help you, otherwise.
I am glad I found this article but still have had NO luck whatsoever in getting the EPP code because I desperately want to transfer the domains I purchased from GOOGLE APPS for my blogs! It's a huge run around. I have clicked every link in EVERY email they ever sent and get "INVALID REQUEST" to every single attempt. DO you have any suggestions. I have emailed, called and sent support tickets to every company -- GOOGLE APPS, ENOM, INC (the losing registrar that google resold the domain for) .... and ICANN. Nightmare while awake!
Nitecruzr said…
Hey Comm,

If you see "Invalid Request" or "Server Error" when trying to login to Google Apps, you don't setup a new administrator account. You use the user name "bloggeradmin" (already setup, on your behalf), and reset the password.

http://blogging.nitecruzr.net/2012/12/after-using-buy-domain-blog-owners.html
Laura said…
Resetting the password does not work because it says that email address "bloggeradmin@mydomainname" has been permanently deleted. I tried using the link in the original email Google sent me when I registered my domain, but I entered the same cycle. And yes, I did this after opening a new browser, clearing everything, etc.
Unknown said…
When I log in (under either of my two google accts) I get a message that says to log into a different account. I only have 2 and it does this for both.

Popular posts from this blog

What's The URL Of My Blog?

We see the plea for help, periodically I need the URL of my blog, so I can give it to my friends. Help! Who's buried in Grant's Tomb, after all? No Chuck, be polite. OK, OK. The title of this blog is "The Real Blogger Status", and the title of this post is "What's The URL Of My Blog?".

Add A Custom Redirect, If You Change A Post URL

When you rename a blog, the most that you can do, to keep the old URL useful, is to setup a stub post , with a clickable link to the new URL. Yo! The blog is now at xxxxxxx.blogspot.com!! Blogger forbids gateway blogs, and similar blog to blog redirections . When you rename a post, you can setup a custom redirect - and automatically redirect your readers to the post, under its new URL. You should take advantage of this option, if you change a post URL.

Adding A Link To Your Blog Post

Occasionally, you see a very odd, cryptic complaint I just added a link in my blog, but the link vanished! No, it wasn't your imagination.