I figured out eventually..... My router was snarfing the requests, despite having a NAT rule to pass them through explicitly. *sigh* Phil Phil Sumner wrote:
I've got my previous DNS issue sorted, looks like it was just a matter of time for the changes needed to propgate.
My new problem is this - I query my own DNS server for NS records from inside the network, all is good and very very groovy. I get the right response. So the DNS recognises itself as authoritative for the domain "pmsumner.eu.org". Responses below.
---------------------
server 192.168.0.2 Default Server: [192.168.0.2] Address: 192.168.0.2
pmsumner.eu.org Server: [192.168.0.2] Address: 192.168.0.2
pmsumner.eu.org nameserver = ns8.zoneedit.com pmsumner.eu.org nameserver = ns19.zoneedit.com pmsumner.eu.org nameserver = pmsumner.force9.co.uk ns8.zoneedit.com internet address = 206.55.124.4 ns19.zoneedit.com internet address = 69.10.134.196 pmsumner.force9.co.uk internet address = 80.229.18.238
----------------------------
OK, now I've got the internal sorted, everything from outside should be cool and groovy too, yeah? Apparently not. If I query my nameserver from an outside computer, I get a non-authoritative answer - pointing back to itself! What the heck is that all about? Output below... can anyone explain?
set type=ns pmsumner.eu.org Server: pmsumner.force9.co.uk Address: 80.229.18.238
Non-authoritative answer: pmsumner.eu.org nameserver = ns19.zoneedit.com pmsumner.eu.org nameserver = pmsumner.force9.co.uk pmsumner.eu.org nameserver = ns8.zoneedit.com
Authoritative answers can be found from: pmsumner.force9.co.uk internet address = 80.229.18.238
-------------------
Many thanks! Phil