|Summary:||ASTERISK-13749: 18.104.22.168-rc2: dmsmgr can't resolve addresses|
|Reporter:||Sean Darcy (seandarcy)||Labels:|
|Date Opened:||2009-03-14 20:51:23||Date Closed:||2011-06-07 14:08:26|
|Description:||cli is full of:|
> doing dnsmgr_lookup for 'ekiga.net'
> doing dnsmgr_lookup for 'proxy01.sipphone.com'
but nslookup works fine:
[asterisk@asterisk build]$ nslookup proxy01.sipphone.com
proxy01.sipphone.com canonical name = northamerica.sipphone.com.
|Comments:||By: Leif Madsen (lmadsen) 2009-03-16 09:52:51|
Is the lookup actually failing? Those messages are normal, and are just stating that a lookup happened. There is no ERROR or WARNING there.
By: Sean Darcy (seandarcy) 2009-03-18 15:38:21
The lookup is happening. I realize it's not a great thing, but the messages occur about every 60 seconds. I usually leave the cli open, so if a user has a problem, I can often scroll back to the issue. These messages just clutter it up.
I guess I'm surprised that dnsmgr resolves the addresses so frequently, I'm not sure I care. What would be great is that it didn't post a message unless there was a problem.
By: Leif Madsen (lmadsen) 2009-03-18 15:57:50
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.
By: Sean Darcy (seandarcy) 2009-03-18 18:13:32
core set debug 18
Core debug was 12 and is now 18
waited 90 minutes, no messages.
Maybe it was sunspots.
By: Leif Madsen (lmadsen) 2009-03-18 18:22:26
Closed as it appears there was some sort of sun spots happening the day this was reported.