[OpenSIPS-Users] opensips 2.4.7 - Dispatcher ds_is_in_list() DNS resolution

solarmon solarmon at one-n.co.uk
Mon Mar 1 16:54:36 EST 2021

Hi Livui,

OK, understood that a DNS lookup is done at reload/restart, and the IP is
cached. This makes sense in that ds_is_in_list() matches to the IP address
that has been cached.

The problem is that when you list/dump the dispatcher database it is still
showing the DNS address, and not the resolved IP address. You could
obviously get into the situation where the DNS has been changed, but it is
still using the old IP address.

Obviously, the workaround is to get the dispatcher module is issued with a
reload. However, what is the impact on active sessions/dialogs when
dispatcher is reloaded? Can this be done without impacting active


On Mon, 1 Mar 2021 at 16:11, Liviu Chircu <liviu at opensips.org> wrote:

> On 01.03.2021 18:04, solarmon wrote:
> > I would like somebody to confirm this is the behaviour - i.e.
> > ds_is_in_list() does a DNS lookup on the Destination address of the
> > endpoint.
> Hi,
> Technically speaking, ds_is_in_list() does *not* perform a DNS lookup,
> as it works with cached data.  DNS lookups are indeed done, however,
> during startup or after each MI "ds_reload" command.  The resulting IP
> addresses will be cached *indefinitely*, until the next reload/restart.
> Best regards,
> --
> Liviu Chircu
> www.twitter.com/liviuchircu | www.opensips-solutions.com
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210301/da3ab56a/attachment.html>

More information about the Users mailing list