Question about a high load BIND server setup...

[Blake Covarrubias]

Those messages are being sent by your server in response to failed  
connections to port 53. Because named is no longer listening on that  
port (service is stopped) your server is informing machines which are  
attempting to make connections to port 53 that the port is closed.

--
Blake Covarrubias


On Aug 31, 2006, at 11:08 PM, John Von Essen wrote:

> 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 at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-isp
> To unsubscribe, send any mail to "freebsd-isp-unsubscribe at freebsd.org"
>