Blogger Magic - Reading A Dig Log

There are hundreds of registrars, serving the Internet community, each with their own dashboard. Blog owners, setting up their domains for their Blogger blogs, must deal with the syntax and terminology used by each different dashboard.

A Dig log lets the blog owner identify the DNS addresses for the domain, using a consistent display.
By identifying the DNS addresses used in a given domain, a blog owner or an experienced forum helper can diagnose many custom domain DNS related problems.

I have a domain (www.rockchickenz.com) - and want to link my blog (rockchickenz.blogspot.com).

Start by verifying URLs involved.

Continue with Dig Web Interface.

A full screen print of the Dig log.

The relevant portion of the Dig log, from the screen print.

The relevant portion of the Dig log, as text.

The advice provided, to the blog owner.

Alternate / complementary tools used.

Start by verifying URLs involved.

Whenever possible, make a screen print, and a text copy, of the Blogger dashboard Publishing wizard, at Settings - Basic. Knowing the status of the blog and domain - and the exact URLs involved - can go a long way to diagnosing many custom domain publishing problems.

Continue with a Dig Web Interface log.

The best tool for generating a Dig log is Dig Web Interface. Alternate / complementary tools are listed below.

I use DWI, for this purpose, by preference. DWI lets you:

Package the URLs in the Dig target, in the reference URL.

Include multiple target URLs, in one reference URL.

Both capabilities are very useful, in diagnosing Blogger custom domain publishing problems.

Start from the Dig Web Interface page.

Add the domain root and "www" alias, under "Hostnames or IP addresses:".

This is the complete Dig log, resulting from the Dig Log URL (above), and containing the relevant portion (below).

This is the Dig log, for "rockchickenz.com".

The relevant portion of the Dig log, from the screen print.

This is the important portion of the screen print (above), and showing the text (below).

This is the relevant portion of the Dig log, for "rockchickenz.com".

Note the TTL value of "14399" - which is a typical Dig log display for TTL set as "14400" (14400 seconds or 4 hours), in the registrar's zone editor. TTL is a setting which is used to adjust name server performance.

Unless you are experienced with DNS setup (and probably don't need to read this advice), you should use the default TTL provided by the registrar, for your domain. Your registrar wants to provide a stable domain for you - and the TTL value affects domain stability.

The relevant portion of the Dig log, as text.

These are the important details from the screen print (above), with colour highlights corresponding to domain specific details (below).

Remove the addresses highlighted in red - and add the addresses highlighted in green - and keep the addresses highlighted in yellow.

Then, specific advice:

This is what you have:
rockchickenz.com. 14400 IN A 78.137.164.51www.rockchickenz.com. 14400 IN CNAME ghs.google.com.
This is what you need:
rockchickenz.com. 14400 IN A 216.239.32.21
rockchickenz.com. 14400 IN A 216.239.34.21
rockchickenz.com. 14400 IN A 216.239.36.21
rockchickenz.com. 14400 IN A 216.239.38.21www.rockchickenz.com. 14400 IN CNAME ghs.google.com.

One of the most useful tools, for diagnosing #Blogger custom domain problems, is a Dig Log. Learning how to read a Dig Log is a useful skill, for any blog owner wishing to publish a blog to a custom domain.

Comments

Popular posts from this blog

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.

Some blog owners prefer to save money when registering a custom domain, for their blogs. We've seen several free domain registration services, providing what is claimed to be a two level Top Level Domain "co.xx" (where "xx" == various country codes).

The latest in this ongoing story appears to be "net.tf" - and 13 other "top level domains".There is also an additional free service offering third-level .tf domains, under the name United Names Organisation. They occupy 14 second-level domains, including .eu.tf, .us.tf, .net.tf, and .edu.tf. They are run by the same company as smartdots.com, and are given away as URL redirections.