on 25-Jan-2019 12:34
February 1, 2019 is DNS Flag Day. This day could be catastrophic to your website if you don't have the appropriate configurations in place for your DNS servers. In this video, I outline the details of DNS Flag Day and talk about what to do to make sure you are ready for the big transition that is coming. Enjoy!
Excellent explanation John! One Important thing: If you manage a Normal Cache Resolver DNS inside your company, is not mandatory to update your DNS to send EDNS and only accept EDNS responses. The most sensitive point is to make EDNS-compatible the Authoritative DNS, this issue is very important because starting 1 Feb several DNS resolver vendors will not accept noEDNS Authoritative DNS responses.
¬†In case of EDNS tester had scored my domains as "Minor problems detected!" and in my need to postpone my BIG-IP update to 220.127.116.11 due to possible new issues not yet tested, do you think is good workaround to apply the code from here: https://devcentral.f5.com/s/articles/implementing-client-subnet-dns-requests, plus adding code to fix buffer size "DNS::edns0 sz 512", it covers all is needed for awhile? This way, should I be "compliant"? Is it a good workaround till the BIG-IP version can be updated or need I just to plan upgrade soon I can?
¬†Thank you in advance.
If External DNS is being pointed to Link Controller (LC) Inbound Wide IP, does it consider as using GTM?
Anything to be worried about?
I can see in the KB https://support.f5.com/csp/article/K07808381 - it mentioned as Non-applicable, just to clarify this...
Thanks for the explanation John. Not impacting but AWS route 53 need to fix their infra.