Re: bind-9.10.0-P2 memory leak?

2014-09-09 Thread Len Conrad
At 09:40 PM 9/9/2014, you wrote: On 9/9/2014 05:05, lcon...@go2france.com wrote: freebsd 10.0, bind-9.10.0-p2 logging the rss field for named process: less /var/tmp/bind_rss_history.txt This never happened with earlier BIND9, and our mx1 uses this recursive BIND machine for all

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

forward only not

2010-09-29 Thread Len Conrad
FreeBSD 7.2-RELEASE BIND 9.6.0-P1 resolv.conf: nameserver 127.0.0.1 machine is postfix MX relay-only gateway on a separate machines, zen.dnsbld.domain.net on IPs 10.1.60.1 10.1.60.2, rbldnsd is running a local copy of zen.spamhaus nmap shows 10.1.60.1 and 10.1.60.2 with port 53 UDP open.

Re: forward only not

2010-09-29 Thread Len Conrad
-- Original Message -- From: Len Conrad lcon...@go2france.com Reply-To: lcon...@go2france.com Date: Wed, 29 Sep 2010 15:58:13 +0200 FreeBSD 7.2-RELEASE BIND 9.6.0-P1 resolv.conf: nameserver 127.0.0.1 machine is postfix MX relay-only gateway

caching of server fail BIND9

2010-08-24 Thread Len Conrad
We just had a problem where a BIND9 running on our postfix MX 451-rejected-as-unknown-domain all msgs from @sender.domain for 9 days. rndc flush allowed the domain to be resolved immediately and its messages accepted. When the BIND reports server fail, rather than a negative answer with

blockhole'd IP receiving referral?

2009-12-18 Thread Len Conrad
bind 9.6.1-P1 named-checkconf /etc/namedb/named.conf ... ok (in global options) options { allow-recursion { mynets; }; blackhole { !mynets; }; }; dig'ging from a !mynets IP receives a referral to rather than time-out/silence. dig'ging from a mynets IP receives an

Re: 9.6.1-P1 zone parser false errors

2009-11-04 Thread Len Conrad
-- Original Message -- From: Tony Finch d...@dotat.at Date: Wed, 4 Nov 2009 13:52:10 + On Mon, 2 Nov 2009, Mark Andrews wrote: getaddrinfo() is reporting that aspmx.l.google.com's cannonical name is mail-yx0-f102.google.com. Somewhere in the

FWD: 9.6.1-P1 zone parser false errors

2009-11-03 Thread Len Conrad
I may have missed other responses. Anbody have any idea of what's going on below? thanks Len uname -a Linux ns1.abcxyz.net 2.4.20-31.9smp #1 SMP Tue Apr 13 17:40:10 EDT 2004 i686 i686 i386 GNU/Linux old BIND: /usr/sbin/named-checkzone -v 9.2.1 /usr/sbin/named-checkzone abcxyz.com

9.6.1-P1 zone parser false errors

2009-10-30 Thread Len Conrad
uname -a Linux ns1.abcxyz.net 2.4.20-31.9smp #1 SMP Tue Apr 13 17:40:10 EDT 2004 i686 i686 i386 GNU/Linux old BIND: /usr/sbin/named-checkzone -v 9.2.1 /usr/sbin/named-checkzone abcxyz.com /var/named/db.abcxyz.com zone abcxyz.com/IN: loaded serial 2009102902 OK == current BIND:

maverick named logging

2009-01-23 Thread Len Conrad
Redhat release 9 BIND 9.5.0-P2, compiled from source named.conf has it /* logging */ ... commented out. rndc status version: 9.5.0-P2 number of zones: 81 debug level: 0 xfers running: 0 xfers deferred: 0 soa queries in progress: 0 query logging is OFF recursive clients: 8/0/1000 tcp