How to Blog?

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. Let us consider the following URL in issue. newsblok.com www.newsblok.com The actual authoritative Dig Log gives us the following results, newsblok.com@dns1.name-services.com.: /usr/bin/dig: couldn't get address for 'dns1.name-services.com.': failure newsblok.com@dns2.name-services.com.: /usr/bin/dig: couldn't get address for 'dns2.name-services.com.': failure newsblok.com@dns3.name-services.com.: /usr/bin/dig: couldn't get address...

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, 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. 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,...