After Setting Upwards Your Custom Domain Dns Addresses, Ever Verify Your Work

So many problems alongside custom domain publishing showtime alongside incorrectly setup DNS addresses. Sometimes the problems showtime alongside misunderstanding almost the stiff requirements of DNS addresses, other times misunderstanding almost how to purpose the Domain Manager tools provided - as well as sometimes the registrar gets involved, as well as causes problems.

Many times, I'll offering advice inward Blogger Help Forum: Something Is Broken, as well as the reply volition signal the confusion.

Here's a screenshot of my settings - I can't run into a problem!

or

I but got my registrar to setup the DNS addresses, every bit you lot gave me. Surely, they are right?

But nosotros diagnose the problem, as well as honour that the addresses are even as well as thus wrong.

In business, nosotros larn of the importance of using good known, touchstone testing procedures. People setting upwards a custom domain would produce good to larn this concept, also.

I accept a various assortment of online tools, which I purpose for diagnosing custom domain publishing problems. Here are 3 (as always, inward alphabetical order), which I purpose to examine as well as verify DNS addresses.

• Kloth Dig.
• Name.com Dig / Who.Is Lookup.
• WebMaster Toolkit Dig.

Each tool complements the other ii - none of them are a replacement for the other two.

Kloth Dig

• Lets you lot re-create as well as glue the output, easily.
• Lets you lot Dig the domain root, or whatsoever specific aliases.
• Lets you lot choose what host to perform the Dig.

Name.com Dig / Who.Is Lookup

• Lets you lot cheque results promptly, non waiting for TTL to expire.
• Lets you lot reference the outcome using an included URL.
• Lets you lot produce a Who Is lookup, to complement the Dig.

WebMaster Toolkit Dig

• Lets you lot re-create as well as glue the output, easily.
• Lets you lot Dig the domain root, or whatsoever specific aliases.
• Lets you lot reference the outcome using an included URL.

Prompt Verification Is Essential.
When you lot brand changes to the DNS addresses, you lot volition desire to cheque your results, promptly - waiting for DNS cache to expire, varying according to TTL, causes confusion. The Name.com Dig accesses the domain master copy server, as well as thus you lot tin strength out by as well as large run into results promptly. To cross cheque the Name.com Dig, you lot tin strength out purpose the Kloth Dig - as well as reference the domain master copy server, explicitly.

All Domain Hosts Must Be Verified.
When you lot brand changes to a Non Root Virtual Host, you'll demand to Dig the results. Both Kloth as well as WebMaster Toolkit allow you lot specify the host name, to target inward the Dig, as well as thus you lot tin strength out target whatsoever host - non but the domain source as well as "www" aliases.

Ability To Copy And Paste Results Is Useful.
It is useful to re-create as well as glue the results from whatsoever Dig transaction. Both Kloth as well as WebMaster Toolkit Digs render results that are non tabular array bound, as well as tin strength out hold out easily copied as well as pasted.

Ability To Reference The Result In The URL Is Useful.
It is useful to salvage a i click link to cheque Dig results, to avoid having to repeatedly glue or type a domain URL to hold out checked. Both Name.com as well as WebMaster Toolkit render results that tin strength out hold out checked past times clicking on a link, which you lot tin strength out bookmark.

A WhoIs Lookup Is Useful
Many times, the domain status, examined using a WhoIs lookup, provides an essential clue. Both when a domain buy is unsuccessful, as well as when a domain registration has expired, a Name.com Who.Is Lookup volition atomic number 82 to the occupation diagnosis.

Each of these tools render vital details as well as features, that the others produce non provide. And each of these tools, used properly, tin strength out assist individual to avoid posting inward Blogger Help Forum: Something Is Broken, frantically hollo for for help.

>> Top

Enom Hosted Custom Domains Showing Intermittent Connectivity Issues

We are seeing reports from owners of several Blogger blogs, published to custom domains, of intermittent connectivity problems, reported inward Blogger Help Forum: Something Is Broken.

