Re: tinydns authoritative ACL's

Harm van Tilborg wrote:
> Hi Jimmy,
> 
> I think the location notation is what you are looking for. See:
> 
> http://cr.yp.to/djbdns/tinydns-data.html
> 
> for that, especially the text below `Data format'.
> 

Hi,

thanks for such a quick response. In the documentation I see this

Quote

For versions 1.04 and above: You may include a client location on each 
line. The line is ignored for clients outside that location. Client 
locations are specified by % lines:
      %lo:ipprefix

  means that IP addresses starting with ipprefix are in location lo. lo 
is a sequence of one or two ASCII letters. A client is in only one 
location; longer prefixes override shorter prefixes. For example,
      %in:192.168
      %ex
      +jupiter.heaven.af.mil:192.168.1.2:::in
      +jupiter.heaven.af.mil:1.2.3.4:::ex

  specifies that jupiter.heaven.af.mil has address 192.168.1.2 for 
clients in the 192.168.* network and address 1.2.3.4 for everyone else.

/Quote

Would it be possible to have
%in:192.168
%in:172.16
%ex
+jupiter.heaven.af.mil:192.168.1.2:::in
+jupiter.heaven.af.mil:1.1.1.1:::ex

As we have separate non-contiguous space for various offices that we 
have been assigned by our ISP's which we would like to segregate. Or 
does it need to be or for example if we have our dnscache server on 
2.2.2.2 3.3.3.3 and 4.4.4.4 could we do.

%in:2.2.2.2
%in:3.3.3.3
%in:4.4.4.4
%ex
+jupiter.heaven.af.mil:192.168.1.2:::in
+jupiter.heaven.af.mil:1.1.1.1:::ex

Regards,

Jimmy.