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)
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