Recently, I convey been unable to charge my custom domain weblog www.mydomain.com. My browsers (whether Chrome, Firefox, Safari, etc.) all rate me they are "unable to uncovering the server". Various online utilities study problems also. I am able to instruct to Blogger together with my dashboard for the blog, but cypher volition charge the page. All other services on my figurer look to endure working normally.

The work appears to endure somewhat intermittent together with varying across dissimilar ISPs, together with diverse online utilities which I use.

The domains existence reported all look to endure registered amongst eNom - together with at start glance, domain registration appears normal. We convey to create simply about detailed investigation to position a consistent detail, which appears to endure mutual to all individually reported domains.

At start glance, the typical eNom registered domain - fifty-fifty those amongst this reported work - appears to endure normal.

REGISTRY WHOIS FOR mydomain.com  Registrar: ENOM, INC. Whois Server: whois.enom.com Referral URL: http://www.enom.com Status: clientTransferProhibited  Expiration Date: 2013-04-10 Creation Date: 2012-04-10 Last Update Date: 2012-04-10  Name Servers:     dns1.name-services.com     dns2.name-services.com     dns3.name-services.com     dns4.name-services.com     dns5.name-services.com 

The clue to this work is seen inward the concluding sentence, inward the higher upwards example.

The work appears to endure somewhat intermittent together with varying across dissimilar ISPs, together with diverse online utilities which I use.

eNom uses v DNS servers. We tin cheque the output from each of the v servers, using the Kloth online Dig utility, together with specifying each server, inward turn.

• Domain: mydomain.com
• Server: dns1.name-services.com
• Query: H5N1 (IPv4 address)

and repeat for dns2.name-services.com etc.

Running a Dig against each of the v servers, nosotros tin encounter a consistency problem. Here is a re-create of the v Dig logs, concatenated.

