Difference between revisions of "OPS535 Advanced DNS"
| Line 8: | Line 8: | ||
nsupdate is used to submit Dynamic DNS Update requests as defined in RFC 2136 to a name server. This allows resource records to be added or removed from a zone without manually editing the zone file. A single update request can contain requests to add or remove more than one resource record. | nsupdate is used to submit Dynamic DNS Update requests as defined in RFC 2136 to a name server. This allows resource records to be added or removed from a zone without manually editing the zone file. A single update request can contain requests to add or remove more than one resource record. | ||
</pre> | </pre> | ||
| + | * TSIG - Transaction SIGnatures | ||
| + | ** BIND primarily supports TSIG for server to server communication. | ||
| + | ** TSIG can also be useful for dynamic update.The nsupdate program supports TSIG via the -k and -y command line options or inline by use of the key. | ||
* DNSSEC | * DNSSEC | ||
| + | ** Cryptographic authentication of DNS information is possible through the DNS Security (DNSSEC-bis) extensions, defined in RFC 4033, RFC 4034, and RFC 4035. | ||
Revision as of 01:31, 9 November 2016
- DNS Logging
- Dynamic DNS
- Dynamic Zone - Allow-update
- Dynamic DNS update using nsupdate
Man Page:
nsupdate is used to submit Dynamic DNS Update requests as defined in RFC 2136 to a name server. This allows resource records to be added or removed from a zone without manually editing the zone file. A single update request can contain requests to add or remove more than one resource record.
- TSIG - Transaction SIGnatures
- BIND primarily supports TSIG for server to server communication.
- TSIG can also be useful for dynamic update.The nsupdate program supports TSIG via the -k and -y command line options or inline by use of the key.
- DNSSEC
- Cryptographic authentication of DNS information is possible through the DNS Security (DNSSEC-bis) extensions, defined in RFC 4033, RFC 4034, and RFC 4035.
