DNS lookup failure on one PN server

[#1]

Resolves ok using opendns, google dns, level 3 dns and the root servers.
For interest I also tried and successfully resolved using this dns == 83-244-207-119.cust-83.exponential-e.net. 

[#2]

Just tested a few...
[tt]
$ dig @212.159.6.9 dansdata.com

; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> @212.159.6.9 dansdata.com
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached
$ dig @8.8.8.8 dansdata.com

;; Query time: 32 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Feb  2 19:28:57 2015
;; MSG SIZE  rcvd: 46

$ dig @208.67.222.123 dansdata.com

;; Query time: 24 msec
;; SERVER: 208.67.222.123#53(208.67.222.123)
;; WHEN: Mon Feb  2 19:29:26 2015
;; MSG SIZE  rcvd: 46
$ dig @4.2.2.1 dansdata.com

;; Query time: 287 msec
;; SERVER: 4.2.2.1#53(4.2.2.1)
;; WHEN: Mon Feb  2 19:29:50 2015
;; MSG SIZE  rcvd: 46

[#3]

dig hangs for quite a while before returning a result using dig @212.118.241.33 dansdata.com
Can anybody confirm the same results?

[#4]

The nameservers for dansdata.com are ns1.dnswizards.com and ns2.dnswizards.com.
ns1.dnswizards.com = 64.85.13.6
ns2.dnswizards.com = 64.85.19.190
There doesn't appear to be any problem repeatedly doing "dig @64.85.13.6 ns2.dnswizards.com" and "dig @64.85.19.190 dansdata.com".
But "dig @212.159.6.9 ns1.dnswizards.com" often times out.
11110_110: dig @212.118.241.33 dansdata.com often times out or replies after over 3 seconds. I recommend +tries=1 in your .digrc file. If dig takes a long time but then prints out a lower response time, it may have retried the query.
Edit: 212.118.241.33 replies with SERVFAIL after 3-4 seconds, or times out.

[#5]

Doesn't seem to like the 212 ip range...
[tt]
$ dig @212.118.241.1 dansdata.com

; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> @212.118.241.1 dansdata.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 56020
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;dansdata.com.                  IN      A

;; Query time: 29 msec
;; SERVER: 212.118.241.1#53(212.118.241.1)
;; WHEN: Mon Feb  2 20:10:16 2015
;; MSG SIZE  rcvd: 30

$ dig dansdata.com

; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> dansdata.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57490
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1

;; QUESTION SECTION:
;dansdata.com.                  IN      A

;; ANSWER SECTION:
dansdata.com.          30601  IN      A      64.85.21.74

;; AUTHORITY SECTION:
dansdata.com.          30601  IN      NS      ns2.dnswizards.com.
dansdata.com.          30601  IN      NS      ns1.dnswizards.com.

;; ADDITIONAL SECTION:
ns1.dnswizards.com.    23437  IN      A      64.85.13.6

;; Query time: 8 msec
;; SERVER: 192.168.0.15#53(192.168.0.15)
;; WHEN: Mon Feb  2 20:11:47 2015
;; MSG SIZE  rcvd: 109

[#6]

Quote from: 11110_110

dig hangs for quite a while before returning a result using dig @212.118.241.33 dansdata.com

Gives a "SERVFAIL" here.
I normally find that to be a very reliable resolver. 

[#7]

Quote from: 11110_110

Doesn't seem to like the 212 ip range...

No, it's not that

Quote

; <<>> DiG 9.8.6-P1 <<>> dansdata.com @212.44.39.117 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13635 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;dansdata.com.                  IN      A ;; ANSWER SECTION: dansdata.com.          21599  IN      A      64.85.21.74 ;; Query time: 234 msec ;; SERVER: 212.44.39.117#53(212.44.39.117) ;; WHEN: Mon Feb 02 20:29:21 GMT Standard Time 2015 ;; MSG SIZE  rcvd: 46

[#8]

Damn 

[#9]

If you've got the time you can test some of these.
http://public-dns.tk/nameserver/gb.html
The two demon.co.uk servers don't resolve it and they're 212....