Skip to main content

Common issues where custom domain is involved.

In BHF, one of the common issues we face is setting up custom domain. We already have a lot of information on how to setup a custom domain. So I am going to go ahead and write on the troubleshooting tips for custom domain.

This article is dedicated to Chuck Croll who has been/is a great mentor to me since the beginning.

So let's start with the first and foremost golden rule of Custom domain troubleshooting.
Any issue where you have custom domains involved, first check if the custom domain is setup properly.
Some common issues where custom domain  are involved and you'll not know DNS was causing the trouble are,
  1. You'll be able to see the custom domain while some of your friends/users will not be able to. In this case, you shall use DWI to see if the DNS addresses are righteous.
  2. Cannot get thumbnail on Facebook. What can I do?
    • So what? Use Facebook OG Object Debugger is what most people think.
    • There comes the case, Inspite of using Facebook OG Object Debugger, I am not able to get thumbnail. So What now? Simple. Use DWI. It could be incorrect DNS Setup.
  3.  And the list goes on.
What on earth is DWI?
DWI is expanded as DigWebInterface which is an online DNS Lookup tool which can be found at http://www.digwebinterface.com

The detailed article on how to use DWI and what is the required custom domain setup for blogger is written here -> http://howtoblog.krishnainfotron.com/2017/01/how-to-use-dwi.html

I could not find anything in the DWI. What now?

The moment you realise DWI gives you back SOA records or you cannot see any CName/A records, the next thing to do is a Who Is lookup.

What is Who Is Lookup?
Who Is lookup gives exactly what the name means. "Who Is". In addition to Who Is, this will give few useful information like,
  1. Registrar Information
  2. Registered date and expiry information
and so on.
A detailed writeup of Who Is lookup and troubleshooting can be read through here -> http://howtoblog.krishnainfotron.com/2017/01/who-is-lookup.html

I did not get a proper DNS response and no issues with Who Is. What do I do now?
In this case the next thing could be a Corrupt DNS. If the DNS is corrupted, none of the above troubleshooting could help.

In that matter we need to know two important things.
  1. How do I know my DNS is corrupt?
  2. Where do I report about my corrupt  DNS?
A detailed writeup on troubleshooting corrupt DNS could be found here -> http://howtoblog.krishnainfotron.com/2017/01/dns-is-corrupted-how-do-i-know-and-what.html

I cannot find a DNS Zone to edit. What can I do? 
When you cannot find a DNS zone to edit, there could be two reasons,
  1. You do not know where it is.
  2. There really isn't one.
When it is Case 1, you have to figure out where your DNS Zone editor is available or the best thing is to contact your registrar.

When it is Case 2, it could be that you're using Google domains to which the integration is different. Please read the support article of Google domains -> Integrate Google domains with Blogger.

Comments

Post a comment

People also read,

How to secure your Google account and Blogger blog?

As a part of contributions to NCSAM, I am writing this article down on what all should we be aware of with respect to Google's security aspect and how to make sure your blog stays yours forever.
What is NCSAM? It's National Cyber Security Awareness Month which is observed during the month of October every year in America.

However, we all know cyber security is a world topic and is not limited to just the USA. So let me give some tips with respect to keeping the Google account safe and Blogger blogs safe from hackers. As I secure my account, I hope you people catch up too.

In this blog post, I am going to tell about the following,
Securing your Google account.Securing your Blogger blog. Securing your Google account Since Blogger is also part of your Google account, let's first see what all we need to do to keep our Google account safe. Don't share your password to anyone.Keep changing your password every 60 - 90 days.Make sure your password is strong enough. Have at leas…

Blogger HTTPS for custom domain and Cloudflare

In BHF, there was a recent issue related to cloudflare where the browser screams the site is a phishing site. So I thought of writing up how does a service like cloudflare affect your blogger blog.

What is Cloudflare?
Well we have that written all over Wikipedia: Cloudflare. Let's go on with why Blogger users look for Cloudflare.
Anciently Blogger users used Cloudflare for one simple reason. HTTPS for custom domains.
So what happens when you introduce Cloudflare into your domain?
DNS Redirect. Your custom domain will be configured with the proxy info provided by Cloudflare and when the request is hit, DNS redirect happens.
DNS redirect is bad for the site's health. A number of reasons, but the most important is that some browsers, when it detects a DNS redirection, it thinks that it is a phishing site.

What is a DNS redirect?
I am trying to explain this in easy terms. I'll try not to be too technical. When a custom domain URL is hit, usually the domain requests go to Name ser…

Blogger & Twitter card previews

So, there was a report in Blogger Help Community which is what made me write this down. This is in correlation with Blogger & Facebook OG Object debugger. The report was that Blogger blogs doesn't show preview in Twitter card validator.So, I went ahead and tried previewing one of my blog posts and I got the following,

Therefore, I tweeted the same link which is here and it didn't show any preview.  Hence, I concluded not just the validator, the whole twitter stopped scraping my open graph information. Therefore, I made a small research and added a tag in my template.Please follow instructions below,Go to https://blogger.com > ThemesClick on the three dot menu near "My Themes" and choose Edit HTMLIn the appearing page, press Ctrl + F and find the below code,
<b:include data='blog' name='all-head-content'/>
Right after that code, paste the following code,
<meta name="twitter:card" content="summary" />
So, it should look…