-----------------------------------------------------------------------       dns1.name-services.com Dig Log   ; <<>> DiG 9.3.2 <<>> @dns1.name-services.com mydomain.com H5N1  ; (1 server found)  ;; global options:  printcmd  ;; Got answer:  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43536  ;; flags: qr aa; QUERY: 1, ANSWER: 4, AUTHORITY: 5, ADDITIONAL: v    ;; QUESTION SECTION:  ;mydomain.com.  IN H5N1    ;; ANSWER SECTION:  mydomain.com. 1800 IN H5N1 216.239.32.21  mydomain.com. 1800 IN H5N1 216.239.34.21  mydomain.com. 1800 IN H5N1 216.239.36.21  mydomain.com. 1800 IN H5N1 216.239.38.21    ;; AUTHORITY SECTION:  mydomain.com. 3600 IN NS dns1.name-services.com.  mydomain.com. 3600 IN NS dns2.name-services.com.  mydomain.com. 3600 IN NS dns3.name-services.com.  mydomain.com. 3600 IN NS dns4.name-services.com.  mydomain.com. 3600 IN NS dns5.name-services.com.    ;; ADDITIONAL SECTION:  dns1.name-services.com. 3600 IN H5N1 98.124.192.1  dns2.name-services.com. 3600 IN H5N1 98.124.197.1  dns3.name-services.com. 3600 IN H5N1 98.124.193.1  dns4.name-services.com. 3600 IN H5N1 98.124.194.1  dns5.name-services.com. 3600 IN H5N1 98.124.196.1  -----------------------------------------------------------------------       dns2.name-services.com Dig Log       ; <<>> DiG 9.3.2 <<>> @dns2.name-services.com mydomain.com H5N1  ; (1 server found)  ;; global options:  printcmd  ;; Got answer:  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51481  ;; flags: qr aa rd; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0    ;; QUESTION SECTION:  ;mydomain.com.  IN H5N1    ;; ANSWER SECTION:  mydomain.com. 1800 IN H5N1 216.239.36.21  mydomain.com. 1800 IN H5N1 216.239.32.21  mydomain.com. 1800 IN H5N1 216.239.38.21  mydomain.com. 1800 IN H5N1 216.239.34.21  -----------------------------------------------------------------------       dns3.name-services.com Dig Log   ; <<>> DiG 9.3.2 <<>> @dns3.name-services.com mydomain.com H5N1  ; (1 server found)  ;; global options:  printcmd  ;; Got answer:  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9542  ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0    ;; QUESTION SECTION:  ;mydomain.com.  IN H5N1    ;; AUTHORITY SECTION:  com.   3601 IN SOA dns1.name-services.com. info.name-services.com. 2010 10001 1801 604801 181  -----------------------------------------------------------------------       dns4.name-services.com Dig Log     ; <<>> DiG 9.3.2 <<>> @dns4.name-services.com mydomain.com H5N1  ; (1 server found)  ;; global options:  printcmd  ;; Got answer:  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 2101  ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0    ;; QUESTION SECTION:  ;mydomain.com.  IN H5N1    ;; AUTHORITY SECTION:  com.   3601 IN SOA dns1.name-services.com. info.name-services.com. 2010 10001 1801 604801 181  -----------------------------------------------------------------------       dns5.name-services.com Dig Log    ; <<>> DiG 9.3.2 <<>> @dns5.name-services.com mydomain.com H5N1  ; (1 server found)  ;; global options:  printcmd  ;; Got answer:  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13658  ;; flags: qr aa; QUERY: 1, ANSWER: 4, AUTHORITY: 5, ADDITIONAL: v    ;; QUESTION SECTION:  ;mydomain.com.  IN H5N1    ;; ANSWER SECTION:  mydomain.com. 1800 IN H5N1 216.239.32.21  mydomain.com. 1800 IN H5N1 216.239.34.21  mydomain.com. 1800 IN H5N1 216.239.36.21  mydomain.com. 1800 IN H5N1 216.239.38.21    ;; AUTHORITY SECTION:  mydomain.com. 3600 IN NS dns1.name-services.com.  mydomain.com. 3600 IN NS dns2.name-services.com.  mydomain.com. 3600 IN NS dns3.name-services.com.  mydomain.com. 3600 IN NS dns4.name-services.com.  mydomain.com. 3600 IN NS dns5.name-services.com.    ;; ADDITIONAL SECTION:  dns1.name-services.com. 3600 IN H5N1 98.124.192.1  dns2.name-services.com. 3600 IN H5N1 98.124.197.1  dns3.name-services.com. 3600 IN H5N1 98.124.193.1  dns4.name-services.com. 3600 IN H5N1 98.124.194.1  dns5.name-services.com. 3600 IN H5N1 98.124.196.1  ----------------------------------------------------------------------- 

Examine the Dig logs from "dns3.name-services.com." together with "dns3.name-services.com.". See the reply from those servers, which returns exclusively an "SOA" for the ".com" Top Level Domain? This is consistent of a domain, improperly setup past times the registrar. In the cases reported inward Blogger Help Forum: Something Is Broken, my reply is simple.

In your case, servers #3 together with #4 create non look to properly recognise your domain. Any online service, quest either server #3 or #4 for your domain addresses, volition likely convey problems. This may explicate your inconsistent access problem. As the registered domain owner, you lot demand to contact eNom Customer Support. Show them the Dig logs from the v servers, together with inquire them why servers #3 together with #4 seem to convey a work serving your DNS addresses.

The work appears to involve domains setup on 4/9/2012 - 4/10/2012. Hopefully, plenty domain owners volition study their problems to eNom Customer Support, then this work tin endure investigated together with resolved.

---

(Update 6/18): With a modest but a useful diagnostic tool, to analyse DNS inconsistencies similar this.

---

>> Top

Custom Domain Diagnoses - Put Dns Address Inconsistencies

