mikeV02 opened a new issue, #7082: URL: https://github.com/apache/trafficcontrol/issues/7082
<!-- ************ STOP!! ************ If this issue identifies a security vulnerability, DO NOT submit it! Instead, contact the Apache Traffic Control Security Team at [email protected] and follow the guidelines at https://apache.org/security regarding vulnerability disclosure. - For *SUPPORT QUESTIONS*, use the #traffic-control channel on the ASF slack (https://s.apache.org/tc-slack-request) or the Traffic Control Users mailing list (send an email to [email protected] to subscribe). - Before submitting, please **SEARCH GITHUB** for a similar issue or PR * https://github.com/apache/trafficcontrol/issues * https://github.com/apache/trafficcontrol/pulls --> <!-- Do not submit security vulnerabilities or support requests here - see above --> ## This Bug Report affects these Traffic Control components: <!-- delete all those that don't apply --> - Traffic Router ## Current behavior: <!-- Describe how the bug happens --> For IPv4 only infrastructure, that is, no IPv6 anywhere more than the default link-local, Traffic Router replies NXDOMAIN for AAAA when a client issues request. Causing DNS resolvers to flush cache and mark the Delivery Service FQDN as non-existent for the TTL lifetime. This happens regardless the value of "IPv6 Routing Enabled" on the Delivery Service ## Expected behavior: <!-- Describe what the behavior would be without the bug --> Traffic Router should return NODATA (an empty NOERROR reply) instead of NXDOMAIN for non-existent AAAA records within an existent zone. ## Steps to reproduce: <!-- If the current behavior is a bug, please provide the *STEPS TO REPRODUCE* and include the applicable TC version. --> Do a DNS lookup for the Delivery Service for A records, NS, records, AAAA records. A and NS return valid answers, AAAA returns NXDOMAIN. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
