I am currently working out a problem with DDNS failures. We are currently seeing about 10 to 20 updates per second, but every once in while the app used to send the updates gives the following error: java.net.SocketTimeoutException: Receive timed out at java.net.PlainDatagramSocketImpl.receive(Native Method) at java.net.DatagramSocket.receive(DatagramSocket.java:711) at org.xbill.DNS.SimpleResolver.send(SimpleResolver.java:248) at com.alopa.prov.core.ddns.DDNS.sendUpdate(DDNS.java:435) at com.alopa.prov.core.ddns.DDNS.notify(DDNS.java:336) at com.alopa.prov.core.ddns.DDNSClient.run(DDNSClient.java:98) At this time I see nothing in the logs that shows an error. ### BIND CONFIG ### options { directory "/etc/bind"; auth-nxdomain no; # conform to RFC1035 recursion yes; version "Off with your head!"; interface-interval 0; notify no; transfer-format many-answers; recursive-clients 100000; allow-transfer { xfer; }; allow-query { trusted; }; blackhole { bogon; }; }; zone "{ZONE}" { type master; file "{ZONEFILE}"; notify explicit; also-notify {{IP};}; allow-transfer { {IP}; }; allow-update { {IP}; {IP};}; }; ### END ### What I am looking for suggestions on how I can diagnose the problem, and any ideas on how to increase performance of bind to support this many updates. Thanks. NOTE: Yes I know I am not using TSIG this is a limitation with the app we are using. And I don't want to hear any flames about that... I have already flamed the vender plenty. And I also know this box is used for recursive lookups and authoritative zones, again, don't need to hear the flames. -- Peter Kringle Callsign: KC9BIW http://www.planetnet.org