I agree,
register.com's DNS servers are not playing ball.
$ dig
www.denizlispor.com
; <<>> DiG 9.3.4-P1 <<>>
www.denizlispor.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 61465
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
but if you dig deeper you will see what they have wrong...
$dig
www.denizlispor.com @
dns185.b.register.com
; <<>> DiG 9.3.4-P1 <<>>
www.denizlispor.com @
dns185.b.register.com
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 484
;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; ANSWER SECTION:
www.denizlispor.com. 3600 IN CNAME
ghs.google.com.
ghs.google.com. 14400 IN CNAME
ghs.google.com.
;; Query time: 151 msec
;; SERVER: 216.21.232.185#53(216.21.232.185)
;; WHEN: Mon Nov 24 13:44:18 2008
;; MSG SIZE rcvd: 76
... that 'looping' CNAME is never going to work. I suggest you ask
register.com to sort out their server, it should be something like:
$ dig
ghs.google.com @
ns.google.com
; <<>> DiG 9.3.4-P1 <<>>
ghs.google.com @
ns.google.com
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54269
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 7, ADDITIONAL: 7
;; QUESTION SECTION:
;
ghs.google.com. IN A
;; ANSWER SECTION:
ghs.google.com. 604800 IN CNAME
ghs.l.google.com.
2008/11/24 Efe <
efeh...@gmail.com>:
--
Barry
-
www.nearby.org.uk -
www.geograph.org.uk -