|Summary:||ASTERISK-16420: " > doing dnsmgr_lookup" message appears on the console often|
|Date Opened:||2010-07-25 04:48:06||Date Closed:||2012-10-17 14:42:47|
|Description:||the above message appears on the console every 1m45s. The peer is using an ip address, not a hostname. Chatted with kpfleming on irc (see additional info) who confirms that this is a bug|
****** ADDITIONAL INFORMATION ******
kpfleming: that should probably be optimized to not use dnsmgr for ip addresses
kpfleming: it's probably showing up that often because each time it is called it is expected to create a dnsmgr object, but it doesn't because the input is a raw IP address
kpfleming: and it's being called every time that peer has a message sent to it for an OPTIONS ping (qualify) or something like that
kpfleming: it's definitely a bug
|Comments:||By: frinklabs (frinklabs) 2010-08-06 13:25:26|
I get the same behavior when using a hostname instead of an IP address.
Be advised that I was also getting the associated intermittent SIP loss of connectivity described in 0017777 but 188.8.131.52 resolved that part. Still getting the flood of messages on the console though.
By: vittorio alfieri (vittorio88) 2012-03-14 11:49:26.481-0500
Hello I am running Asterisk 184.108.40.206 ,and can confirm this is still a bug.
In my case Asterisk is automatically sending the ip address indicated in sip.conf under a register statement to get DNS resolved. It should be parsed, and identified as an IP address before being sent to get DNS resolved.
I am aware I can disable DNS lookup, but I require it for a different proxy.
Here is a sample output:
> doing dnsmgr_lookup for '220.127.116.11'
By: Richard Mudgett (rmudgett) 2012-03-14 13:05:29.816-0500
This issue may have been fixed by ASTERISK-17815.
Please try a newer version of Asterisk.
By: jmls (jmls) 2012-10-17 14:42:47.986-0500
fixed in 11+