Showing posts with label Google Apps. Show all posts
Showing posts with label Google Apps. Show all posts

Friday, January 2, 2015

Using A Custom Domain Outside Blogger

From time to time, we see questions about using a Blogger / Google custom domain, with publishing services outside Blogger / Google.

Some Blogger blog owners want to combine their Blogger blogs, with non Blogger blogs and websites - and others want simply to move their blogging activity to non Blogger services. And a few think ahead, and wonder how adding or moving to another service will affect the ability of their existing readers to find their blog, and / or their ability to get new readers.

As with using a Blogger blog with an existing non Google domain, this is not a simple project - and to do this properly will require research - and well informed decisions. Some assistance can be provided by Blogger or in Blogger Help Forum: Learn More About Blogger - and other portions of the project will require advice or instruction from the support groups for the new service.

Start by deciding how the domain is to be used, with the new website.

Consider The Options

There are several ways to add / substitute a non Blogger blog / website, in a domain purchased for use with a Blogger blog.

  1. Transfer domain registration, to the registrar, as required by the new hosting service.
  2. Update DNS for the domain, to use name servers, as required by the new hosting service.
  3. Update DNS for the domain, to use only addresses pointing to the new hosting service.
  4. Update DNS for the domain, to use additional addresses pointing to the new hosting service.

Which of these options, that you are able to use, will depend upon requirements of the new hosting service.

WordPress provides detailed instructions, in WordPress Support: Coming from Blogger?. Not all hosting services will be so helpful, however.

Retain / Transfer Existing Traffic

Options #1 - #3 will require you to start a new URL, published by the new hosting service. Blogger will not permit blogs to be used as gateways. You'll have to get your new blog / website indexed, from the bottom up - with no automatic traffic from your Blogger blog.

Any followers or readers, that are associated with your Blogger blog, will have to be redirected to your new blog / website using visual instructions - or at best a clickable link, in a stub blog. You may be able to redirect subscribers - if the new host offers a compatible newsfeed.

You probably won't be able to publish your stub Blogger blog to the domain, though - so chances are, any of these options will leave you starting over - with no instructions to your existing followers and readers, excepting what you provide before moving the domain.

Option #4 will require you to add an additional host, in the domain with your existing Blogger blog. If your new hosting service supports, you may be able to make your Blogger blog and new blog / website equal members of a domain based cluster.

For a domain cluster to be really effective, you will need to maintain both the existing Blogger blog, and the new non Blogger website as separate entities - and have unique content, regularly updated for each.

Access The Current Registrar Dashboard

Whether you transfer domain hosting, or update the domain, you will need access to the current registrar's dashboard.

  • For domains purchased using Blogger / Google "Buy a domain ..." or similar services, access to the registrar's dashboard will require access to the Google Apps / Control Panel utility.
  • For domains purchased directly from the registrar, access to the registrar's dashboard will require an account / password that (hopefully) was setup when the domain was purchased.

You will need access to the registrar's dashboard to obtain the EPP code, required by Option #1 - or to make changes to the domain, required by Options #2 - #4.

You May Need Google Apps Access

Most projects - but not all - which involve custom domains require Google Apps access - and establishing Google Apps access is the most common concern, when access to the registrar's dashboard is needed.

  1. Get access to Google Apps.
  2. That will give you access to the registrar's dashboard.
  3. Retrieve the EPP code, or update the DNS addresses per instructions of the additional / new blogging host service - depending upon which Option you are taking.

In some cases, and if you are considering multiple non Google services, choice of what new service you go with may start with identifying migration / setup options provided by each different service.

Regain Followers, Readers, Subcribers, Search Engine Reputation - And Traffic

A domain moved to use outside Blogger will be similar to a new blog / website - with some characteristics of a renamed Blogger blog, and / or a newly published custom domain blog. Just as all Blogger blogs are unique, so will be any domain migration.

You may consider moving existing blog content, to the new service. This will require planning, and testing.

Both the actual movement of the content - and preventing Blogger spam classification, if you move the content - will be important.

You need to understand all of these issues, to regain traffic sources. Blog / website traffic is a complex subject.

Respect Your Existing Audience

If the question of existing / new followers, subscribers, and readers, and search engine reputation, resulting from the move, is a serious issue with you, you may want to plan your move from Blogger with great care.

