Re: Question about a high load BIND server setup...

Okay, so this is where I am at.

sysctl tunables are standard, but somaxconn was bumped up to 512.

I edit /boot/loader.conf and added:

kern.dfldsiz=900000000
kern.dflssiz=700000000
kern.maxdsiz=900000000
kern.maxssiz=700000000
kern.maxusers=512

And I recompiled Bind 9.3.2 and enabled the internal memory allocator.

One thing I still get, which I dont understand why, is whenever I stop named, I get the following console error:

Aug 31 23:47:57 cache01 kernel: Limiting icmp unreach response from 213 to 200 packets/sec
Aug 31 23:47:58 cache01 kernel: Limiting icmp unreach response from 242 to 200 packets/sec
Aug 31 23:47:59 cache01 kernel: Limiting icmp unreach response from 208 to 200 packets/sec
Aug 31 23:48:00 cache01 kernel: Limiting icmp unreach response from 224 to 200 packets/sec

As soon as I start named, it goes away. Any idea what this can be?

-John
_______________________________________________
freebsd-isp@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-isp
To unsubscribe, send any mail to "freebsd-isp-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Question about a high load BIND server setup...
    ... Because named is no longer listening on that port your server is informing machines which are attempting to make connections to port 53 that the port is closed. ... Aug 31 23:47:57 cache01 kernel: Limiting icmp unreach response from 213 to 200 packets/sec ...
    (freebsd-isp)
  • speed issues
    ... When downloading or uploading files from this freebsd using ftp a have ... Limiting icmp unreach response from 268 to 200 packets per second ...
    (freebsd-questions)
  • speed issues
    ... When downloading or uploading files from this freebsd using ftp a have ... Limiting icmp unreach response from 268 to 200 packets per second ...
    (freebsd-questions)