Bug ID 460590: Multiple DNS resolvers and multiple domains behavior

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:
11.4.1, 11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6

Opened: May 05, 2014

Severity: 3-Major

Related Article: K16029

Symptoms

If one of two nameservers returns a response of "No such name" for a domain query, then the same domain query is not tried on the second nameserver.

Impact

When a response is already received from the first nameserver, the domain query is not attempted on the second nameserver. So even though an entry may be present on the second nameserver, the resolve fails. This is expected behavior. DNS operates on the assumption that all nameservers everywhere contain the correct and valid data. Always have two name servers in sync so they should have the same set of domain entries.

Conditions

Two name servers configured: The DNS entry for a particular domain name is present only in one name server.

Workaround

None

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips