networking:dns:unbound:selectively_override_dns_records
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| networking:dns:unbound:selectively_override_dns_records [2022/10/08 13:11] – peter | networking:dns:unbound:selectively_override_dns_records [2022/10/08 13:27] (current) – [typetransparent zones] peter | ||
|---|---|---|---|
| Line 56: | Line 56: | ||
| There is no way to use a **typetransparent** zone but delete certain record types for some names, which you would use so you can do things like remove all MX entries for some host names. | There is no way to use a **typetransparent** zone but delete certain record types for some names, which you would use so you can do things like remove all MX entries for some host names. | ||
| - | ---- | + | Zones, however, |
| - | + | ||
| - | Zones do not have to map to actual DNS zones, so you can do this: | + | |
| <code yaml> | <code yaml> | ||
| + | # Instead of this: | ||
| + | |||
| local-zone: example.org typetransparent | local-zone: example.org typetransparent | ||
| local-data: " | local-data: " | ||
| Line 74: | Line 74: | ||
| * This would remove, say, MX entries. | * This would remove, say, MX entries. | ||
| - | * Since I just tried this out, note that a transparent local zone with no data naturally does not blank out anything, so if you want to totally delete a name's records you need to supply some dummy record (e.g. a TXT record). | + | * A transparent local zone with no data naturally does not blank out anything, so if you want to totally delete a name's records you need to supply some dummy record (e.g. a TXT record). |
| </ | </ | ||
networking/dns/unbound/selectively_override_dns_records.1665234709.txt.gz · Last modified: 2022/10/08 13:11 by peter