Skip to main content

Posts

Showing posts from January, 2017

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. 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 servers from w…

DWI - Not all the time "Authoritative" helps

We already saw the common issues when custom domain is involved where we saw a tool called DWI - Dig Web Interface which will help us get DNS records of a particular domain.

Today while coming across a forum thread, got to notice a strange thing ever. It's not the first time however. If you refer the article about corrupted DNS, the blog URL used had similar issue.

It is normally recommended to use "Authoritative" under Name servers when digging a domain. However this doesn't always workout.

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.

DNS is corrupted. How do I know and What to do?

As far as custom domain troubleshooting is concerned, it's not always there'll be issues with,
DNS RecordsWho Is Issues like Domain expirationclientHold There is a case where the DNS could be corrupted. In that matter we need to know two important things.
How do I know my DNS is corrupt?Where do I report about my corrupt  DNS?
How do I know my DNS is corrupt?

Who Is Lookup

Again as a part of Custom Domain Troubleshooting, we do Who Is lookup which gives us a handful of information.


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,
Registrar InformationRegistered date and expiry information and so on.

How to do Who Is Lookup?

How to use DWI?

In  BHF, when it comes to custom domain, I or Chuck or any other expert mentioning a dig log URL mentioned most of the times as DWI.

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

How to use DWI?