[asterisk-bugs] [Asterisk 0010983]: Bad DNS lookups on ENUMLOOKUP - various problems

[noreply at bugs.digium.com]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=10983 
====================================================================== 
Reported By:                jtodd
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   10983
Category:                   Functions/func_enum
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 85140 
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             10-15-2007 12:54 CDT
Last Modified:              01-15-2008 20:28 CST
====================================================================== 
Summary:                    Bad DNS lookups on ENUMLOOKUP - various problems
Description: 
1) ENUMLOOKUP apparently is doing an "A" record lookup on the domain in the
From: header.  Why is this?  It's bad, slow, and leaks information.  Should
not happen; no reason for it to happen.

2) Failures on ENUMLOOKUP on NAPTR records on ISN-style lookups.  The
lookups just outright fail, though the DNS returns the correct NAPTR back
to Asterisk.  Not sure if this is an ISN-style problem or if this is an
issue with all NAPTRs.

====================================================================== 

---------------------------------------------------------------------- 
 file - 01-15-08 20:28  
---------------------------------------------------------------------- 
I've fixed the DNS lookup as of revision 98954, and the other lookup I
believe is a configuration thing. If you look at the debug output it's
doing the lookup against e164.org, not freenum.org. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-15-08 20:28  file           Status                   new => resolved     
01-15-08 20:28  file           Resolution               open => fixed       
01-15-08 20:28  file           Assigned To               => file            
01-15-08 20:28  file           Note Added: 0080724                          
======================================================================