Home » Blogger Tutorials, Tricks and Hacks » Blogger Domain Names » Diagnose Your DNS Address For Inconsistencies With Dig Web Interface

Welcome to our AllBlogTools.com v.3 new version, We are still in beta, please contact us to report an error.

|| View All Tutorials ||

Diagnose Your DNS Address For Inconsistencies With Dig Web Interface

Diagnose Your DNS Address For Inconsistencies With Dig Web Interface

1 Star2 Stars3 Stars4 Stars5 Stars

Report Error

653 views

One of the problems that you might encounter when using a custom domain is inconsistent DNS server configuration, and if are already familiar with troubleshooting it then you know how complicated and troublesome it can be to conduct a diagnosis and detect inconsistencies.

Fortunately though, there’s a tool you can use that will save you from all this trouble. It’s called Dig Web Interface, which provides you with the ability to diagnose inconsistent DNS servers much more easily via GUI transaction, and it only takes less than a minute.

To use it, just do the following steps:

  • Provide the “naked domain” and “www” aliases.
  • Select “A” for “Type” (“A” / “CNAME” / “NS” lookups).
  • Select “Authoritative” for “Nameservers”.
  • Hit “Dig”.

And that’s it! Pretty much half of the work is already done for you. All that’s left for you to do is examine the report it provides, which is not that hard to parse. Each authority server for each URL is identified and Dug. You’ll quickly find any DNS inconsistency in the log as it will show the difference in DNS addresses. Pretty neat, huh? Hope you enjoy using this helpful tool!

Liked It ? Please Share

Comments

2 Responses | Post A Comment | Subscribe To Comments RSS Feed

  1. Good day! This is kind of off topic but I need some advice from an
    established blog. Is it very hard to set up
    your own blog? I’m not very techincal but I can figure things out pretty fast. I’m thinking about making my own but I’m not sure where to start. Do you have any points or suggestions? Thank you

Comments will be closed off on this post 365 days (1 year) after it is published. Apologies to this, but it's all about avoiding a growing comment spam problem. See our most recent posts where you can comment here