Fix more links

diff --git a/pdns/docs/markdown/authoritative/upgrading.md b/pdns/docs/markdown/authoritative/upgrading.md
index c875bba7cde2fb2626d4b40c3aabd4f9f12e7d57..ece641753d2b3d66c9a1941430b11bd0c711a5a5 100644 (file)
--- a/pdns/docs/markdown/authoritative/upgrading.md
+++ b/pdns/docs/markdown/authoritative/upgrading.md
@@ -195,7 +195,7 @@ You can test the BINARY change with the new and experimental 'pdnssec test-schem
 drop index orderindex;
 create index recordorder on records (domain_id, ordername text_pattern_ops);
 ```
-Additionally, with 3.2 supporting empty non-terminals (see [XXX](XXX)), your frontend may need some changes.
+Additionally, with 3.2 supporting empty non-terminals (see [Rules for filling out fields in Database Backends](dnssec.md#rules-for-filling-out-fields-in-database-backends)), your frontend may need some changes.
 
 Due to a bug, in 3.1 and earlier releases, the pipebackend would default to a 1000 second timeout for responses from scripts, instead of the intended and documented 1000 milliseconds (1 second). In 3.2, pipe-timeout is in fact in milliseconds. To avoid some surprise, the default is now 2000 (2 seconds). If you have slow pipebackend scripts, make sure to increase [`pipe-timeout`](backend-pipe.md#pipe-timeout).
 
@@ -218,7 +218,7 @@ postgres=# ALTER TABLE records ALTER COLUMN content TYPE VARCHAR(65535);
 postgres=# ALTER TABLE tsigkeys alter column algorithm type VARCHAR(50);
 ```
 
-The definition of 'auth' and 'ordername' in backends has changed slightly, see [XXX](XXX).
+The definition of 'auth' and 'ordername' in backends has changed slightly, see [Rules for filling out fields in Database Backends](dnssec.md#rules-for-filling-out-fields-in-database-backends).
 
 PowerDNS 3.0 and 3.1 will only fetch DNSSEC metadata and key material from the first DNSSEC-capable backend in the launch line. In 3.1, the bindbackend supports DNSSEC storage. This means that setups using `launch=bind,gsqlite3` or `launch=gsqlite3,bind` may break. Please tread carefully!
 
@@ -255,7 +255,7 @@ A: Yes. If the '-dnssec' setting is enabled, PowerDNS expects the 'auth' field t
 Q: I want to fill out the 'auth' and 'ordername' fields directly, how do I do this?
 A: The 'auth' field should be '1' or 'true' for all records that are within your zone. For a zone without delegations, this means 'auth' should always be set. If you have delegations, both the NS records for that delegation and possible glue records for it should not have 'auth' set.
 
-For more details on 'auth' and 'ordername', please see [XXX](XXX).
+For more details on 'auth' and 'ordername', please see [Rules for filling out fields in Database Backends](dnssec.md#rules-for-filling-out-fields-in-database-backends).
 
 Q: If I don't update to the new DNSSEC schema, will 3.0 give identical answers as 2.9.x?
 A: Not always. The core DNS logic of 3.0 was changed, so even if no changes are made to the database, you may get different answers. This might happen for zones without SOA records for example, which used to (more or less) work. An upgrade from 2.9.x to 3.0 should always be monitored carefully.

diff --git a/pdns/docs/markdown/recursor/settings.md b/pdns/docs/markdown/recursor/settings.md
index 343625571d3ecaa4d07e703b22871b1948460eaa..bbbcbf2d6a62973fe79e58f357156c5f2e90b573 100644 (file)
--- a/pdns/docs/markdown/recursor/settings.md
+++ b/pdns/docs/markdown/recursor/settings.md
@@ -20,16 +20,16 @@ Authoritative zones can transmit a TTL value that is lower than that specified i
 Comma separated list of 'zonename=filename' pairs. Zones read from these files (in BIND format) are served authoritatively. Example: `auth-zones=example.org=/var/zones/example.org, powerdns.com=/var/zones/powerdns.com`. Available since version 3.1.
 
 ## `carbon-ourname`
-If sending carbon updates, if set, this will override our hostname. See [XXX](XXX). Available beyond 3.5.3.
+If sending carbon updates, if set, this will override our hostname. See ["PowerDNS Metrics"](../common/logging.md#sending-to-carbongraphitemetronome). Available beyond 3.5.3.
 
 ## `carbon-server=...`
-If set to an IP or IPv6 address, will send all available metrics to this server via the carbon protocol, which is used by graphite and metronome. See [XXX](XXX). Available beyond 3.5.3.
+If set to an IP or IPv6 address, will send all available metrics to this server via the carbon protocol, which is used by graphite and metronome. See ["PowerDNS Metrics"](../common/logging.md#sending-to-carbongraphitemetronome). Available beyond 3.5.3.
 
 ## `carbon-interval=...`
-If sending carbon updates, this is the interval between them in seconds. See [XXX](XXX). Available beyond 3.5.3.
+If sending carbon updates, this is the interval between them in seconds. See ["PowerDNS Metrics"](../common/logging.md#sending-to-carbongraphitemetronome). Available beyond 3.5.3.
 
 ## `chroot`
-If set, chroot to this directory for more security. See [XXX](XXX).
+If set, chroot to this directory for more security. See [Security](../common/security.md).
 
 Make sure that `/dev/log` is available from within the chroot. Logging will silently fail over time otherwise (on logrotate).