[asterisk-bugs] [Asterisk 0014667]: 1.6.1.0-rc2: dmsmgr can't resolve addresses

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14667 
====================================================================== 
Reported By:                seandarcy
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14667
Category:                   General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.1.0-rc2 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-03-14 20:51 CDT
Last Modified:              2009-03-18 15:57 CDT
====================================================================== 
Summary:                    1.6.1.0-rc2: dmsmgr can't resolve addresses
Description: 
cli is full of:

> doing dnsmgr_lookup for 'ekiga.net'
> doing dnsmgr_lookup for 'proxy01.sipphone.com'

but nslookup works fine:

nslookup ekiga.net
Server:		10.10.11.252
Address:	10.10.11.252#53

Non-authoritative answer:
Name:	ekiga.net
Address: 86.64.162.35

[asterisk at asterisk build]$ nslookup proxy01.sipphone.com
Server:		10.10.11.252
Address:	10.10.11.252#53

Non-authoritative answer:
proxy01.sipphone.com	canonical name = northamerica.sipphone.com.
Name:	northamerica.sipphone.com
Address: 198.65.166.131

sean
====================================================================== 

---------------------------------------------------------------------- 
 (0101950) lmadsen (administrator) - 2009-03-18 15:57
 http://bugs.digium.com/view.php?id=14667#c101950 
---------------------------------------------------------------------- 
Hmmmmmm... 60 seconds eh? I'm surprised to because the default (according
to the configuration file) is every 300 seconds (5 minutes).

Can you enable the debugging on the console and see if there is anything
obvious that might pop up to indicate why that is happening? Perhaps the
debug will give us some hints. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-03-18 15:57 lmadsen        Note Added: 0101950                          
======================================================================