Kirk wrote:
$ dig +trace @127.0.0.1 -x 203.22.30.47
; <<>> DiG 9.4.3 <<>> +trace @127.0.0.1 -x 203.22.30.47
; (1 server found)
;; global options: printcmd
. 517909 IN NS G.ROOT-SERVERS.NET.
. 517909 IN NS A.ROOT-SERVERS.NET.
.
Noel Butler wrote:
On Wed, 2009-06-10 at 11:20 +0100, Jason Crummack wrote:
dig @82.138.243.4 30.22.203.in-addr.arpa NS
I get a response from that IP as well, however from mine, I don't, I
suspect that's the server cache.
Is this IP range still delegated to you?
dig 30
Thanks for the reply Noel i still don't understand why that would work
on the external name server we have access to and not on our internal one?
$ dig @82.138.243.4 30.22.203.in-addr.arpa NS
; <<>> DiG 9.3.2 <<>> @82.138.243.4 30.22.203.in-addr.arpa NS
; (1 server found)
;; global options:
n 1473 ms
running bind version 9.4.3
named.conf
<<<
options {
directory "/var/named";
query-source address 192.168.0.15 port 53;
allow-recursion { any; };
allow-query { any; };
allow-query-cache { any; };
};
logging {
category lame-servers { null; };
};
# mai
4 matches
Mail list logo
