You can check DNS response. I think there may be a set flag that indicates "partial response." In this case, the client should switch transport used to send requests from UDP to TCP. As I know Freewithch (libsofia) do not support DNS request via TCP and this lead to failed DNS lookup. On Fri, Dec 10, 2021 at 8:10 PM Brian : <brians@iptel.co> wrote:
We noticed something similar with 1.1.1.1 and srv records a while ago. Didn't spend much time on it just told customer to use a resolver that works.
On Friday, December 10, 2021, Podrigal, Aron <aronp@guaranteedplus.com> wrote:
Hi, I am experiencing weird behavior. I have my nameserver set to 1.1.1.1, doing sofia_dig returns no results, one request out of five succeeds. - When I do a dig / host lookup directly outside freeswitch using 1.1.1.1, it works. - sofia_dig with any other DNS server (8.8.8.8, 9.9.9.9 etc) works. PCAP shows DNS traffic being sent and received normally. In the non working scenario, the response from 1.1.1.1 simply has zero ips. See below.
</mail/u/0/s/?view=att&th=17da4c1a164bfbe4&attid=0.0.1&disp=emb&realattid=ii_kwzyxhsx1&zw&atsh=1>
--
- Aron Podrigal
_________________________________________________________________________
The FreeSWITCH project is sponsored by SignalWire https://signalwire.com Enhance your FreeSWITCH install with disruptive priced SMS and PSTN services. Build your next product on our scalable cloud platform.
Join our online community to chat in real time https://signalwire.community
Professional FreeSWITCH Services sales@freeswitch.com https://freeswitch.com
Official FreeSWITCH Sites https://freeswitch.com/oss https://freeswitch.org/confluence https://cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users https://freeswitch.com