dns:dnssec
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| dns:dnssec [2025/01/13 12:05] – [Internal DNSSEC] bstafford | dns:dnssec [2025/05/09 13:18] (current) – [Internal DNSSEC] bstafford | ||
|---|---|---|---|
| Line 40: | Line 40: | ||
| From [[https:// | From [[https:// | ||
| - | The following query will only return an IP if DNSSEC validation is turned off. If DNSSEC validation is turned on, the resolver will realise | + | The following query will only return an IP if DNSSEC validation is turned off. If DNSSEC validation is turned on, the resolver will realize |
| < | < | ||
| The following record should work regardless of wether or not DNSSEC validation is enabled because it is correctly DNSSEC signed. | The following record should work regardless of wether or not DNSSEC validation is enabled because it is correctly DNSSEC signed. | ||
| Line 88: | Line 88: | ||
| When we paste the following into a shell, we get the desired result: | When we paste the following into a shell, we get the desired result: | ||
| < | < | ||
| + | ===== DNSSEC Flags ===== | ||
| + | Flags in DNS Query Packets ([[https:// | ||
| + | |||
| + | * **DO**: The DO bit is included in a DNS query and is an abbreviation for " | ||
| + | * **AD**: The AD bit is included in a DNS response and is an abbreviation for " | ||
| + | * **CD**: The CD bit is included in a DNS query and is an abbreviation for " | ||
| + | * **AA**: A fourth important flag (bit) that can be present in a DNS packet header is the AA bit. This flag isn't new with DNSSEC, but it can be used when DNSSEC is deployed. The AA bit is included in a DNS response and is an abbreviation for " | ||
| + | |||
| ===== Disabling DNSSEC ===== | ===== Disabling DNSSEC ===== | ||
| Remove the DS records at the parent (via registrar) | Remove the DS records at the parent (via registrar) | ||
| Line 98: | Line 106: | ||
| ===== Internal DNSSEC ===== | ===== Internal DNSSEC ===== | ||
| + | [[https:// | ||
| + | |||
| Internal domains should not be DNSSEC signed. If they are truly internal domains, connecting into the chain of trust would be challenging if not impossible. However, there is another concern if the internal domains are receiving DDNS updates, then they will constantly need to re-sign the domain, which could end up being a major performance impact. DNSSEC validation is done by DNS servers, not clients, so if the clients are going to be querying servers that have the authoritative data, there is absolutely nothing to validate. | Internal domains should not be DNSSEC signed. If they are truly internal domains, connecting into the chain of trust would be challenging if not impossible. However, there is another concern if the internal domains are receiving DDNS updates, then they will constantly need to re-sign the domain, which could end up being a major performance impact. DNSSEC validation is done by DNS servers, not clients, so if the clients are going to be querying servers that have the authoritative data, there is absolutely nothing to validate. | ||
| Line 108: | Line 118: | ||
| ===== DNSSEC and Forwarding | ===== DNSSEC and Forwarding | ||
| - | [[forwarding# | + | [[infoblox_nios: |
dns/dnssec.1736769926.txt.gz · Last modified: by bstafford
