We are testing a query:
- FQDN: test.example.net
- Query Type: AAAA
Client > DNS A > DNS B
Simplified DNS query flow:
- Client queries test.example.net -t AAAA
- Query goes to DNS A which then forwards the query to DNS B
- DNS B responds with 2 ORDERED IPV6 addresses to DNS A
- DNS A receives the 2 ORDERED IPV6 addresses from DNS B
Expected
- DNS A responsds with 2 ORDERED IPV6 addresses to Client
What is happening
- DNS A responds with 2 NON-ORDERED IPV6 addresses to Client
Things we have tried:
- Turn off cacheing on DNS A and DNS B
Things we noticed:
- When the query goes from DNS A to DNS B, the transaction ID changes
- When DNS A responds with 2 IPV6 address to Client, the transaction ID changes back to the original transaction ID.
Questions:
- What options/settings are we overlooking to make sure the Client receives fixed ordered query responses?
- What could be the reason for DNS A receiving the ordered query response from DNS B, but does not send the ordered query response back to the client?
Thanks BD
SRV
then they add a priority or equivalent field to encode that. Why does your client has a need of ordered list? Specifically forAAAA
aka IPv6 records, the listing/priority is governed by/etc/gai.conf
.