Once upon a time, Stephen John Smoogen <smooge@gmail.com> said:
> Because a lot of networks use routing tricks to send traffic to particular
> DNS server IP addresses. They may round robin, traffic route, or other
> methods to send you to different DNS servers with the same ip address. Even
> if they are all the same 'model' device, they have different features
> turned on or are at different revisions.. so whatever you have cached is
> wrong.
I'm pretty sure that's considered "their problem"... anycast servers are
expected to behave the same (or similar enough) in terms of features
supported. Real DNS recursive servers like Unbound and BIND keep info
about particular servers by IP.
However, using info that's being tracked as a reason to not to use
multiple servers is a rather weak argument... keeping track of info for
additional servers should not be difficult.
Good point. However at what point to improving these features becomes where systemd "bloat. Systemd came up with an "ok" low level solution and then people keep nitpicking that it could do a better job and track more things.. and eventually you have systemd rewritten in eLISP and a native emacs mode. [Change to more appropriate languages for the 21st century.. rewritten in javascript and a native Node-VSCode mode.]
--
Chris Adams <linux@cmadams.net>
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org