From: bert hubert Date: Mon, 22 Sep 2014 19:21:20 +0000 (+0200) Subject: remove spurious 'any' (thanks seth) plus clarify CNAME walking X-Git-Tag: rec-3.7.0-rc1~208^2~3 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=9e0a9689fc03d0cb2ee90e4cbead77712e47bc6f;p=thirdparty%2Fpdns.git remove spurious 'any' (thanks seth) plus clarify CNAME walking --- diff --git a/pdns/docs/alias.md b/pdns/docs/alias.md index e5096c492a..33d6ba41f2 100644 --- a/pdns/docs/alias.md +++ b/pdns/docs/alias.md @@ -13,7 +13,7 @@ ALIAS record will return A or AAAA records with addresses belonging to the target of the ALIAS. Similarly, if an ANY query arrives for the name, all records from the local store -for that name are returned, plus the any A and AAAA types associated with the ALIAS +for that name are returned, plus the A and AAAA types associated with the ALIAS record's target. As an example: @@ -35,8 +35,9 @@ based on the IPv4 address of www.powerdns.com which was retrieved earlier. The same applies, mutatis mutandis, for a query for the AAAA record of example.com. -It should be noted that if www.powerdns.com is itself a CNAME chain to A or AAAA records, -the data returned should be the eventual A and AAAA records, and not the CNAMEs themselves. +It should be noted that if www.powerdns.com is itself a CNAME chain to A or +AAAA records, the data returned should be sourced from the eventual A and +AAAA records. The intermediate CNAMEs should not be returned. A query for the A of serv.example.com gets normal CNAME processing, and then similarly hits the ALIAS record, and returns the synthesized A record for example.com.