You won't be able to blatantly redirect your existing readers to your new website - you will need a carefully planned dual website publishing strategy.

Start With The Support Group For The Chosen Service

If you are going to host a blog or website outside Blogger / Google, you must start with instructions from the support group for the new blog / website. DNS is a key issue, in any domain migration - whether BlogSpot to non BlogSpot, or non BlogSpot to non Google.

---

Occasionally, a #Blogger blog owner decides to move their blog to a non Google website. Starting with advice in Blogger Help Forum, the owner learns that many necessary decisions, related to a hosting change, require support from the new website host.

Not every blog owner realises why setting up and publishing a Blogger blog is so simple, until they have to make decisions about hosting outside Google.

Friday, August 8, 2014

"You do not have access to this service", Being Seen

Recently, we've been seeing a number of reports in Blogger Help Forum: Something Is Broken, from people suddenly unable to login to Blogger and maintain or publish their blogs.

It appears that more and more private network owners are converting their email and office applications suites, to use Google Apps / Docs. This gives the various employers and schools the ability to block people, using their email, from also using extraneous / unnecessary services like Blogger and YouTube - and encourages the employees and students to spend their time more productively.

People with Blogger accounts, that are based on the converted email domains, are seeing problems accessing their blogs.

Part of the Google Apps / Docs package includes the ability to disable the use of various Google products and services, to people using accounts in the domains.

Blog owners are locked out of Blogger, with new managed domains.

People with Blogger accounts that are based on the newly converted domains are finding themselves locked out of Blogger.
When I login, I get the message.
Blogger has not been enabled by the administrator of the domain employerdomain.com.
What do I do, now?

Not all domain administrators, even for those domains which use GMail / Google services for non "gmail.com" email addresses, believe Blogger blogs to be an essential service. Some domain administrators will forbid you to access non domain email services, from their domains.

Not all domain administrators know how to manage the domains properly.

Administrators of small domains, having just converted to Google Apps, may not be aware of the Services settings in their domains, and may need coaching - even if sympathetic to your needs. Any willing domain administrator can refer to Google Apps Help: Add Google Apps services to your account, for instructions on adding the Blogger service to the domain, that you need to use.

The bottom line is that, if your Blogger account is based on an email domain that has been recently converted to Google Apps, you may have some work ahead of you - if you want to use your Blogger account.

Blog Owners Seeing "You do not have access to this service", When Logging In To Blogger

Recently, we've been seeing a number of reports in Blogger Help Forum: Something Is Broken, from people suddenly unable to login to Blogger and maintain or publish their blogs.

It appears that more and more private network owners are converting their email and office applications suites, to use Google Apps / Docs. This gives the various employers and schools the ability to block people, using their email, from also using extraneous / unnecessary services like Blogger and YouTube - and encourages the employees and students to spend their time more productively.

People with Blogger accounts, that are based on the converted email domains, are seeing problems accessing their blogs.

Part of the Google Apps / Docs package includes the ability to disable the use of various Google products and services, to people using accounts in the domains.

People with Blogger accounts that are based on the newly converted domains are finding themselves locked out of Blogger.
When I login, I get the message.
Blogger has not been enabled by the administrator of the domain employerdomain.com.
What do I do, now?

Not all domain administrators, even for those domains which use GMail / Google services for non "gmail.com" email addresses, believe Blogger blogs to be an essential service. Some domain administrators will forbid you to access non domain email services, from their domains.

Administrators of small domains, having just converted to Google Apps, may not be aware of the Services settings in their domains, and may need coaching - even if sympathetic to your needs.

The bottom line is that, if your Blogger account is based on an email domain that has been recently converted to Google Apps, you may have some work ahead of you - if you want to use your Blogger account.

Saturday, May 17, 2014

The Google Apps "Advanced DNS settings" Wizard Does Not Provide A Link To The Registrar

We're seeing reports from some blog owners, who purchased custom domains through Blogger / Google, who are unable to access the registrars zone editor through Google Apps.

Owners of blogs published to custom domains, where the domains were purchased through "Buy a domain", need to use the registrars zone editor to maintain their domains. In the past, the zone editor could be accessed from a link in the "Advanced DNS settings" wizard in the "Admin console" / Google Apps dashboard.

