I'm afraid Planetarion has a few nameserver problems of its own.
slave.planetarion.com is dead:
Code:
[tomkins@wildfire ~]$ dig ANY planetarion.com @slave.planetarion.com.
; <<>> DiG 9.3.3rc2 <<>> ANY planetarion.com @slave.planetarion.com.
; (1 server found)
;; global options: printcmd
;; connection timed out; no servers could be reached
dns-3.planetarion.com is a lame server (it isn't acting as a slave server, it's serving from cache instead of giving an authoritative answer):
Code:
[tomkins@wildfire ~]$ dig ANY planetarion.com @dns-3.planetarion.com.
; <<>> DiG 9.3.3rc2 <<>> ANY planetarion.com @dns-3.planetarion.com.
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16731
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 3, ADDITIONAL: 4
;; QUESTION SECTION:
;planetarion.com. IN ANY
;; ANSWER SECTION:
planetarion.com. 1232 IN A 195.149.21.29
planetarion.com. 1232 IN MX 10 mail.planetarion.com.
;; AUTHORITY SECTION:
planetarion.com. 172703 IN NS dns-3.planetarion.com.
planetarion.com. 172703 IN NS dns1.planetarion.com.
planetarion.com. 172703 IN NS slave.planetarion.com.
...
Both dns1.planetarion.com and dns-3.planetarion.com allow recursive queries (bit concerning for security):
Code:
[tomkins@wildfire ~]$ dig +short A slashdot.org @dns1.planetarion.com.
66.35.250.150
[tomkins@wildfire ~]$ dig +short A slashdot.org @dns-3.planetarion.com.
66.35.250.150
You might want to get your admin to fix this.