Bug ID 564465: RFC 6147 compliance - support PTR records according to RFC

Last Modified: Jun 04, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP GTM(all modules)

Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4

Opened: Dec 22, 2015
Severity: 3-Major

Symptoms

DNS64 feature is not fully RFC compliant and does not process PTR records.

Impact

Clients are unable to get correct responses to PTR lookups in the ip6.arpa domain for synthesized records.

Conditions

When a client requests a reverse lookup of a AAAA that was synthesized by the BIG-IP from an original A record, we send out the unmodified PTR request to the internet

Workaround

None

Fix Information

None

Behavior Change