The "Advanced DNS settings" wizard provides important tokens, to let the owner of a domain, purchased through Blogger / Google, interact with the registrar. Besides the tokens, there is a link, captioned "Sign in to DNS console", which should lead directly to the sign in screen provided by either eNom or GoDaddy.

Right now, the "Sign in to DNS console" link leads back to the "Admin console" dashboard. This does not help the domain owner.

Having discussed this issue with a Google Apps Top Contributor, it appears that the only way to login, right now, is using the correct registrar login screen. The link must be properly selected, according to the registrar who hosts the domain. These two links, properly selected, should permit owners of domains, purchased using "Buy a domain", to access the zone editor of the respective registrar.

The domain owner will still have to access the "Advanced DNS settings" wizard, to retrieve the "Sign-in name" and "Password" tokens, which are unique to each domain. The tokens, once retrieved, will be used on the appropriate eNom / GoDaddy login screen, as linked above.

>> Top

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

Sunday, May 2, 2010

Custom Domains Redirecting To Google Sites

Similar to a redirection to the Google Apps Start Page service, some custom domains will be found to be directed to Google Sites. Again, we'll see an apparently normal (asymmetrical) DNS address configuration.
mydomain.net.            3600    IN      A       216.239.32.21
mydomain.net. 3600 IN A 216.239.34.21
mydomain.net. 3600 IN A 216.239.36.21
mydomain.net. 3600 IN A 216.239.38.21
www.mydomain.net. 3600 IN CNAME ghs.google.com.
---
ghs.google.com. 282206 IN CNAME ghs.l.google.com.
ghs.l.google.com. 300 IN A 74.125.43.121
The diagnosis, again, will be made using an (abbreviated) HTTP trace.


Sending request:

GET / HTTP/1.1
Host: mydomain.net
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:
1.9.0.5) Gecko/2008120122 Firefox/3.0.5
Connection: close

• Finding host IP address...
• Host IP address = 209.85.171.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://www.mydomain.net(CR)(LF)

Sending request:

GET / HTTP/1.1
Host: www.mydomain.net
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:
1.9.0.5) Gecko/2008120122 Firefox/3.0.5
Connection: close

• Finding host IP address...
• Host IP address = 209.85.171.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://sites.google.com/a/mydomain.com/sites/system/app/pages/meta/domainWelcome(CR)(LF)

Unlike the generically known "Server Not Found Error 404" symptom, this one won't be solved by merely publishing back to Blog*Spot, then re publishing to the custom domain.

What we see here is that Sites, similar to Start Page, is apparently enabled, and published to "www.mydomain.net". In this case, you're going to first have to disable Sites. If you don't, you're going to see another old friend
Another blog is already hosted at this address.
After doing that, then you can publish back to Blog*Spot, then re publish to the custom domain.

A second variation on this redirect may not start with an explicit "Server Not Found Error 404", and the HTTP trace will be slightly different. You will probably see "Another blog is already hosted at this address." in the usual places.
Sending request:

GET / HTTP/1.1
Host: mydomain.net
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:
1.9.0.6) Gecko/2009011913 Firefox/3.0.6
Connection: close

• Finding host IP address...
• Host IP address = 216.239.34.21
• 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://www.mydomain.net(CR)(LF)

Sending request:

GET / HTTP/1.1
Host: www.mydomain.net
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:
1.9.0.6) Gecko/2009011913 Firefox/3.0.6
Connection: close

• Finding host IP address...
• Host IP address = 209.85.171.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)
(Here is a short excerpt of the rest of the trace -
you have to look carefully for these clues)

<body·xmlns="http://www.google.com/ns/jotspot"·id="body"·class="·en">(LF)
<div·id="sites-page-toolbar">(LF)
<div·id="sites-status"·class="sites-status"·style="display:none;">(LF)
<div·id="sites-notice"·class="sites-notice">·</div>(LF)
</div>(LF)
</div>(LF)
<div·id="sites-chrome-everything"·style="direction:·ltr">(LF)
<div·id="sites-chrome-page-wrapper">(LF)
<div·id="sites-chrome-page-wrapper-inside">(LF)
<div·xmlns="http://www.w3.org/1999/xhtml"·id="sites-chrome-header-wrapper">(LF)

As shown immediately above, we have Google Sites involved, though less obviously. Resolution of this scenario, too, seems to involve disabling Sites. After doing that, you will likewise need to publish back to Blog*Spot, then re publish to the custom domain.

