[asterisk-bugs] [Asterisk 0017902]: Asterisk 1.8.0-beta3 DNSMGR address corruption

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17902 
====================================================================== 
Reported By:                afried
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17902
Category:                   Core/PBX
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.8.0-beta3 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-08-23 11:51 CDT
Last Modified:              2010-08-25 21:53 CDT
====================================================================== 
Summary:                    Asterisk 1.8.0-beta3 DNSMGR address corruption
Description: 
This may be related to 0017496.  DNSMGR appears to be assigning the wrong
ip addresses to host names that appear in iax.conf and "forgettting"
previous lookups.

This is causing inbound calls from contexts with hostnames to be handled
by the default context.

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

---------------------------------------------------------------------- 
 (0126347) afried (reporter) - 2010-08-25 21:53
 https://issues.asterisk.org/view.php?id=17902#c126347 
---------------------------------------------------------------------- 
I believe this issues is more than simply a display problem as evidenced by
the fact that incoming calls are not being properly handled by the correct
incoming context.  In my case, all of the incoming calls land in "guest".

I even tried hardcoding IP addresses into the host fields.  The calls
still land in guest, and dnsmgr produced this log entry:

[Aug 25 22:48:39] NOTICE[1670]: dnsmgr.c:167 dnsmgr_refresh: dnssrv: host
'64.34.181.47' changed from 173.208.45.51:0 to 64.34.181.47:0 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-08-25 21:53 afried         Note Added: 0126347                          
======================================================================