One of the to a greater extent than intriguing causes of intermittent custom domain problems starts amongst inconsistent DNS server configuration. Recently, eNom, i of the "partners" inwards "Buy a domain", has been serving inconsistent DNS configurations, from fourth dimension to fourth dimension - including i rattling blatant episode the afternoon of 6/18/2012, which was reported past times several dozen angry weblog owners.

Detecting, in addition to diagnosing, the inconsistencies is typically a complicated process.

1. Identify the domain authorization servers, typically using a Who Is lookup.
2. Dig each domain address (typically "naked domain" in addition to "www" aliases), from each of the identified domain authorization servers.
3. Extract in addition to aggregate each Dig log.
4. Compare aggregated Dig snippets.

This was non a project for the faint of heart, or tech challenged, weblog owner.

Recently, I was given a handy tool which does all of this, inwards i quick GUI transaction.

The Dig Web Interface, nevertheless roughly other gratis online tool, provides us the mightiness to diagnose inconsistent DNS servers - such every bit the work eNom seems to have, inwards a thirty bit transaction.

1. Provide the "naked domain" in addition to "www" aliases.
2. Select "A" for "Type" ("A" / "CNAME" / "NS" lookups).
3. Select "Authoritative" for "Nameservers".
4. Hit "Dig".

Finally, but re-create the log produced, for examination.

It's non a fancy tool, but it does the chore - rattling well. Here, nosotros meet the log for this domain, "nitecruzr.net".

nitecruzr.net@ns11.domaincontrol.com.: nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.36.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.32.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.34.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.38.21 nitecruzr.net.  3600 IN NS ns54.domaincontrol.com. nitecruzr.net.  3600 IN NS ns53.domaincontrol.com. nitecruzr.net.  3600 IN NS ns12.domaincontrol.com. nitecruzr.net.  3600 IN NS ns11.domaincontrol.com. 
 nitecruzr.net@ns12.domaincontrol.com.: nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.36.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.32.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.34.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.38.21 nitecruzr.net.  3600 IN NS ns54.domaincontrol.com. nitecruzr.net.  3600 IN NS ns53.domaincontrol.com. nitecruzr.net.  3600 IN NS ns12.domaincontrol.com. nitecruzr.net.  3600 IN NS ns11.domaincontrol.com. 
 nitecruzr.net@ns53.domaincontrol.com.: nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.36.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.34.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.38.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.32.21 nitecruzr.net.  3600 IN NS ns54.domaincontrol.com. nitecruzr.net.  3600 IN NS ns53.domaincontrol.com. nitecruzr.net.  3600 IN NS ns12.domaincontrol.com. nitecruzr.net.  3600 IN NS ns11.domaincontrol.com. 
 nitecruzr.net@ns54.domaincontrol.com.: nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.36.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.34.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.38.21 nitecruzr.net.  3600 IN Influenza A virus subtype H5N1 216.239.32.21 nitecruzr.net.  3600 IN NS ns54.domaincontrol.com. nitecruzr.net.  3600 IN NS ns53.domaincontrol.com. nitecruzr.net.  3600 IN NS ns12.domaincontrol.com. nitecruzr.net.  3600 IN NS ns11.domaincontrol.com. 
 www.nitecruzr.net@ns11.domaincontrol.com.: www.nitecruzr.net. 3600 IN CNAME ghs.google.com. 
 www.nitecruzr.net@ns12.domaincontrol.com.: www.nitecruzr.net. 3600 IN CNAME ghs.google.com. 
 www.nitecruzr.net@ns53.domaincontrol.com.: www.nitecruzr.net. 3600 IN CNAME ghs.google.com. 
 www.nitecruzr.net@ns54.domaincontrol.com.: www.nitecruzr.net. 3600 IN CNAME ghs.google.com. 

The log is non complicated, to parse. For each URL, each authorization server is identified, in addition to Dug. In the representative of this domain, hosted on GoDaddy, nosotros meet each URL, Dug from each of four authorization servers, i past times one.