>> Top

Friday, November 27, 2009

Deactivation Of The Google Sites Or Start Page Service

Unsolicited redirect to a Google AdServices, Sites, or Start page is a very common cause, right now, for the well known custom domain symptom "Another blog is already hosted at this address". And, it's a reasonably easy symptom to correct.

Start by logging in to Google Apps.Then, deactivate the AdServices, Sites or Start Page service.
  • When you login, you will be at the Google Apps Dashboard. If you're logged in using an account with administrative authority, you'll have the links that you need, there in front of you.
  • You disable and enable a service, and set the publishing address, from the service settings screen.
  • If simply disabling the service in question is not productive, you'll need to recycle the service settings. This will involve slightly more work.

If your Apps dashboard does not include a shortcut for the service that's a problem for you, you may be able to add that service to the dashboard, then deactivate it. If the service in question isn't on your dashboard, and you can't add it to your dashboard, then you'll have to do the full domain settings recycle, to methodically reset the "Another blog is already hosted at this address" symptom.

The Google Apps Services

You install and activate any needed service, using the "Organization & Users" - "Services" wizard.

The Service Settings Screen

You disable a service, and set the publishing address, from the service settings screen. You access the service settings screen using the "Settings" menu entry on the far right - or the "View all settings" dashboard link.

The CustomURL Screen

Besides the multiple mappings which may be active for Sites, you can display all installed services, and their mappings, using the CustomURL screen.


Note:

>> Top

Wednesday, August 20, 2008

Custom Domains And Email Delivery

Most bloggers who setup a Google Custom Domain do it purely to serve a web site. That's what Blogger blogs are, anyway - easily setup journal style web sites. As your web site grows in reputation, you may think about the advantages of having email with the domain name. Most corporations, that have their own email and web servers, do that - so why shouldn't you?

If you purchased a domain for your Blogger blog (either explicitly setup using "Advanced Settings", or setup for you by "Buy A Domain"), you can have your own email addresses - up to 200 of them - as part of your Google Apps custom domain account.

If you already own a domain, and have DNS control, you can setup Google Apps for an existing domain. This is a very useful solution, if you're publishing a Blogger blog to a custom domain, in an existing corporate domain.

With a properly setup Google Apps style custom domain, just login to Google Apps. From the Google Apps Dashboard, select "Settings". In the "Services" menu on the left, select "Email", and you'll see the "Email settings" wizard.


Click the link for "Email".


  • The default URL for reading my Google Apps email is "mail.nitecruzr.net". Yours will be similar, or you can change the URL if you wish.
  • Setup a default email handling process, either to discard improperly addressed email, or forward it to a specific mailbox in the domain.
  • Then, click the link for "Instructions on how to activate email".




Activating email isn't complicated.
  1. Create user accounts. Who do you want to get email?
  2. Setup email delivery at your DNS Host. You'll use the Domain Manager wizard of your DNS Host, just as you did when you setup the custom domain itself. Select your DNS host from the pull down list in the next screen, for detailed instructions. If you used "Buy A Domain", these settings may already be in place.




It's just like having your own email server, without so much of the work.

Having setup your personal domain email, you can use the Google Apps desktop to read the email. Or, you can forward the email to your GMail account, if you like the GMail desktop better.

>> Top

Wednesday, June 18, 2008

Custom Domain Publishing, And Google Apps

I've been writing about setting up a Google Custom Domain for a while, and I've described the process of setting them up, and various configurations that are produced from the setup. Most of the setup processes have focused on new domains, where the blog owner simply wants to publish the blog to a non-Blog*Spot URL, and no complications exist.

But what if you want to use different services in your domain, which you may or may not be already using? Maybe you have email, an FTP server, and / or a third party (non-Google) web site, hosted on a third party server.

Or, maybe your DNS host won't let you redirect the primary domain using a "CNAME" referral.

That's what you use Google Apps for - integrating existing and new domain components.

Let's look at this domain, "nitecruzr.net", which I setup using the "Buy A Domain" wizard. You can do the same, or use Google Apps, which will give the same results for you without a lot of work. Or, if you already have your domain, and it has existing services, you can setup the domain in Google Apps manually.

