Blogger Magic - Reading A Dig Log
Saturday, May 18, 2013
Edit
Whether you're setting upwardly or troubleshooting a custom domain, knowing how to read a Dig log is a useful skill.
There are hundreds of registrars, serving the Internet community, each alongside their ain dashboard. Blog owners, setting upwardly their domains for their Blogger blogs, must bargain alongside the syntax in addition to terminology used past times each dissimilar dashboard.
Influenza A virus subtype H5N1 Dig log lets the weblog possessor position the DNS addresses for the domain, using a consistent display.
By identifying the DNS addresses used inwards a given domain, a weblog possessor or an experienced forum helper tin dismiss diagnose many custom domain DNS related problems.
Here is an illustration of Dig log use, showing an excerpted Dig log, inwards Diagnosing Problems With Custom Domains: Dig.
Start past times verifying URLs involved.
Whenever possible, brand a enshroud print, in addition to a text copy, of the Blogger dashboard Publishing wizard, at Settings - Basic. Knowing the condition of the weblog in addition to domain - in addition to the exact URLs involved - tin dismiss become a long means to diagnosing many custom domain publishing problems.
Continue alongside a Dig Web Interface log.
The best tool for generating a Dig log is Dig Web Interface. Alternate / complementary tools are listed below.
I exercise DWI, for this purpose, past times preference. DWI lets you:
Start from the Dig Web Interface page.
Add the domain rootage in addition to "www" alias, nether "Hostnames or IP addresses:".
I guide Type: "A", in addition to Nameservers: "Authoritative", for my actual diagnoses.
Click "Dig".
The Dig Log reference URL, for "rockchickenz.com", generated from DWI. Target URLs are "rockchickenz.com" in addition to "www.rockchickenz.com".
A total enshroud impress of the Dig log.
This is the consummate Dig log, resulting from the Dig Log URL (above), in addition to containing the relevant component subdivision (below).
This is the Dig log, for "rockchickenz.com".
The relevant component subdivision of the Dig log, from the enshroud print.
This is the of import component subdivision of the enshroud impress (above), in addition to showing the text (below).
This is the relevant component subdivision of the Dig log, for "rockchickenz.com".
Note the TTL value of "14399" - which is a typical Dig log display for TTL laid upwardly equally "14400" (14400 seconds or four hours), inwards the registrar's zone editor. TTL is a setting which is used to adjust cite server performance.
Unless y'all are experienced alongside DNS setup (and in all probability don't involve to read this advice), y'all should exercise the default TTL provided past times the registrar, for your domain. Your registrar wants to supply a stable domain for y'all - in addition to the TTL value affects domain stability.
The relevant component subdivision of the Dig log, equally text.
These are the of import details from the enshroud impress (above), alongside color highlights corresponding to domain specific details (below).
The latter is typically seen, alongside a weblog possessor having received bogus advice - in addition to reporting an inconsistently accessible blog.
The advice provided, to the weblog owner.
The typical advice, Setting Up DNS Addresses For Custom Domains.
First, generic advice:
Remove the addresses highlighted inwards red - in addition to add together the addresses highlighted inwards green - in addition to expire along the addresses highlighted inwards yellow.
Then, specific advice:
The advice references a typical ASymmetrical DNS custom domain setup - the address laid upwardly used inwards 99% of all custom domain setups. Note here, the specified TTL of "14400" (4 hours).
Using the inwards a higher house advice, the weblog possessor tin dismiss then, if necessary, research the syntax used past times the registrar's dashboard (aka "zone editor") - in addition to brand the necessary changes.
Alternate / complementary tools used.
Alternate tools, which tin dismiss travel used to generate a Dig log, are the used to verify results.
Complementary tools include the Rex Swain HTTP Viewer, in addition to the Whois Lookup.
In or thus cases, my 12 link affinity / differential connectivity test may travel useful.
For to a greater extent than information.
See WikiPedia: dig (command).
One of the nigh useful tools, for diagnosing #Blogger custom domain problems, is a Dig Log. Learning how to read a Dig Log is a useful skill, for whatever weblog possessor wishing to issue a weblog to a custom domain.
There are hundreds of registrars, serving the Internet community, each alongside their ain dashboard. Blog owners, setting upwardly their domains for their Blogger blogs, must bargain alongside the syntax in addition to terminology used past times each dissimilar dashboard.
Influenza A virus subtype H5N1 Dig log lets the weblog possessor position the DNS addresses for the domain, using a consistent display.
By identifying the DNS addresses used inwards a given domain, a weblog possessor or an experienced forum helper tin dismiss diagnose many custom domain DNS related problems.
Here is an illustration of Dig log use, showing an excerpted Dig log, inwards Diagnosing Problems With Custom Domains: Dig.
I accept a domain (www.rockchickenz.com) - in addition to desire to link my weblog (rockchickenz.blogspot.com).
- Start past times verifying URLs involved.
- Continue alongside Dig Web Interface.
- A total enshroud impress of the Dig log.
- The relevant component subdivision of the Dig log, from the enshroud print.
- The relevant component subdivision of the Dig log, equally text.
- The advice provided, to the weblog owner.
- Alternate / complementary tools used.
Start past times verifying URLs involved.
Whenever possible, brand a enshroud print, in addition to a text copy, of the Blogger dashboard Publishing wizard, at Settings - Basic. Knowing the condition of the weblog in addition to domain - in addition to the exact URLs involved - tin dismiss become a long means to diagnosing many custom domain publishing problems.
Continue alongside a Dig Web Interface log.
The best tool for generating a Dig log is Dig Web Interface. Alternate / complementary tools are listed below.
I exercise DWI, for this purpose, past times preference. DWI lets you:
- Package the URLs inwards the Dig target, inwards the reference URL.
- Include multiple target URLs, inwards ane reference URL.
- Both capabilities are real useful, inwards diagnosing Blogger custom domain publishing problems.
Start from the Dig Web Interface page.
Add the domain rootage in addition to "www" alias, nether "Hostnames or IP addresses:".
I guide Type: "A", in addition to Nameservers: "Authoritative", for my actual diagnoses.
Click "Dig".
The Dig Log reference URL, for "rockchickenz.com", generated from DWI. Target URLs are "rockchickenz.com" in addition to "www.rockchickenz.com".
http://www.digwebinterface.com/?hostnames=rockchickenz.com%0D%0Awww.rockchickenz.com&type=A&ns=resolver&useresolver=8.8.4.4&nameservers=
A total enshroud impress of the Dig log.
This is the consummate Dig log, resulting from the Dig Log URL (above), in addition to containing the relevant component subdivision (below).
This is the Dig log, for "rockchickenz.com".
The relevant component subdivision of the Dig log, from the enshroud print.
This is the of import component subdivision of the enshroud impress (above), in addition to showing the text (below).
This is the relevant component subdivision of the Dig log, for "rockchickenz.com".
Note the TTL value of "14399" - which is a typical Dig log display for TTL laid upwardly equally "14400" (14400 seconds or four hours), inwards the registrar's zone editor. TTL is a setting which is used to adjust cite server performance.
Unless y'all are experienced alongside DNS setup (and in all probability don't involve to read this advice), y'all should exercise the default TTL provided past times the registrar, for your domain. Your registrar wants to supply a stable domain for y'all - in addition to the TTL value affects domain stability.
The relevant component subdivision of the Dig log, equally text.
These are the of import details from the enshroud impress (above), alongside color highlights corresponding to domain specific details (below).
rockchickenz.com@8.8.4.4 (Default): rockchickenz.com. 14399 IN Influenza A virus subtype H5N1 78.137.164.51 www.rockchickenz.com@8.8.4.4 (Default): www.rockchickenz.com. 14399 IN CNAME ghs.google.com. ghs.google.com. 21392 IN CNAME ghs.l.google.com. ghs.l.google.com. 92 IN Influenza A virus subtype H5N1 64.233.183.121
The latter is typically seen, alongside a weblog possessor having received bogus advice - in addition to reporting an inconsistently accessible blog.
The advice provided, to the weblog owner.
The typical advice, Setting Up DNS Addresses For Custom Domains.
First, generic advice:
Remove the addresses highlighted inwards red - in addition to add together the addresses highlighted inwards green - in addition to expire along the addresses highlighted inwards yellow.
Then, specific advice:
This is what y'all have: rockchickenz.com. 14400 IN Influenza A virus subtype H5N1 78.137.164.51 www.rockchickenz.com. 14400 IN CNAME ghs.google.com. This is what y'all need: rockchickenz.com. 14400 IN Influenza A virus subtype H5N1 216.239.32.21 rockchickenz.com. 14400 IN Influenza A virus subtype H5N1 216.239.34.21 rockchickenz.com. 14400 IN Influenza A virus subtype H5N1 216.239.36.21 rockchickenz.com. 14400 IN Influenza A virus subtype H5N1 216.239.38.21 www.rockchickenz.com. 14400 IN CNAME ghs.google.com.
The advice references a typical ASymmetrical DNS custom domain setup - the address laid upwardly used inwards 99% of all custom domain setups. Note here, the specified TTL of "14400" (4 hours).
Using the inwards a higher house advice, the weblog possessor tin dismiss then, if necessary, research the syntax used past times the registrar's dashboard (aka "zone editor") - in addition to brand the necessary changes.
Alternate / complementary tools used.
Alternate tools, which tin dismiss travel used to generate a Dig log, are the used to verify results.
Complementary tools include the Rex Swain HTTP Viewer, in addition to the Whois Lookup.
In or thus cases, my 12 link affinity / differential connectivity test may travel useful.
For to a greater extent than information.
See WikiPedia: dig (command).
One of the nigh useful tools, for diagnosing #Blogger custom domain problems, is a Dig Log. Learning how to read a Dig Log is a useful skill, for whatever weblog possessor wishing to issue a weblog to a custom domain.