If a DNS inconsistency existed, the inwards a higher house log would exhibit the differing DNS addresses - such every bit eNom hosted domains show, from fourth dimension to time. Given this tool, it may endure easier to await for DNS inconsistencies, when problems amongst custom domains are reported, inwards Blogger Help Forum: Something Is Broken.

>> Top

Enom: Fix Your Dns Servers!

For over 2 months, we've been seeing reports from spider web log owners who published their blogs to custom domains, amongst domain DNS hosted yesteryear eNom, inwards Blogger Help Forum: Something Is Broken.

I bought my domain cite through Blogger,last week. It is beingness hosted yesteryear eNom. Ever since I bought it roughly of my followers, together with sometimes myself, can't access my site. There is either a DNS search or a "Ooops, Google Chrome can't find..."

I tried contacting eNom, together with they said they tin run across my site together with that all of my settings are correct. They enjoin it must live Google's problem.

The keyword hither is "sometimes".

Ever since I bought it roughly of my followers, together with sometimes myself, can't access my site.

Influenza A virus subtype H5N1 uncomplicated Dig, purchased using "Buy a domain", volition live asymmetrical aka "Google Apps".

enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.32.21 enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.34.21 enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.36.21 enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.38.21 www.enomhosteddomain.com. 1800 IN CNAME ghs.google.com. 

The problem, which non together with then many people appreciate, is that eNom uses multiple DNS servers, mayhap geographically separated. This is normal DNS hosting technique, together with guarantees redundancy if 1 information middle goes offline.

However, for redundancy to work, all DNS servers accept to live kept consistently synchronised. If nosotros attempt out the five eNom DNS servers individually, we volition oftentimes run across discrepancies.

enomhosteddomain.com @ dns1.name-services.com.:  enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.32.21 enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.34.21 enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.36.21 enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.38.21 enomhosteddomain.com. 3600 IN NS dns1.name-services.com. enomhosteddomain.com. 3600 IN NS dns2.name-services.com. enomhosteddomain.com. 3600 IN NS dns3.name-services.com. enomhosteddomain.com. 3600 IN NS dns4.name-services.com. enomhosteddomain.com. 3600 IN NS dns5.name-services.com.  enomhosteddomain.com @ dns2.name-services.com.:  enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.34.21 enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.38.21 enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.32.21 enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.36.21  enomhosteddomain.com @ dns3.name-services.com.:  com.   3601 IN SOA dns1.name-services.com. info.name-services.com. 2010 10001 1801 604801 181  enomhosteddomain.com @ dns4.name-services.com.:  enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.32.21 enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.36.21 enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.34.21 enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.38.21  enomhosteddomain.com @ dns5.name-services.com.:  enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.32.21 enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.34.21 enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.36.21 enomhosteddomain.com. 1800 IN Influenza A virus subtype H5N1 216.239.38.21 enomhosteddomain.com. 3600 IN NS dns1.name-services.com. enomhosteddomain.com. 3600 IN NS dns2.name-services.com. enomhosteddomain.com. 3600 IN NS dns3.name-services.com. enomhosteddomain.com. 3600 IN NS dns4.name-services.com. enomhosteddomain.com. 3600 IN NS dns5.name-services.com.   www.enomhosteddomain.com @ dns1.name-services.com.:  www.enomhosteddomain.com. 1800 IN CNAME ghs.google.com.  www.enomhosteddomain.com @ dns2.name-services.com.:  www.enomhosteddomain.com. 1800 IN CNAME ghs.google.com.  www.enomhosteddomain.com @ dns3.name-services.com.:  com.   3601 IN SOA dns1.name-services.com. info.name-services.com. 2010 10001 1801 604801 181  www.enomhosteddomain.com @ dns4.name-services.com.:  www.enomhosteddomain.com. 1800 IN CNAME ghs.google.com.  www.enomhosteddomain.com @ dns5.name-services.com.:  www.enomhosteddomain.com. 1800 IN CNAME ghs.google.com.  

