Skip to main content

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,
  1. DNS Records
  2. Who Is Issues like 
    • Domain expiration
    • clientHold
There is a case where the DNS could be corrupted. 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?

How do I know my DNS is corrupt?



The diagnosis on a custom domain issue with DWI will tell you there could be an issue in DNS while WhoIs Lookup will confirm. I had to face one such thread whose diagnosis steps are shown below,
The above is the dig log of the custom URL which gave me very weird results. I went ahead and checked for expiration/non registered URL/clientHold at Who Is Lookup,


Registry Domain ID: 1619884945_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.enom.com
Registrar URL: www.enom.com
Updated Date: 2016-10-12T03:07:49.00Z
Creation Date: 2010-10-11T18:39:00.00Z
Registrar Registration Expiration Date: 2016-10-11T17:39:26.00Z
Registrar: ENOM, INC.
Registrar IANA ID: 48
Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited

The domain is really registered and that is the very reason we get these details.

This confirmed there is no issues with DWI or WhoIs. Now comes the third tool IntoDNS - http://intodns.com

What is IntoDNS? 

IntoDNS is again an online tool that helps us check if the DNS is healthy.


How to use Into DNS?

1. Go to http://www.intodns.com
2. Provide your naked domain URL and Report as shown below,
3. As you scroll down, you might see an error with red highlights as shown below,

This will finally tell you your DNS is corrupt.

Where do I report about my corrupt DNS?

The DNS is corrupt and the DNS is offered to you by your registrar. Therefore as you have enough fact that there's an issue at the registrar's end, you may please go ahead and contact the registrar sharing screen shots and links to IntoDNS.

To know how to find who is your registrar, do a Who Is Lookup.

Comments

Feeds for you

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.

Blogger in Draft says "Try the new Blogger!"

It's been long time that I wrote something here. Interestingly there seems to be a new update in Blogger in Draft (https://draft.blogger.com).

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…