| Where allowed to run: All environments (*ALL) Threadsafe: No |
Parameters Examples Error messages |
The Check DNS Zone (CHKDNSZNE) command checks the syntax and integrity of a zone data file. It performs the same checks as the Domain Name System (DNS) server when loading a zone. This is useful for checking zone data files before configuring them into a DNS server.
Restrictions:
| Top |
| Keyword | Description | Choices | Notes |
|---|---|---|---|
| ZONEDMN | Zone name | Character value | Required, Positional 1 |
| ZONEDTAF | Zone file | Path name | Required, Positional 2 |
| DEBUG | Show debug information | *NO, *YES | Optional |
| QUIET | Quiet mode | *NO, *YES | Optional |
| CHKDNSJRNF | Check journal files | *NO, *YES | Optional |
| CLASS | Class | *IN, *CH, *HS | Optional |
| CHKDTAITG | Check load integrity | *NONE, *FULL, *FULLNOSIBL, *LOCAL, *LOCALNOSIBL | Optional |
| INFMT | Input format | *DFT, *TEXT, *RAW | Optional |
| OUTFMT | Output format | *DFT, *TEXT, *RAW | Optional |
| DETAIL | Dump style | *DFT, *FULL, *BASIC | Optional |
| CANONICAL | Dump canonical names | *NO, *YES | Optional |
| ZONESTMF | Zone output file | Path name, *STDOUT | Optional |
| CHKLBL | Check labels | *WARN, *FAIL, *IGNORE | Optional |
| CHKMXADR | Check MX for address | *WARN, *FAIL, *IGNORE | Optional |
| CHKMXNAME | Check MX for CNAME | *WARN, *FAIL, *IGNORE | Optional |
| CHKNSADR | Check servers | *WARN, *FAIL, *IGNORE | Optional |
| CHKSRVNAME | Check SRV for CNAME | *WARN, *FAIL, *IGNORE | Optional |
| CHKWLDCRD | Check for wildcards | *WARN, *IGNORE | Optional |
| TOSTMF | Output file | Path name, *STDOUT | Optional |
| Top |
Specifies the domain name of the zone being checked.
This is a required parameter.
| Top |
Specifies the zone data file to check.
This is a required parameter.
| Top |
Specifies whether or not to enable debugging.
| Top |
Specifies whether or not to perform the check in quiet mode. Quiet mode will only use an exit code and not send any messages.
| Top |
Specifies, when loading a data zone file, whether or not to read the DNS journal file if it exists. A DNS journal file contains zone updates that need to be merged with the master zone data file.
| Top |
Specifies the protocol group of the information.
| Top |
Specifies which post-load zone data integrity checks to perform.
| Top |
Specify the format of the zone data file to be read as input.
| Top |
Specify the format of the output file specified by the TOSTMF parameter. This does not have any effect unless the utility dumps the zone data contents.
| Top |
Specifies the detail level of records for the dumped zone data file. The *FULL format is most suitable for processing automatically by a separate script. The *BASIC format is more human-readable and is thus suitable for manual editing. This parameter will only have an effect if the utility dumps the zone data contents with the TOSTMF parameter. It also does not have any meaning if the OUTFMT parameter is not *TEXT.
| Top |
Specifies whether or not to dump the zone data file in canonical format. Since a Resource Record (RR) can have more than one name (aliases) associated with it, this allows you to dump the real (canonical) name instead of the aliases.
| Top |
Specifies the output file to which the zone data will be written. The output format will be based on the OUTFMT, DETAIL and CANONICAL parameters.
| Top |
Specifies how to handle domain name check errors.
Errors are handled using the following failure modes.
| Top |
Specifies how to handle errors found when checking MX records to see if they are addresses.
Errors are handled using the following failure modes.
| Top |
Specifies how to handle errors found when checking MX records to see if they refer to a CNAME.
Errors are handled using the following failure modes.
| Top |
Specifies how to handle errors found when checking NS records to see if they are addresses.
Errors are handled using the following failure modes.
| Top |
Specifies how to handle errors found when checking SRV records to see if they refer to a CNAME.
Errors are handled using the following failure modes.
| Top |
Specifies whether or not to check for non-terminal wildcards. Non-terminal wildcards are almost always the result of a failure to understand the wildcard matching algorithm (RFC 1034).
Errors are handled using the following failure modes.
| Top |
Specifies the name of a stream file where all command output is written.
| Top |
CHKDNSZNE ZONEDMN(i5os.ibm.com)
ZONEDTAF('/QIBM/UserData/OS400/DNS/NS/i5os.ibm.com.DB')
CHKDNSJRNF(*YES)
This command checks the zone 'i5os.ibm.com' in the zone data file '/QIBM/UserData/OS400/DNS/NS/i5os.ibm.com.DB'. It also checks any DNS journal files that may apply to this zone. Output from this command might look like this:
zone i5os.ibm.com/IN: loaded serial 2 OK
| Top |
*ESCAPE Messages
| Top |