This is 1 of the to a greater extent than subtle discrepancies, which I accept observed, inwards the yesteryear distich months - alone DNS Server #3 is out of synch, inwards this case. But that's enough, to brand the domain unreliable.

The work is intermittent. All all of a abrupt my site loads, only 10 minutes agone it didn't.

That's one eNom customer, out of over a dozen, which I accept documented. And that's 1 eNom customer, who should live complaining, to someone to a higher house eNom Customer Service.

eNom: cook your servers!

---

(Update 2012/07/03): Suspicion that the work is related to Anycast DNS led me to a bud, who is a immature homo TC, together with a network skillful inwards India, together with who provided an intriguing spider web log post, neatly diagnosing the underlying problem. It appears that eNom server monitoring policies may live a fleck superficial.

---

---

Use these links, for convenient reference:

• Discrepancy suspected.
• Discrepancy confirmed.

---

>> Top

Custom Domain Publishing, Together With 403 Forbidden

Next to its immediate cousin error

Another spider web log is already hosted at this address

I don't know of likewise many to a greater extent than frustrating Blogger mistake states than seeing

403 Forbidden

Most cases of "403 Forbidden", seen in addition to discussed lately inwards have geographical affinity - in addition to are typically transient - in addition to utilise to blogs published to "blogspot.com".

Some cases of "403 Forbidden" however, volition involve custom domain publishing, where the spider web log possessor should - but nearly probable volition non - see

Another spider web log is already hosted at this address

When publishing the spider web log to the domain.

In simply about cases, when publishing a spider web log to an incorrectly setup custom domain, the custom domain publishing sorcerer volition neglect to discovery the wrong DNS addresses. Instead of the spider web log owner, seeing immediately

Another spider web log is already hosted at this address.

The possessor volition see

Your spider web log has been published.

Later, the spider web log possessor - in addition to all potential spider web log readers - run into the secondary symptom

403 Forbidden

.




Here, nosotros accept an splendid instance of the problem - diagnosis, in addition to treatment.

Let's get-go hold off at a Dig log extract.

jubileeventure.org.uk.    86400    IN    Influenza A virus subtype H5N1    94.136.40.75 www.jubileeventure.org.uk. 86400 IN    Influenza A virus subtype H5N1    94.136.40.75 

Now, an HTTP draw extract, showing unsuccessful access to the domain.

Sending request:  GET / HTTP/1.1 Host: www.jubileeventure.org.uk User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20100101 Firefox/13.0.1 Referer: http://www.rexswain.com/httpview.html Connection: unopen  • Finding host IP address... • Host IP address = 94.136.40.75 • Finding TCP protocol... • Binding to local socket... • Connecting to host... • Sending request... • Waiting for response... Receiving Header: HTTP/1.1·403·Forbidden(CR)(LF) 

The solution to this work involves a touchstone misconfigured domain diagnosis (excerpted here), in addition to requires DNS address correction.

Here's what you lot have:

jubileeventure.org.uk. 86400 IN Influenza A virus subtype H5N1 94.136.40.75
www.jubileeventure.org.uk. 86400 IN Influenza A virus subtype H5N1 94.136.40.75

Google custom domain publishing requires properly setup referrals to Google servers. "94.136.40.75" is non a Google server.

Here's what you lot need:

jubileeventure.org.uk. 86400 IN Influenza A virus subtype H5N1 216.239.32.21
jubileeventure.org.uk. 86400 IN Influenza A virus subtype H5N1 216.239.34.21
jubileeventure.org.uk. 86400 IN Influenza A virus subtype H5N1 216.239.36.21
jubileeventure.org.uk. 86400 IN Influenza A virus subtype H5N1 216.239.38.21
www.jubileeventure.org.uk. 86400 IN CNAME ghs.google.com.

>> Top