Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.0.7

Bug #16312 DNS query returns no more than seven NAPTR records
Submitted: 2009-06-09 22:48 UTC
From: renne Assigned: bate
Status: Closed Package: Net_DNS (version 1.0.1)
PHP Version: 5.2.9 OS: Gentoo Linux
Roadmaps: (Not assigned)    
Subscription  


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 43 - 13 = ?

 
 [2009-06-09 22:48 UTC] renne (Rene Bartsch)
Description: ------------ In several tests I've realized that Net_DNS returns not more than seven NAPTR records (haven't checked that for other record types). Please fix Net_DNS to show all NAPTR records. Test script: --------------- <?php require_once 'Net/DNS.php'; $resolver = new Net_DNS_Resolver(); $resolver->debug = 1; $response = $resolver->query('4.2.7.8.7.2.2.7.0.0.7.9.4.e164.arpa', 'NAPTR', 'IN'); if ($response) { foreach ($response->answer as $rr) { $rr->display(); } } ?> Expected result: ---------------- Shows 10 records. Actual result: -------------- Shows only 7 results.

Comments

 [2010-08-09 09:46 UTC] mikepultz (Mike Pultz)
Looks like there was a logic issues in Resolver.php related to truncated packets. This would have broken truncated packets for any RR, not just NAPTR. On a related note, the logic just above this that checks the packet length was also broken; so it would never select the send_tcp option based on the packet size. Patch to follow.
 [2010-08-09 09:47 UTC] mikepultz (Mike Pultz)
 [2010-08-09 09:48 UTC] bate (Marco Kaiser)
-Assigned To: +Assigned To: bate
 [2010-08-09 10:40 UTC] bate (Marco Kaiser)
-Status: Assigned +Status: Closed
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.