First, you setup the DNS for the domain, using the domain manager wizard provided by your DNS host. You may find Custom Domains - The Details In The DNS Settings, to help you understand the information provided in the Dig logs, presented below. You may also wish to read about proper DNS configurations, and alternately about improper DNS configurations.

Let's examine a brief Dig log for the primary domain "nitecruzr.net".
;; QUESTION SECTION:
;nitecruzr.net. IN A

;; ANSWER SECTION:
nitecruzr.net. 3600 IN A 64.233.179.121 <<== Do not include this server - See Below.
nitecruzr.net. 3600 IN A 66.249.81.121 <<== Do not include this server - See Below.
nitecruzr.net. 3600 IN A 72.14.207.121


There are the 3 Google Apps servers - and currently, only 1 of them is active. If we directed the primary domain to "ghs.google.com", you'd lose any email, FTP, and other special services, because "ghs.google.com" doesn't provide special services. Instead, we use Google Apps.

Next, a brief Dig log for the "www" alias "www.nitecruzr.net".
;; QUESTION SECTION:
;www.nitecruzr.net. IN A

;; ANSWER SECTION:
www.nitecruzr.net. 3600 IN CNAME ghs.google.com.
ghs.google.com. 586847 IN CNAME ghs.l.google.com.
ghs.l.google.com. 203 IN A 72.14.207.121


There we have "ghs.google.com". You will probably publish the blog to the "www" alias, and redirect the primary domain to the "www" alias, using Google Apps. See Google Custom Domains - The Two Step Domain Referral for detailed explanation.

Effectively, and showing what I call an excerpted Dig log, you should have
nitecruzr.net.  3600 IN A 64.233.179.121
nitecruzr.net. 3600 IN A 72.14.207.121
www.nitecruzr.net. 3600 IN CNAME ghs.google.com.


And, remember to setup an updated sitemap, when it is all working.

If you get the well known "Another blog is already hosted at this address." error, and your DNS is absolutely setup per the above advice, recycle the domain settings in Google Apps. If you get another well known error, "404 Server Not Found", publish the blog back to its BlogSpot URL, then re publish to the "www" alias.

Having done the above, you'll have one blog published to your domain. If you have a multiple blog domain, this will be your "home blog", similar in function to my blog "www.nitecruzr.net". If you want more blogs published to your domain, you setup a virtual hosts cluster, ala my blogs "blogging.nitecruzr.net" and "recipes.nitecruzr.net".

(Update 10/13/2008): The complement of servers, as described above, has been changed.

>> Top

Thursday, April 17, 2008

The GoDaddy Domain Manager

Making any custom settings to your custom domain, beyond what is done by the "Buy A Domain" wizard, involves the eNom / GoDaddy Domain Manager. If you bought your domain on your own, you might have chosen eNom, GoDaddy, or any of dozens other DNS hosts / registrars. Each domain manager will be different.

Once you're in the domain manager, what do you do? GoDaddy provides a lot of settings for managing your domain. eNom, the alternate Google partner in custom domain registration, has a Domain Manager that's similar only in result. Any other DNS host will have something still more different.

You may get to the Domain Manager directly (using a bookmark). If you bought the domain using "Buy A Domain" or Google Apps, you can alternately use the Google Apps "Advanced DNS settings" wizard. My domain is hosted by GoDaddy, and I bought it using "Buy A Domain".

Having entered your userid and password, successfully, you are presented with the "Domains" menu. Here you will see a list of your domains. Select one, by clicking on the link in the name.

This takes you to the "Domain Manager - Domain Details" screen, for your chosen domain. As of 2010/11/01, you'll see a menu bar, right in the middle of the screen. One of the buttons in the menu bar will be Forwarding. Click here, to setup a "301 Redirect". You may have a submenu, offering a choice to "Forward Domain" or "Forward Subdomain".

At the bottom of the screen, in the middle, will be a section labeled "Total DNS", with a "Launch" link. Click on "Launch", to setup "A" / "CNAME" referrals and other DNS control records.

If you're setting up a new domain, you'll use "Total DNS", and one or more "A" / "CNAME" records. If you're adding aliases to an existing domain, you can use either "Total DNS" or "Forwarding". While "Forwarding" has its place occasionally, 99% of the time you'll be using "Total DNS" for adding aliases.

Here, you may wish to peruse my other tutorials. Also, see (corrected) GoDaddy instructions, for setting up a custom domain.

