39 reputation
9
bio website
location
age
visits member for 1 year, 10 months
seen Feb 26 '13 at 15:36

please delete me


Jan
14
comment BIND9 as a cache-only nameserver doesn't work
If I run dig @8.8.8.8 +trace www.google.com, the output directly jumps from . to www.google.com, as you said. If I try to run, for example, dig @8.8.8.8 +trace serverfault.com I can see also the com. sections, but a lot of them has a ;; BAD (HORIZONTAL) REFERRAL at the end. The address from which the response is received is different every time (the ;; Received 505 bytes from 192.43.172.30#53(192.43.172.30) in 1798 ms has a different address every time), and finally I also obtain the correct response for serverfault.com. Is it weird?
Jan
11
comment BIND9 as a cache-only nameserver doesn't work
I edited my post with your suggestions. And I also edited my real named.conf, but as you can see lookups continue to fail.
Jan
9
comment BIND9 as a cache-only nameserver doesn't work
BIND has started because it listens on port 53 (TCP and UDP). /etc/resolv.conf contains only one line: nameserver 127.0.0.1. The re are NO errors at the startup. Errors in log files are those arising from queries.
Jan
3
comment How to execute (some) CGI commands as root
Thank you. If I'm not wrong, I can use setuid only if I write the CGI in C, right?
Jan
3
comment How to execute (some) CGI commands as root
Thank you. Unfortunately I don't know how to do either of those things (wrapper script, passwordless sudo), but maybe I should ask different questions?
Dec
3
comment Where BIND9 saves its cache?
I know this is an OT, but I have directory "/etc/bind/"; and I also run chown root.bind /etc/bind/, but the dumpdb file doesn't yet exist.
Dec
3
comment Where BIND9 saves its cache?
Thank you for the explanation. But after I run rndc dumpdb --cache I can't find the file in /var/cache/bind. This folder contains managed-keys.bind and managed-keys.bind.jnl
Nov
24
comment Why don't DNS root servers answer?
I can't say, but I tried again to query a root-server at home and it works, while at university it doesn't work.
Nov
21
comment Why don't DNS root servers answer?
For the first time I tried to dig to a root-server from my home network (when I asked the question I was at university) and it works. Probably the university network's firewall blocks the direct queries to a root-server and permits queries only to the internal DNS server. Is it possible?
Nov
21
comment Why don't DNS root servers answer?
If I query an other root-server, it doesn't work. I've the same output. But if I query 8.8.8.8 (for example) I've the correct answer.
Nov
21
comment Why don't DNS root servers answer?
I checked and the root hints file was updated. Anyway I update it again just to be sure. In spite of everything, dig @b.root-servers.net www.ubuntu.com still doesn't work (and it doesn't work even if I use any other root-server).
Nov
20
comment Install and use BIND9 as forwarder - step by step
If I simply use, for example, dig www.amazon.com I obtain SERVFAIL. If I use dig @10.0.2.3 www.amazon.com I obtain the correct answer. If I use nslookup I obtain SERVFAIL.