[OpenSIPS-Users] DNS could not resolve hostname in dispatcher

Fri Jan 12 09:56:15 UTC 2024

Hi Alain,

Thank you for your help and your suggestion.

We are trying to implement DNS_CACHE module with a record "oms" in etc/hosts (same in dispatcher) and Opensips doesn't resolve the name when DNS_CACHE is activated.

Here are our declarations in opensips.cfg file :

### DNS CACHE MODULE ###loadmodule "cachedb_local.so"
loadmodule "cachedb_sql.so"
loadmodule "dns_cache.so"
modparam("cachedb_sql", "cachedb_url", "sql:mysql://opensips:opensipsrw@ossdb/opensips")
modparam("cachedb_sql", "db_table","cachedb")
modparam("dns_cache", "cachedb_url", "sql:mysql://opensips:opensipsrw@ossdb/opensips")

Here are the logs :
CRITICAL:core:mk_proxy: could not resolve hostname: "oms"
Jan 12 10:47:52 [37] ERROR:dispatcher:add_dest2list: could not resolve oms, skipping it
Jan 12 10:47:52 [37] WARNING:dispatcher:ds_load_data: failed to add destination sip:oms:5060 in group 100
Jan 12 10:47:52 [37] WARNING:dispatcher:ds_load_data: No record loaded from db, running on empty sets

There is another name ("rtpe") declared in etc/hosts is also used in opensips.cfg and there is no problem to resolve it. The problem seams to be only in dispatcher.

Are we missing something in our way of using it ?

Regards,

   Guillaume

De : Users <users-bounces at lists.opensips.org> De la part de Alain Bieuzent
Envoyé : mardi 9 janvier 2024 10:54
À : OpenSIPS users mailling list <users at lists.opensips.org>
Objet : Re: [OpenSIPS-Users] DNS could not resolve hostname in dispatcher

Hi Guillaume,

have you tried to cache your DNS queries with the dns_cache module (https://opensips.org/html/docs/modules/3.3.x/dns_cache) ?

Regards

De : Users <users-bounces at lists.opensips.org<mailto:users-bounces at lists.opensips.org>> au nom de <guillaume.desgeorge at orange.com<mailto:guillaume.desgeorge at orange.com>>
Répondre à : OpenSIPS users mailling list <users at lists.opensips.org<mailto:users at lists.opensips.org>>
Date : mardi 9 janvier 2024 à 10:35
À : OpenSIPS users mailling list <users at lists.opensips.org<mailto:users at lists.opensips.org>>
Objet : [OpenSIPS-Users] DNS could not resolve hostname in dispatcher

Hi everyone,

We are facing a problem with Opensips 3.3 (but I've done tests on opensips 2.4 and it was the same).

In the dispatcher, if we have a name instead of an IP address in "destination", and that the DNS falls down, we have an error "could not resolve hostname" in the log. Then, Opensips can't resolve the name, there is no more OPTIONS message sent to the destination but the state stays as 0 and if a call arrives, Opensips still route the INVITE to the last known IP address.

I find that's strange :

  *   Either Opensips consider that the DNS is down but the destination may be still up with the last IP address he knows and he could still send OPTIONS messages to the last known IP address
  *   Either Opensips consider that the DNS is down and doesn't send OPTIONS message but in that case he should not send INVITE to the old IP address.

I work with a product that has his own DNS and removes the name of the server in the DNS when the machine is down. So everytime the server is down, Opensips can't resolve the name and still send calls to that server...

Is there any parameters I can use to change that way of working ?

Regards,

    Guillaume
Orange Restricted

____________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.
_______________________________________________ Users mailing list Users at lists.opensips.org<mailto:Users at lists.opensips.org> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20240112/53ce2911/attachment-0001.html>