[Dnsmasq-discuss] Issues with DNSMASQ Retries using same port

[Singh, Prashant]

Hi Simon,

We use DNSMASQ for resolving/forwarding the dns queries of the applications hosted. We started seeing a few errors in dns resolutions. We investigated and found that the issue was due to the corrupted network path the request took. And it takes around 7 to 8 secs for network path taken to heal, hence all the retries were also failing as they took same network path.

We were exploring ways if we can force the dnsmasq to use different source port for retries so that retried requests can take random network path rather than bad network path.

I wanted to know the reasoning behind (if there is) the choice of using the same source port for retries. And is it possible to have a patch/flag in dnsmasq to update this logic?


Thanks,
Prashant

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/20220225/f52820a5/attachment.htm>