Skip to main content

Set up a third party domain to google blogger domain

When you buy a domain, you can personalize your blog’s website address.

Important:
If you use CAA Records on your custom domain, add a record for lets encrypt.org, or Blogger won't create or renew your SSL certificate. 

Step 1: Buy a domain

See if you can buy a Google Domain or buy a domain from a non-Google provider. To buy a Google domain:
  1.     Sign in to Blogger.
  2.     Select the blog to update.
  3.     On the left, click Settings and then Basic.
  4.     Under "Publishing," next to "Blog Address," click Buy a domain.
  5.     At the top, search for a domain.
  6.     Next to the domain you want, click Buy.
  7.     To finish buying your domain, follow the on-screen steps.

Note: If you’re an administrator, learn more about managing domains registered through Blogger.

Step 2: Set up your domain with your blog
 
Connect to your Google Domain from Blogger
  1.  Sign in to Blogger.
  2.  Select the blog you want to update.
  3.  On the left, click Settings and then Basic.
  4.  Under "Publishing," click +Setup a Google Domains URL for your blog.
  5.  Under "Google Domains Settings," select your subdomain and domain and click Save.

Connect to your non-Google domain from Blogger
  1. Sign in to Blogger.
  2. Select the blog you want to update.
  3. On the left, click Settings and then Basic.
  4. Under "Publishing," click + Setup a 3rd party URL for your blog.
  5. Type the URL of the domain you've purchased.
  6. Click Save.
  7. You'll see an error with two CNAMEs.
  8. Name, Label or Host: Enter the name as the subdomain, like "blog." or "www." For destination, enter "ghs.googlehosted.com."
  9. Destination, Target or Points to: This is different for each person and is specific to your blog and your Google Account.
  10. Go to the website where you bought your domain. Find the DNS (Domain Name System) in the control panel.
  11. Under "Name, Label or Host," type the subdomain you entered in the previous step.
  12. Under "Destination, Target or Points to," type "ghs.googlehosted.com."
  13. Enter details for the second CNAME, which are specific to your blog and Google Account.
  14. Wait for at least an hour for your DNS settings to activate.
  15. Repeat steps 1 through 6. Your blogspot.com address will redirect to your custom domain. It may take to 24 hours.

Step 3 (optional): Add www. to your domain.

To change your domain (example: mydomain.com) to www.mydomain.com, set up a naked redirect.​
  1. Go to your domain provider’s website.
  2. Open your DNS settings.
  3. Enter your domain name in the format example.com.
  4. Add four A-records which point to Google IPs.
  5.         216.239.32.21
  6.         216.239.34.21
  7.         216.239.36.21
  8.         216.239.38.21
  9. Sign in to Blogger.
  10. Select the blog you want to update.
  11. On the left, click Settings and then Basic.
  12. Under "Publishing," under "Blog Address," check Redirect [mydomain.com to www.mydomain.com].

Troubleshoot issues


If you have problems, here are some steps you can try.
  1. You may not have to enter the two CNAMEs when setting up your doStep 3 (optional):main.
  2. Make sure the "Name, Label, or Host" CNAME is correct.
  3. If your custom domain doesn’t work, wait before trying the steps again. If you have problems, contact your domain provider.

Comments

Popular posts from this blog

Special Permissions in linux

The setuid permission on an executable file means that the command will run as the user owning the file, not as the user that ran the command. One example is the passwd command: [student@desktopX ~]$ ls -l /usr/bin/passwd -rw s r-xr-x. 1 root root 35504 Jul 16 2010 /usr/bin/passwd In a long listing, you can spot the setuid permissions by a lowercase s where you would normally expect the x (owner execute permissions) to be. If the owner does not have execute permissions, this will be replaced by an uppercase S . The special permission setgid on a directory means that files created in the directory will inherit their group ownership from the directory, rather than inheriting it from the creating user. This is commonly used on group collaborative directories to automatically change a file from the default private group to the shared group, or if files in a directory should be

The Seven-Step Model of Migration

Irrespective of the migration approach adopted, the Seven-step Model of Cloud Migration creates a more rational point of view towards the migration process and offers the ability to imbibe several best practices throughout the journey Step 1: Assess Cloud migration assessments are conducted to understand the complexities in the migration process at the code, design and architectural levels. The investment and the recurring costs are also evaluated along with gauging the tools, test cases, functionalities and other features related to the configuration. Step 2: Isolate The applications to be migrated to the cloud from the internal data center are freed of dependencies pertaining to the environment and the existing system. This step cuts a clearer picture about the complexity of the migration process. Step 3: Map Most organisations hold a detailed mapping of their environment with all the systems and applications. This information can be used to distinguish between the

RequestsDependencyWarning: urllib3 (1.24.1) or chardet (3.0.4) doesn't match a supported version

import tweepy /usr/lib/python2.7/dist-packages/requests/__init__.py:80: RequestsDependencyWarning: urllib3 (1.24.1) or chardet (3.0.4) doesn't match a supported version!   RequestsDependencyWarning) Traceback (most recent call last):   File "<stdin>", line 1, in <module>   File "/usr/local/lib/python2.7/dist-packages/tweepy/__init__.py", line 14, in <module>     from tweepy.api import API   File "/usr/local/lib/python2.7/dist-packages/tweepy/api.py", line 12, in <module>     from tweepy.binder import bind_api   File "/usr/local/lib/python2.7/dist-packages/tweepy/binder.py", line 11, in <module>     import requests   File "/usr/lib/python2.7/dist-packages/requests/__init__.py", line 97, in <module>     from . import utils   File "/usr/lib/python2.7/dist-packages/requests/utils.py", line 26, in <module>     from ._internal_utils import to_native_string   File "/usr/lib/python2.

tag