We tried probing the dns server for handhelds.org from outside UKC and it worked, but there were problems with the name server. See this dig command.
dig ns handhelds.org
;; reply from unexpected source: 195.20.224.234#53, expected
217.160.173.251#53
;; Warning: ID mismatch: expected ID 44340, got 15531
;; reply from unexpected source: 195.20.224.234#53, expected
217.160.173.251#53
;; Warning: ID mismatch: expected ID 44340, got 15531
;; reply from unexpected source: 195.20.224.234#53, expected
217.160.173.251#53
;; Warning: ID mismatch: expected ID 44340, got 15531
; <<>> DiG 9.3.1 <<>> ns handhelds.org
;; global options: printcmd
;; connection timed out; no servers could be reached
Inside UKC dig would not connect to that remote dns server, the reason being that if a corrupt entry is cached into the DNS, it will remain in the
cache until it is flushed (24hrs??). The bottom line is that the owner of the remote dns site has to fix their dns entries for it to work properly
and make sure that forward and reverse lookups work properly.