>> Top

Friday, April 4, 2008

Managing Your Custom Domain

As I stated in The Choice Is Yours, given the choice in the future, I would personally recommend and use the "Buy A Domain" wizard for setting up any new domain. Not all bloggers will agree with me on this, as some have additional needs, and prefer to setup their domains with more detail.

If you already own a domain, and maybe have additional components like mail or other servers defined, you'll use the "Advanced Settings" wizard in Blogger - after using the wizard provided by your DNS host to setup the DNS for your domain. If you bought your domain from GoDaddy, you'll use the GoDaddy DNS Manager; if you bought your domain from another registrar, you'll use their DNS Manager.

Note that some basic functions, like payment / domain registration renewal, may be available in the Apps desktop, for Google Apps accounts setup for domains purchased through Blogger. These functions may not be available for domains purchased directly from a registrar, with the Google Apps account setup after purchase.

If you intend to setup additional components for a new domain, you might choose the same procedure, though you'll have more work to do. And the additional work is not unavoidable, because you can setup any new domain using the "Buy A Domain" wizard, then use the wizard provided by your DNS host (the GoDaddy DNS Manager, or any other) to setup any additional components, at your convenience. You can even do this to setup any blog or web site not hosted by Google.

  • Setup your new domain, using the "Buy A Domain" wizard.
  • Find and open the domain registration confirmation email from Google Apps. Look for email from "google-apps-do-not-reply". If you paid for the domain, but didn't get email from Google Apps, you have to go to Google Apps Help, and Google Apps Frequently Reported Issues, and have the domain reset. Be imaginative, and persistent, in searching for the email message.
  • Find, and click on, the link accompanying
    If you haven't already created an administrator account for your domain, click the following link:
  • Setup an administrator account, for Google Apps, for your domain.
  • Login to Google Apps with your administrator account.
  • You are now in Google Apps, and looking at the Google Apps dashboard. This is where you start, when recycling domain settings in Google Apps.
  • Find, and click on, the "domain names" link at the top of the dashboard, above "Service settings".
  • Find, and click on, "Advanced DNS settings".
    Sign in to godaddy to change your MX records, CNAME and other advanced DNS settings.
  • "Advanced DNS settings" has 4 key identity elements, and a URL.
    1. Sign-in name.
    2. Password.
    3. Customer service PIN.
    4. Customer service email.
    5. The URL to login to the GoDaddy (or eNom) DNS Settings wizard.
  • Once in the GoDaddy (eNom) wizard, it's the same as if you had purchased the domain on your own, except that you are a Google customer, and enjoy the Google GoDaddy (eNom) Custom Service relationship. Now, you can
  • Bookmark the Google Apps signon, for future use.



The "Advanced DNS settings" link is where you start. If that link isn't on your screen, you have a problem, and it's time to look for help from Google Apps.




"Advanced DNS settings" has 4 key identity elements, and a URL, to let you use the resources provided by the registrar.


  1. Sign-in name.
  2. Password.
  3. Customer service PIN.
  4. Customer service email.
  5. A URL to login to the GoDaddy DNS Settings wizard (if the domain is registered by GoDaddy), or the eNom DNS Settings wizard (if the domain is registered by eNom).

So, use "Advanced Settings" if you already have a working domain. If you don't already have a working domain, start with "Buy A Domain" and concentrate on making the domain easy for your readers to use. Don't waste time setting up the domain on your own.

If you can't find the email from Google Apps, or if you just bought the domain directly from a registrar and Google Apps wasn't involved, you're now here trying to setup your domain in Google Apps. If the domain was never setup in Google Apps, use the Google Apps Sign Up wizard.

If you just bought a popular domain, and that domain has been used by someone else previously, maybe it's already registered in Google Apps. When you go to setup your Google Apps account, you get
This domain has already been registered with Google Apps. Please contact your domain administrator for instructions on using Google Apps with this domain.

In the latter case, you have to go to Google Apps Help, and Google Apps Frequently Reported Issues, and have the domain reset. You'll need to use this procedure also, if you don't have email from Google Apps.

And, if you bought your domain using "Buy a domain" or Google Apps, and you have not yet setup your Google Apps account, please consider this as your wakeup call.

>> Top

Navigate» Become author for this Blog