You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like kamailio when using SRV records does not read and use the ADDITIONAL SECTION, and instead sends another DNS request to get the IP for the host, which is inefficient and could be supported just like mentioned in the RFC 2782 :
For each element in the new list
query the DNS for address records for the Target or
use any such records found in the Additional Data
section of the earlier SRV response.
Example, for our _sip._udp service using our service discovery tool :
;; ANSWER SECTION:
_sip._udp.service.consul. 15 IN SRV 1 1 5063 ourserver.node.us.consul.
_sip._udp.service.consul. 15 IN SRV 1 1 5060 ourserver.node.us.consul.
_sip._udp.service.consul. 15 IN SRV 1 1 5062 ourserver.node.us.consul.
_sip._udp.service.consul. 15 IN SRV 1 1 5061 ourserver.node.us.consul.
;; ADDITIONAL SECTION:
ourserver.node.us.consul. 15 IN A 98.XXX.XXX.XXX
It has all the information it needs but it still does an extra request. Any thoughts?
The text was updated successfully, but these errors were encountered:
It seems like kamailio when using SRV records does not read and use the ADDITIONAL SECTION, and instead sends another DNS request to get the IP for the host, which is inefficient and could be supported just like mentioned in the RFC 2782 :
Example, for our
_sip._udp
service using our service discovery tool :It has all the information it needs but it still does an extra request. Any thoughts?
The text was updated successfully, but these errors were encountered: