Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP DNS
Known Affected Versions:
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, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3
Fixed In:
13.1.0, 13.0.1, 12.1.3.6
Opened: Feb 08, 2017 Severity: 3-Major Related Article:
K32906881
During an import zone operation, ZoneRunner incorrectly associates the "@" directive with the zone name and not $ORIGIN specified.
Zones will not be imported correctly.
If the zone file to be imported contains the $ORIGIN directive, the following "@" directives will reference the zone name, which is incorrect.
Use the named-compilezone tool to "normalize" the zone file before importing into ZoneRunner. The syntax for this command is similar to the following: named-compilezone -s full -o outputfilename zone_name input.file (For information about the other available options, see the named-compilezone tool's man page.) For example, given a zone file named example.com.file that contains the following information: "example.com" $TTL 3600 example.com. 86400 IN SOA ns1.example.com. hostmaster.ns1.example.com. 2017020201 10800 3600 604800 86400 @ IN NS ns1.example.com. ns1.example.com. IN A 1.1.1.1 $ORIGIN alpha.example.com. @ IN A 2.2.2.2 $ORIGIN bravo.example.com. @ IN A 3.3.3.3 The command is as follows: named-compilezone -s full -o example.com.file.full example.com example.com.file The contents of the new file are: example.com. 86400 IN SOA ns1.example.com. hostmaster.ns1.example.com. 2017020201 10800 3600 604800 86400 example.com. 3600 IN NS ns1.example.com. alpha.example.com. 3600 IN A 2.2.2.2 bravo.example.com. 3600 IN A 3.3.3.3 ns1.example.com. 3600 IN A 1.1.1.1 Which is correct. This file can then be used to import into ZoneRunner.
None