Bind 8

From: Anton Bester (extech_at_dod.co.za)
Date: 10/18/05

  • Next message: shafi kamal: "Re: For advice in tcp implementation" 
    Date: Tue, 18 Oct 2005 19:54:02 +0200
To: freebsd-net@freebsd.org

    Hi All,

    I do not know if this is the correct forum for this questions, if not please point me in the right direction.

    My secondary DNS server all of a sudden started to chop up about 100% of my server's cpu, I'm running a FreeBSD 5.1-RELEASE server with Bind 8. It was doning fine until I noticed that the sever's cpu running near 100%, it turned out to be bind.

    When I restart bind it takes a couple of minutes but then it is back at 70% - 100% with a lot of traffic being send to my primary DNS server, I have noticed the following error in the Primary DNS log file:

    Oct 18 12:24:01 ns /kernel: Limiting icmp unreach response from 315 to 200 packets per second
    Oct 18 12:24:02 ns /kernel: Limiting icmp unreach response from 259 to 200 packets per second
    Oct 18 12:24:03 ns /kernel: Limiting icmp unreach response from 223 to 200 packets per second

    The above disapeared when I have stop bind on the secondary server.

    The following is a tcpdump from the secondary when bind is running:

    19:11:57.499201 PRIMARY.SERVER.3177 > SECONDARY.SERVER.domain: 45643+ [1au] PTR? 74.112.10.196.in-addr.arpa. (55)
    19:11:57.499586 SECONDARY.SERVER.52770 > PRIMARY.SERVER.domain: 57396+ [1au] PTR? 74.112.10.196.in-addr.arpa. (55)
    19:11:57.501314 SECONDARY.SERVER.52770 > PRIMARY.SERVER.domain: 46641+ [1au] PTR? 74.112.10.196.in-addr.arpa. (55)
    19:11:57.501435 PRIMARY.SERVER.3177 > SECONDARY.SERVER.domain: 15653+ [1au] PTR? 74.112.10.196.in-addr.arpa. (55)
    19:11:57.503114 SECONDARY.SERVER.52770 > PRIMARY.SERVER.domain: 9949+ [1au] PTR? 74.112.10.196.in-addr.arpa. (55)
    19:11:57.503140 PRIMARY.SERVER.3177 > SECONDARY.SERVER.domain: 37941+ [1au] PTR? 74.112.10.196.in-addr.arpa. (55)
    19:11:57.504878 SECONDARY.SERVER.52770 > PRIMARY.SERVER.domain: 9772+ [1au] PTR? 74.112.10.196.in-addr.arpa. (55)
    19:11:57.504925 PRIMARY.SERVER.3177 > SECONDARY.SERVER.domain: 48193+ [1au] PTR? 74.112.10.196.in-addr.arpa. (55)
    19:11:57.506677 PRIMARY.SERVER.3177 > SECONDARY.SERVER.domain: 1059+ [1au] PTR? 74.112.10.196.in-addr.arpa. (55)
    19:11:57.506811 SECONDARY.SERVER.52770 > PRIMARY.SERVER.domain: 32623+ [1au] PTR? 74.112.10.196.in-addr.arpa. (55)
    19:11:57.508561 SECONDARY.SERVER.domain > PRIMARY.SERVER.3177: 28517 1/4/1 (217)
    19:11:57.508643 PRIMARY.SERVER.3177 > SECONDARY.SERVER.domain: 63119+ [1au] PTR? 74.112.10.196.in-addr.arpa. (55)
    19:11:57.509849 PRIMARY.SERVER.domain > SECONDARY.SERVER.52770: 28288 1/4/1 (217)
    19:11:57.510078 SECONDARY.SERVER.domain > PRIMARY.SERVER.3177: 13104 1/4/1 (217)
    19:11:57.511345 SECONDARY.SERVER.domain > PRIMARY.SERVER.3177: 43705 1/4/1 (217)
    19:11:57.511493 PRIMARY.SERVER.domain > SECONDARY.SERVER.52770: 48426 1/4/1 (217)
    19:11:57.512702 SECONDARY.SERVER.domain > PRIMARY.SERVER.3177: 59554 1/4/1 (217)
    19:11:57.513345 PRIMARY.SERVER.domain > SECONDARY.SERVER.52770: 48467 1/4/1 (217)
    19:11:57.514387 SECONDARY.SERVER.52770 > PRIMARY.SERVER.domain: 43310+ [1au] PTR? 74.112.10.196.in-addr.arpa. (55)
    19:11:57.515025 PRIMARY.SERVER.domain > SECONDARY.SERVER.52770: 16747 1/4/1 (217)
    19:11:57.523654 SECONDARY.SERVER.52770 > PRIMARY.SERVER.domain: 40443+ [1au] PTR? 74.112.10.196.in-addr.arpa. (55)
    19:11:57.525204 SECONDARY.SERVER.52770 > PRIMARY.SERVER.domain: 24062+ [1au] PTR? 74.112.10.196.in-addr.arpa. (55)
    19:11:57.526786 SECONDARY.SERVER.52770 > PRIMARY.SERVER.domain: 55218+ [1au] PTR? 74.112.10.196.in-addr.arpa. (55)
    19:11:57.528310 SECONDARY.SERVER.52770 > PRIMARY.SERVER.domain: 8947+ [1au] PTR? 74.112.10.196.in-addr.arpa. (55)
    19:11:57.529826 SECONDARY.SERVER.52770 > PRIMARY.SERVER.domain: 30856+ [1au] PTR? 74.112.10.196.in-addr.arpa. (55)
    19:11:57.531340 SECONDARY.SERVER.52770 > PRIMARY.SERVER.domain: 33843+ [1au] PTR? 74.112.10.196.in-addr.arpa. (55)
    19:11:57.532870 SECONDARY.SERVER.52770 > PRIMARY.SERVER.domain: 24256+ [1au] PTR? 74.112.10.196.in-addr.arpa. (55)
    19:11:57.534386 SECONDARY.SERVER.52770 > PRIMARY.SERVER.domain: 64054+ [1au] PTR? 74.112.10.196.in-addr.arpa. (55)
    19:11:57.536038 SECONDARY.SERVER.52770 > PRIMARY.SERVER.domain: 65247+ [1au] PTR? 74.112.10.196.in-addr.arpa. (55)

    The same is happening on the Primary Server, when bind is running on the secondary the cpu of the primary shot up to 70%-100% with the same sort of tcpdump info as above.

    Do anybody have an idea what is going on here.

    Thanks
    Anton

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

  • Next message: shafi kamal: "Re: For advice in tcp implementation"