From 7bb56e1f44b539c8b81ef526b9e814e735614168 Mon Sep 17 00:00:00 2001 From: Philip Hazel Date: Fri, 19 Nov 2004 15:18:57 +0000 Subject: Additions to dnsdb lookups: (a) list of domains (b) change output separator. --- doc/doc-misc/WishList | 9 +-------- doc/doc-txt/ChangeLog | 14 +++++++++++--- doc/doc-txt/NewStuff | 39 ++++++++++++++++++++++++++++++++++++++- 3 files changed, 50 insertions(+), 12 deletions(-) (limited to 'doc') diff --git a/doc/doc-misc/WishList b/doc/doc-misc/WishList index d3ce50b98..aa9fb7b2b 100644 --- a/doc/doc-misc/WishList +++ b/doc/doc-misc/WishList @@ -1,4 +1,4 @@ -$Cambridge: exim/doc/doc-misc/WishList,v 1.6 2004/11/09 09:32:58 ph10 Exp $ +$Cambridge: exim/doc/doc-misc/WishList,v 1.7 2004/11/19 15:18:57 ph10 Exp $ EXIM 4 WISH LIST ---------------- @@ -1413,13 +1413,6 @@ be able to set variables in routers like in acl's." This is effectively a radical suggestion for a complete re-design, and is therefore BIG. ------------------------------------------------------------------------------ -(222) 19-Dec-03 S Iterative option for dnsdb - -A way of getting a dnsdb lookup to chop off components until something is -found: e.g. ${lookup dndsb-i{ns=a.b.c.d}} would look for nameservers for -a.b.c.d, then b.c.d, etc. ------------------------------------------------------------------------------- - (223) 22-Dec-03 S Support SOA lookup in dnsdb lookups ------------------------------------------------------------------------------ diff --git a/doc/doc-txt/ChangeLog b/doc/doc-txt/ChangeLog index 5e213d772..1def41364 100644 --- a/doc/doc-txt/ChangeLog +++ b/doc/doc-txt/ChangeLog @@ -1,4 +1,4 @@ -$Cambridge: exim/doc/doc-txt/ChangeLog,v 1.34 2004/11/19 09:45:54 ph10 Exp $ +$Cambridge: exim/doc/doc-txt/ChangeLog,v 1.35 2004/11/19 15:18:57 ph10 Exp $ Change log file for Exim from version 4.21 ------------------------------------------- @@ -149,8 +149,16 @@ Exim version 4.44 per-process caching. But the chance of anyone hitting this buglet seems very small. -37. The dnsdb lookup has a new type, "zns", which walks up the domain tree - until it finds some nameserver records. It should be used with care. +37. The dnsdb lookup has been extended in a number of ways. + + (1) There is a new type, "zns", which walks up the domain tree until it + finds some nameserver records. It should be used with care. + + (2) It is now possible to give a list of domains (or IP addresses) to be + looked up. + + (3) It is now possible to specify the separator character for use when + multiple records are returned. Exim version 4.43 diff --git a/doc/doc-txt/NewStuff b/doc/doc-txt/NewStuff index ee9f55c31..810607a5b 100644 --- a/doc/doc-txt/NewStuff +++ b/doc/doc-txt/NewStuff @@ -1,4 +1,4 @@ -$Cambridge: exim/doc/doc-txt/NewStuff,v 1.12 2004/11/19 09:45:54 ph10 Exp $ +$Cambridge: exim/doc/doc-txt/NewStuff,v 1.13 2004/11/19 15:18:57 ph10 Exp $ New Features in Exim -------------------- @@ -129,6 +129,43 @@ Version 4.44 the name servers for the high-level domains such as .com or .co.uk are not going to be on such a list. +13. It is now possible to specify a list of domains or IP addresses to be + looked up in a dnsdb lookup. The list is specified in the normal Exim way, + with colon as the default separator, but with the ability to change this. + For example: + + ${lookup dnsdb{one.domain.com:two.domain.com}} + ${lookup dnsdb{a=one.host.com:two.host.com}} + ${lookup dnsdb{ptr = <; 1.2.3.4 ; 4.5.6.8}} + + In order to retain backwards compatibility, there is one special case: if + the lookup type is PTR and no change of separator is specified, Exim looks + to see if the rest of the string is precisely one IPv6 address. In this + case, it does not treat it as a list. + + The data from each lookup is concatenated, with newline separators (by + default - see 14 below), in the same way that multiple DNS records for a + single item are handled. + + The lookup fails only if all the DNS lookups fail. As long as at least one + of them yields some data, the lookup succeeds. However, if there is a + temporary DNS error for any of them, the lookup defers. + +14. It is now possible to specify the character to be used as a separator when + a dnsdb lookup returns data from more than one DNS record. The default is a + newline. To specify a different character, put '>' followed by the new + character at the start of the query. For example: + + ${lookup dnsdb{>: a=h1.test.ex:h2.test.ex}} + ${lookup dnsdb{>| mx=<;m1.test.ex;m2.test.ex}} + + It is permitted to specify a space as the separator character. Note that + more than one DNS record can be found for a single lookup item; this + feature is relevant even when you do not specify a list. + + The same effect could be achieved by wrapping the lookup in ${tr...}; this + feature is just a syntactic simplification. + Version 4.43 ------------ -- cgit v1.2.3