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

noreply at bugs.digium.com noreply at bugs.digium.com
Mon Oct 15 13:05:33 CDT 2007


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10983 
====================================================================== 
Reported By:                jtodd
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10983
Category:                   Functions/func_enum
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!): 85140 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             10-15-2007 12:54 CDT
Last Modified:              10-15-2007 13:05 CDT
====================================================================== 
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.

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

---------------------------------------------------------------------- 
 jtodd - 10-15-07 13:05  
---------------------------------------------------------------------- 
OK, some incorrect debugging data in the "Additional Information" page. 
The console on that example was not typical.  Here is the typical output
during this failure mode:

*CLI>   == Using TOS bits 0
    -- Executing [0*270 at sip-from-world:1]
Set("SIP/blahmoofoo.com-870b6000", "ENUM=") in new stack
    -- Executing [0*270 at sip-from-world:2]
Hangup("SIP/blahmoofoo.com-870b6000", "") in new stack
  == Spawn extension (sip-from-world, 0*270, 2) exited non-zero on
'SIP/blahmoofoo.com-870b6000'
    -- Executing [h at sip-from-world:1]
Hangup("SIP/blahmoofoo.com-870b6000", "") in new stack
  == Spawn extension (sip-from-world, h, 1) exited non-zero on
'SIP/blahmoofoo.com-870b6000'
[Oct 15 18:19:42] NOTICE[1539]: cdr.c:432 ast_cdr_free: CDR on channel
'SIP/blahmoofoo.com-870b6000' not posted


Additional notes:

   1) This is Asterisk running on an OpenBSD 4.1 system.

   2) My resolving nameservers are 204.91.156.197 and 192.148.252.133

   3) The "search" line in /etc/resolv.conf contains "freenum.org" 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-15-07 13:05  jtodd          Note Added: 0072023                          
======================================================================




More information about the asterisk-bugs mailing list