Description: ------------ Net_DNS_Resolver:nextid() can generate an id of 65536, which will lead to the the resolver sending an id of 0, but expecting an id of 65536 in the response. The problem is that the conditional to reset the counter to 1 (Resolver.php line 423) tests the value of a post-increment operation ($id++) where it should be a pre-increment operation (++$id) or just broken out into separate steps. If the counter is initialised to a value near 65535 by mt_rand() then the condition can be hit quickly leading to failed lookups Test script: --------------- require_once('pear/Net/DNS.php'); ini_set('mbstring.internal_encoding', 'latin1'); $resolver = new Net_DNS_Resolver(); // This is usually random [0,65535], put it near 65535 to trigger repeatably. $GLOBALS['_Net_DNS_packet_id'] = 65532; $resolver->nameservers = array('8.8.8.8'); for ($i=0; $i<5; $i++) { $result = $resolver->query('www.google.com'); print "$i: " . ($result ? 'OK' : 'FAIL') . "\n"; } Expected result: ---------------- All lookups succeed, ie 0: OK 1: OK 2: OK 3: OK 4: OK Actual result: -------------- The lookup where the id overflows fails: 0: OK 1: OK 2: OK 3: FAIL 4: OK

Added patch Net_DNS-nextid-overflow.

This bug has been fixed in SVN. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.