Skip to content

Commit 819f7a8

Browse files
committed
edit
1 parent dd9836d commit 819f7a8

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

articles/dns/dnssec.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -94,23 +94,24 @@ The DNSSEC validation process works with trust anchors as follows:
9494
## Chain of trust
9595

9696
A chain of trust occurs when all the DNS servers involved in sending a response for a DNS query are able to validate that the response wasn't modified during transit. In order for DNSSEC validation to work end-to-end, the chain of trust must be unbroken.
97-
- Authoritative DNS servers maintain a chain of trust through the use of delegation signer (DS) records. DS records are used to verify the authenticity of child zones zone in the DNS hierarchy.
98-
- Recursive servers maintain a chain of trust through the use of trust anchors.
9997

100-
Authoritative servers:
98+
### Authoritative servers
99+
100+
Authoritative DNS servers maintain a chain of trust through the use of delegation signer (DS) records. DS records are used to verify the authenticity of child zones zone in the DNS hierarchy.
101101
- In order for DNSSEC validation to occur on a signed zone, the parent of the signed zone must also be signed. The parent zone also must have a DS record for the child zone.
102102
- During the validation process, a zone's parent is queried for the DS record. If the DS record is not present, or the DS record data in the parent does not match the DNSKEY data in the child zone, the chain of trust is broken and validation fails.
103103

104-
Recursive servers:
105-
- Recursive DNS servers (also called resolving or caching DNS servers) maintain a chain of trust through the use of DNSSEC trust anchors.
104+
### Recursive servers
105+
106+
Recursive DNS servers (also called resolving or caching DNS servers) maintain a chain of trust through the use of DNSSEC trust anchors.
106107
- The trust anchor is a DNSKEY record, or DS record containing a [hash](/dotnet/standard/security/ensuring-data-integrity-with-hash-codes) of a DNSKEY record. The DNSKEY record is created on an authoritative server when a zone is signed, and removed from the zone if the zone is unsigned.
107108
- Trust anchors must be manually installed on recursive DNS servers.
108109
- If a trust anchor for a parent zone is present, a recursive server can validate all child zones in the hierarchical namespace. This includes forwarded queries. To support DNSSEC validation of all DNSSEC-signed DNS zones, you can install a trust anchor for the root (.) zone.
109110
- Recursive servers that have DNSSEC validation disabled or aren't DNSSEC-aware don't perform validation.
110111

111112
## DNSSEC-related resource records
112113

113-
The following table provides a short description of DNSSEC-related records. For more information, see [RFC 4034: Resource Records for the DNS Security Extensions](https://datatracker.ietf.org/doc/html/rfc4034) and [RFC 7344: Automating DNSSEC Delegation Trust Maintenance](https://datatracker.ietf.org/doc/html/rfc7344).
114+
The following table provides a short description of DNSSEC-related records. For more detailed information, see [RFC 4034: Resource Records for the DNS Security Extensions](https://datatracker.ietf.org/doc/html/rfc4034) and [RFC 7344: Automating DNSSEC Delegation Trust Maintenance](https://datatracker.ietf.org/doc/html/rfc7344).
114115

115116
| Record | Description |
116117
| --- | --- |

0 commit comments

Comments
 (0)