YarisBueller,
It appears that the same DNS issues we touched on early in 2008 have reappeared. DNS requests for yarisworld.com get a response but www.yarisworld.com does not.
The WHOIS record shows that DNS for yarisworld.com should be served by:
However, there are generic NS records in the DNS record held by the registrar, GoDaddy, which point to ns*.ds.nac.net:
So let's see what NAC (the spammer and malware-writer friendly hosting service that you mentioned you were going to get away from last year) has for yarisworld.com:
This issue is simple to resolve. Please simply create a CNAME pointing "www" to "yarisworld.com" right alongside the existing A record at GoDaddy.
It appears that the same DNS issues we touched on early in 2008 have reappeared. DNS requests for yarisworld.com get a response but www.yarisworld.com does not.
The WHOIS record shows that DNS for yarisworld.com should be served by:
Domain servers in listed order:But neither of those servers exist in the master DNS records:
NS1.YARISWORLD.COM
NS2.YARISWORLD.COM
~$ dig any ns1.yarisworld.com
; <<>> DiG 9.4.2-P2 <<>> any ns1.yarisworld.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 25507
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ns1.yarisworld.com. IN ANY
;; Query time: 0 msec
;; SERVER: 10.2.1.2#53(10.2.1.2)
;; WHEN: Thu Jan 1 08:42:28 2009
;; MSG SIZE rcvd: 36
~$ dig any ns2.yarisworld.com
; <<>> DiG 9.4.2-P2 <<>> any ns2.yarisworld.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 54765
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ns2.yarisworld.com. IN ANY
;; Query time: 0 msec
;; SERVER: 10.2.1.2#53(10.2.1.2)
;; WHEN: Thu Jan 1 08:38:13 2009
;; MSG SIZE rcvd: 36
However, there are generic NS records in the DNS record held by the registrar, GoDaddy, which point to ns*.ds.nac.net:
~$ dig any yarisworld.com
; <<>> DiG 9.4.2-P2 <<>> any yarisworld.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39729
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 2, ADDITIONAL: 0
;; QUESTION SECTION:
;yarisworld.com. IN ANY
;; ANSWER SECTION:
yarisworld.com. 13937 IN A 209.123.181.71
yarisworld.com. 13937 IN NS ns2.ds.nac.net.
yarisworld.com. 13937 IN NS ns1.ds.nac.net.
;; AUTHORITY SECTION:
yarisworld.com. 13937 IN NS ns1.ds.nac.net.
yarisworld.com. 13937 IN NS ns2.ds.nac.net.
;; Query time: 0 msec
;; SERVER: 10.2.1.2#53(10.2.1.2)
;; WHEN: Thu Jan 1 08:44:23 2009
;; MSG SIZE rcvd: 122
So let's see what NAC (the spammer and malware-writer friendly hosting service that you mentioned you were going to get away from last year) has for yarisworld.com:
~$ dig @ns1.ds.nac.net any yarisworld.comUh oh, nobody's home. Let's try the other one:
dig: couldn't get address for 'ns1.ds.nac.net': not found
~$ dig @ns2.ds.nac.net any yarisworld.comAnd therein lies the problem. "yarisworld.com" works because there is an A record for it at GoDaddy, but "www.yarisworld.com" does not because the server(s) hosting the core record do not have a CNAME (alias) entry for www, nor do the supposed tertiary servers respond at all (so even if they had CNAME entries it would not matter).
dig: couldn't get address for 'ns2.ds.nac.net': not found
This issue is simple to resolve. Please simply create a CNAME pointing "www" to "yarisworld.com" right alongside the existing A record at GoDaddy.