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:03] – peter | networking:dns:unbound:selectively_override_dns_records [2022/10/08 13:27] (current) – [typetransparent zones] peter | ||
---|---|---|---|
Line 30: | Line 30: | ||
* For any names in **transparent** local-data zones, you are in complete control of all records returned; | * For any names in **transparent** local-data zones, you are in complete control of all records returned; | ||
* either they are in your local-data stanzas, or they do not exist. | * either they are in your local-data stanzas, or they do not exist. | ||
+ | |||
+ | * If you just give **local-data** for something without a local-zone directive, Unbound silently makes it into such a **transparent** local zone. | ||
+ | </ | ||
+ | |||
+ | |||
+ | |||
+ | <WRAP important> | ||
+ | **WARNING: | ||
+ | |||
+ | <code yaml> | ||
+ | local-zone: example.net transparent | ||
+ | local-data: " | ||
+ | </ | ||
+ | |||
+ | * Because this is a transparent zone and we have not listed any NS records for example.net as part of our local data, people will not be able to look up any names inside the zone even though we don't explicitly block or override them. | ||
+ | * Of course if we did list some additional names inside example.net as local-data, people would be able to look up them (and only them). | ||
+ | |||
+ | * Also, since transparent local zones are the default, this happens if you leave out the local-zone or get the name wrong by mistake or accident. | ||
+ | </ | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ===== typetransparent zones ===== | ||
+ | |||
+ | 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, do not have to map to actual DNS zones, so you can do this: | ||
+ | |||
+ | <code yaml> | ||
+ | # Instead of this: | ||
+ | |||
+ | local-zone: example.org typetransparent | ||
+ | local-data: " | ||
+ | |||
+ | # but: | ||
+ | |||
+ | local-zone: www.example.org transparent | ||
+ | local-data: " | ||
+ | </ | ||
+ | |||
+ | <WRAP info> | ||
+ | **NOTE: | ||
+ | |||
+ | * This would remove, say, MX entries. | ||
+ | * 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.1665234237.txt.gz · Last modified: 2022/10/08 13:03 by peter