Re: named 9.10 halted

2014-08-20 Thread Matus UHLAR - fantomas
On 20.08.14 19:59, Len Conrad wrote: monitor reported port 53 not responding I started it manually, then found this in /var/log/messages, which stared about 18:46 and ran until BIND stopped, followed by my manual start: Aug 20 19:12:23 rns1 kernel: Limiting icmp unreach response from 696 to 20

Re: bind-users Digest, Vol 1917, Issue 1

2014-08-20 Thread Bazy V
My confusion arises from these 2 sections in replies from bind-users Digest, Vol 1916, Issue 2# 4 reply states it "should be" # 4 -> >Note that either 0.220/24 wasn't technically correct, it should be: >220/24 NS ns2.sub.test.com. >0.220 CNAME 0.220/24 >but that's an o

Re: named 9.10 halted

2014-08-20 Thread Noel Butler
so what about named's syslog entries, most commonly found in daemon log On 21/08/2014 10:59, Len Conrad wrote: > uname -a > FreeBSD rns1..net 10.0-RELEASE > > named -v > BIND 9.10.0-P2 > > this is a recursive-only NS restricted allowing recursive queries from > "ournetworks" ACL > >

named 9.10 halted

2014-08-20 Thread Len Conrad
uname -a FreeBSD rns1..net 10.0-RELEASE named -v BIND 9.10.0-P2 this is a recursive-only NS restricted allowing recursive queries from "ournetworks" ACL monitor reported port 53 not responding I started it manually, then found this in /var/log/messages, which stared about 18:46 and ran u