Was this article helpful?
5 Comments
- Bernabe_CrenaEmployee
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.
Regards!
- ltwagnonRet. Employee
Thanks @Bernabe Crena!
- cjuniorNacreous
Hey,
 
In case of EDNS tester had scored my domains as "Minor problems detected!" and in my need to postpone my BIG-IP update to 11.6.3.4 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. 
- MFS_324204Nimbostratus
Hi,
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...
Regards,
- Maneesh_72711Cirrostratus
Thanks for the explanation John. Not impacting but AWS route 53 need to fix their infra.
https://forums.aws.amazon.com/message.jspa?messageID=851817