The situation is that some isp or vps provider may hijack public dns server like 8.8.8.8/1.1.1.1 or even all(by redirect udp port 53 request),which results a dns cache longer than expected.
Even if the dns record is already updated,the result we got from server by looking up through public dns server is still the outdated one.This could lead to a duplicated dns record update and notify.eg,If the cache is 5mins and the cronjob frequency is 1min,we will see a 4~5 times duplicated dns record update and nofity.
The situation is that some isp or vps provider may hijack public dns server like 8.8.8.8/1.1.1.1 or even all(by redirect udp port 53 request),which results a dns cache longer than expected. Even if the dns record is already updated,the result we got from server by looking up through public dns server is still the outdated one.This could lead to a duplicated dns record update and notify.eg,If the cache is 5mins and the cronjob frequency is 1min,we will see a 4~5 times duplicated dns record update and nofity.
This is why I reopened https://github.com/TimothyYe/godns/issues/172 today by mistake then close it after I found it's actually a dns cache problem.
DOH/DOT resolver seems to be a good solution for such kind of dns hijack(cache) problem,is it possible to add support to godns?
Thanks!