<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.network.djbdns">
    <title>gmane.network.djbdns</title>
    <link>http://blog.gmane.org/gmane.network.djbdns</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.djbdns/14978"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.djbdns/14970"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.djbdns/14960"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.djbdns/14959"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.djbdns/14952"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.djbdns/14944"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.djbdns/14944"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.djbdns/14932"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.djbdns/14921"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.djbdns/14919"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.djbdns/14917"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.djbdns/14900"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.djbdns/14893"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.djbdns/14885"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.djbdns/14880"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.djbdns/14876"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.djbdns/14873"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.djbdns/14871"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.djbdns/14870"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.djbdns/14854"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.network.djbdns/14978">
    <title>General amusement (nothing to do with TBP DHP nameservice or  dead Wikileaks.org)</title>
    <link>http://comments.gmane.org/gmane.network.djbdns/14978</link>
    <description>&lt;pre&gt;--
Richard J. Sexton  rich4&amp;lt; at &amp;gt;rd.vrx.net  +1 (206) 333-1798 skype: rsx11s
http://rs79.vrx.net http://mbz.org http://killi.net http://aquaria.net

&lt;/pre&gt;</description>
    <dc:creator>Richard J. Sexton</dc:creator>
    <dc:date>2010-12-03T07:41:09</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.djbdns/14970">
    <title>Very long delays, is it just djbdns?</title>
    <link>http://comments.gmane.org/gmane.network.djbdns/14970</link>
    <description>&lt;pre&gt;Try this command from a nice, clean dnscache:
host -v 2001:470:1f09:103e::2354

It took me three tries on my fastest, most well-connected machine to get the NXDOMAIN response.  I haven't got to the bottom of it yet, but if anybody has a clue, please do share!

Cheers,
Sabahattin

&lt;/pre&gt;</description>
    <dc:creator>Sabahattin Gucukoglu</dc:creator>
    <dc:date>2010-11-13T07:19:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.djbdns/14960">
    <title>Wildcards not supported in &amp; records?</title>
    <link>http://comments.gmane.org/gmane.network.djbdns/14960</link>
    <description>&lt;pre&gt;Was trying to delegate the first of several /24's worth
of in-addr.arpa records to a customer's name servers,
some of which are present on said /24 and some not, so
I did the following (first three octets and the domain
name changed obviously):

&amp;amp;*.3.2.1.in-addr.arpa:1.2.3.4:ns1.customerdns.com:3600
&amp;amp;*.3.2.1.in-addr.arpa:3.4.5.32:ns2.customerdns.com:3600
&amp;amp;*.3.2.1.in-addr.arpa:3.4.5.31:ns1.customerdns.net:3600
&amp;amp;*.3.2.1.in-addr.arpa:1.2.3.254:ns2.customerdns.net:3600

Did not get successful ptr lookups after putting that in
place, just get an SOA response from our dns showing our
dns.  I changed the records to test just one IP:

&amp;amp;50.3.2.1.in-addr.arpa:1.2.3.4:ns1.customerdns.com:3600
&amp;amp;50.3.2.1.in-addr.arpa:3.4.5.32:ns2.customerdns.com:3600
&amp;amp;50.3.2.1.in-addr.arpa:3.4.5.31:ns1.customerdns.net:3600
&amp;amp;50.3.2.1.in-addr.arpa:1.2.3.254:ns2.customerdns.net:3600

Now it's happy.  Querying for 50.3.2.1.in-addr.arpa on
my tinydns gives back four NS authority records of the
customer's DNS servers.  If I do a straight root &lt;/pre&gt;</description>
    <dc:creator>David Hubbard</dc:creator>
    <dc:date>2010-11-02T17:12:52</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.djbdns/14959">
    <title>IPv6 readiness and tinydns.</title>
    <link>http://comments.gmane.org/gmane.network.djbdns/14959</link>
    <description>&lt;pre&gt;I am attempting to prepare our infrastructure here to be IPv6 ready.
Part of that is DNS. For several years we have used the fefe.de patch to
serve up AAAA records for several sub-domains. In the documentation it
states explicitly that:

    .... tinydns-edit won't accept IPv6 addresses for NS or MX records yet

So my short question is, can one use a patched version of tinydns to fulling
support an IPv6 environment?

&amp;lt;snip&amp;gt;
On 2008-01-12 Russ Nelson wrote:

   "When Google has an AAAA record, we can talk about adding IPv6 support."

I think we are ready to start talking:

   http://www.google.com/intl/en/ipv6/faq.html
&amp;lt;/snip&amp;gt;

&lt;/pre&gt;</description>
    <dc:creator>Russell Sutherland</dc:creator>
    <dc:date>2010-11-02T15:34:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.djbdns/14952">
    <title>curvedns.net/org : For your interest, or not as the case may be</title>
    <link>http://comments.gmane.org/gmane.network.djbdns/14952</link>
    <description>&lt;pre&gt;Greets,

   http://curvedns.net

   http://curvedns.org

I've taken the trouble to rescue the above two domains before the
search engine guys
take them;  the main idea being to use them as a focal point for
referencing anything
specifically related to DNSCurve.

By putting people with similar goals in touch with one another,  and
having specific
reference points for all efforts, may go some way to
offsetting/reversing the current
imbalance between DNSCurve and DNSEC.  Has to be worth a try, especially since
I am aware of several few people working on, intending to work on, or
in the process
of working on DNSCurve related material.  I along with a few others,
also have some
DNSCurve enabled servers/caches/forwarders imnplemented  working.

Accordingly, I am open to further suggestion and input from any
interested parties as
to appropriate usage of the above two domains.  What would you wish to
see there?
An editable wiki maybe, for example mediawiki, ikiwiki, or similar?
Domains split into
subdomains per proj&lt;/pre&gt;</description>
    <dc:creator>Chris Pugh</dc:creator>
    <dc:date>2010-10-25T09:09:37</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.djbdns/14944">
    <title>Introducing CurveDNS a DNSCurve forwarding name server</title>
    <link>http://comments.gmane.org/gmane.network.djbdns/14944</link>
    <description>&lt;pre&gt;Hello people,

/Not really the appropriate list but I think not much people will
object, since it is quite related to djbdns./

We are happy to announce the first forwarding DNSCurve solution: CurveDNS.

With CurveDNS you are able to transform any authoritative name server in
a DNSCurve capable one. This is done by acting as a kind of proxy, i.e.
listening to DNS or DNSCurve queries and forwarding the non-protected
variants towards the real (existing) name server. The responses are then
send back to the client either protected (if the query was in DNSCurve)
or not.

In short, CurveDNS supports:
* Forwarding of regular (non-protected) DNS packets;
* Unboxing of DNSCurve queries and forwarding the regular DNS packets
* Boxing of regular DNS responses to DNSCurve responses;
* Both DNSCurve's streamlined- and TXT-format;
* Caching of shared secrets;
* Both UDP and TCP;
* Both IPv4 and IPv6.

This entire project is based on a master thesis named 'Shaping DNS
Security with Curves — A Comparative Security Analysi&lt;/pre&gt;</description>
    <dc:creator>Harm van Tilborg</dc:creator>
    <dc:date>2010-10-23T18:14:13</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.djbdns/14944">
    <title>Introducing CurveDNS a DNSCurve forwarding name server</title>
    <link>http://comments.gmane.org/gmane.network.djbdns/14944</link>
    <description>&lt;pre&gt;Hello people,

/Not really the appropriate list but I think not much people will
object, since it is quite related to djbdns./

We are happy to announce the first forwarding DNSCurve solution: CurveDNS.

With CurveDNS you are able to transform any authoritative name server in
a DNSCurve capable one. This is done by acting as a kind of proxy, i.e.
listening to DNS or DNSCurve queries and forwarding the non-protected
variants towards the real (existing) name server. The responses are then
send back to the client either protected (if the query was in DNSCurve)
or not.

In short, CurveDNS supports:
* Forwarding of regular (non-protected) DNS packets;
* Unboxing of DNSCurve queries and forwarding the regular DNS packets
* Boxing of regular DNS responses to DNSCurve responses;
* Both DNSCurve's streamlined- and TXT-format;
* Caching of shared secrets;
* Both UDP and TCP;
* Both IPv4 and IPv6.

This entire project is based on a master thesis named 'Shaping DNS
Security with Curves — A Comparative Security Analysi&lt;/pre&gt;</description>
    <dc:creator>Harm van Tilborg</dc:creator>
    <dc:date>2010-10-23T18:14:13</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.djbdns/14932">
    <title>djbdns/dnscache epoll patch, qmerge and dnscurve included</title>
    <link>http://comments.gmane.org/gmane.network.djbdns/14932</link>
    <description>&lt;pre&gt;
OK, my ISP decided to block ports 1-1023 without prior warning..
http://safari.iki.fi:8765/patches/djbdns/djbdns-1.05-epoll-20101011192500Z-mergequeries-dnscurve.diff
http://safari.iki.fi:8765/patches/djbdns/djbdns-1.05-epoll-20101011192500Z-mergequeries-dnscurve.diff.sig
That's why I have this kind of funny port numbers.

In this version, the qmerge feature is O(1) instead of O(MAXUDP), though.
qmerge is not enabled for dnscurve queries—I haven't thought yet would
it be easy to support.
A different approach was needed for qmerge support with epoll,
because for epoll_wait the fd's were not returned for merged queries.
If someone wants the O(1) version for non-epoll dnscache, it
should be easy to port.

BTW. what's currently the best option for dnscurve server?
Are there other than git://github.com/agl/dnscurve.git ?
Would there be need for dnscurve support for tinydns?
Or specifying (hard-coding) keys in dnscache root/servers files?
Or any other extra features in dnscache?

&lt;/pre&gt;</description>
    <dc:creator>Sami Farin</dc:creator>
    <dc:date>2010-10-12T18:42:42</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.djbdns/14921">
    <title>Beating an Old Horse, but....</title>
    <link>http://comments.gmane.org/gmane.network.djbdns/14921</link>
    <description>&lt;pre&gt;Hello,

Does anyone know of any existing branches / work being done for DNSCache
to support DNSSEC validation?

-brian

&lt;/pre&gt;</description>
    <dc:creator>Brian</dc:creator>
    <dc:date>2010-10-04T18:46:22</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.djbdns/14919">
    <title>EDNS0 for djbdns?</title>
    <link>http://comments.gmane.org/gmane.network.djbdns/14919</link>
    <description>&lt;pre&gt;Has anyone modified tinydns or dnscache to support EDNS0?  I know all
the reasons it is in principle a bad idea, but these days every other
DNS package supports it, and DNS packet sizes are getting bigger.  A
few months ago I modified one of my special purpose DNS servers (the
one that runs abuse.net) to handle it, and I have to say I've seen no
operational problems at all.

I doubt that it would be a huge amount of code, but I'd just as soon
not write it if somebody else has already done so.

R's,
John

&lt;/pre&gt;</description>
    <dc:creator>John Levine</dc:creator>
    <dc:date>2010-09-26T05:08:46</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.djbdns/14917">
    <title>ipv6 walldns</title>
    <link>http://comments.gmane.org/gmane.network.djbdns/14917</link>
    <description>&lt;pre&gt;Has anyone patched walldns to function with ipv6?

The only patches for ipv6 I can find are these from Felix von Leitner.
But these patches only provide AAAA and PTR records. Are there any
other ipv6 patches for djbdns?

R.

&lt;/pre&gt;</description>
    <dc:creator>richard lucassen</dc:creator>
    <dc:date>2010-09-25T10:33:09</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.djbdns/14900">
    <title>dnscache problems</title>
    <link>http://comments.gmane.org/gmane.network.djbdns/14900</link>
    <description>&lt;pre&gt;hello list,

I get more and more problems using dnscache. I've already started a
thread a few months ago about this issue, and until now I entered the
missing queries to an instance of tinydns, but it seems that this
problem is growing:

dnsqr mx newcastle.edu.au
15 newcastle.edu.au:
timed out

dnsqr mx deloitte.com.au
15 deloitte.com.au:
timed out

While other nameservers give me an answer:

host -t mx deloitte.com.au ns2.kpn.net
Using domain server:
Name: ns2.kpn.net
Address: 194.151.228.58#53
Aliases: 

deloitte.com.au mail is handled by 200 deloitte.com.au.s7a2.psmtp.com.
deloitte.com.au mail is handled by 300 deloitte.com.au.s7b1.psmtp.com.
deloitte.com.au mail is handled by 400 deloitte.com.au.s7b2.psmtp.com.
deloitte.com.au mail is handled by 100 deloitte.com.au.s7a1.psmtp.com.

I know it's apparently not a dnscache fault, but the problem is rather
annoying. Customers are complaining and they do not accept that they
have to use gmail or other ways to contact these domains. I think I'm
not the only one&lt;/pre&gt;</description>
    <dc:creator>richard lucassen</dc:creator>
    <dc:date>2010-09-22T07:55:10</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.djbdns/14893">
    <title>Failure of secondaries</title>
    <link>http://comments.gmane.org/gmane.network.djbdns/14893</link>
    <description>&lt;pre&gt;Hello,

I am trying understand a predicament I found myself in today. As background,
my environment is that I work for a small web hosting company. We handle the
authoritative DNS for most of our clients, using djbdns/tinydns. So we have
ns1, ns2, and ns3 type setup. data.cdb is shared among the 3 when the
Makefile is executed so that everything stays in sync. This is a
non-clustered set up, with one ip address per server.

This has seemed to work flawlessly for years now. Last night though someone
inadvertantly disconnected the wrong server, and unplugged the ns1 system.
The eventual impact of that one mistake was that the dns for the hosted
domains all went down totally. The ns2 and n3 systems were never queried.
Direct querying during testing showed they were responding normally (eg dig
blah.com &amp;lt; at &amp;gt;ns2).  Yet, for all practical purposes they might as well been
unplugged too since they were totally quiet. I had been under the false
assumption that should ns1 go down, that the others would automatically come
&lt;/pre&gt;</description>
    <dc:creator>Hal Burgiss</dc:creator>
    <dc:date>2010-09-11T19:44:16</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.djbdns/14885">
    <title>dnscache memory requirements for large number of server files</title>
    <link>http://comments.gmane.org/gmane.network.djbdns/14885</link>
    <description>&lt;pre&gt;Please help me estimate memory requirements to run dnscache with about 769,000 files in the "servers" directory (/etc/service/dncache/root/servers).

Each file has 9 bytes.  The filenames are the domain names to forward to an "override" nameserver (tinydns running on 127.0.0.2).  Each file contains the same content: the IP 127.0.0.2.  (Actually, the files are mostly hardlinks.  Otherwise I would run out of inodes.)

This is part of a project to set up porn-blocking using a list of 769,000 porn domain names.  dnscache should forward dns queries for the porn domains to tinydns, running on 127.0.0.2 on the same machine.  tinydns should return a bogus IP (to a page saying access to the pornography has been blocked).  Of course, I got this working on a few test domains before attempting to load the 769,000 servers entries.

I already loaded the 769,000 (minimal) zones into the tinydns data file, and ran "make."  tinydns seems to be fine (with zero queries).

However, dnscache cannot load the 769.000 servers files&lt;/pre&gt;</description>
    <dc:creator>Lloyd Standish</dc:creator>
    <dc:date>2010-09-07T06:38:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.djbdns/14880">
    <title>dnsrbl.c</title>
    <link>http://comments.gmane.org/gmane.network.djbdns/14880</link>
    <description>&lt;pre&gt;I wrote next for me.  I use ir to test if IP(s) is in RBL list.
Maybe it is useful for some people

Enjoy, Nikola


-------------------------------------------------------
/* dnsrbl.c
   save me under dnstxt.c in djbdns-1.05 and recompile.
   then: mv dnstxt dnsrbl
   or
   diet -Os gcc -Wall -W -DUSE_LIBOWFAT -s -o dnsrbl dnsrbl.c -lowfat

   author: Nikola Vladov
   http://riemann.fmi.uni-sofia.bg/programs/
   See some examples at the end of this file!
*/

#define MAX_RBL_CONNECTIONS10
#define RBLSERVERS \
"sbl.spamhaus.org\n" \
"xbl.spamhaus.org\n" \
"zen.spamhaus.org\n" \
"dnsbl.njabl.org\n" \
"bl.spamcop.net\n" \
"cbl.abuseat.org\n" \
"spam.dnsbl.sorbs.net"

#include "dns.h"
#include "fmt.h"
#include "scan.h"
#include "byte.h"
#include "openreadclose.h"
#include "buffer.h"
#include &amp;lt;alloca.h&amp;gt;

extern int close(int);
extern void _exit(int);

#ifndef USE_LIBOWFAT
#include "strerr.h"
#include "env.h"
char buf_1sp[128];
buffer buf_rbl = BUFFER_INIT(buffer_unixwrite,1,buf_1sp,sizeof(buf_1sp));
#defin&lt;/pre&gt;</description>
    <dc:creator>Nikola Vladov</dc:creator>
    <dc:date>2010-08-19T09:55:29</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.djbdns/14876">
    <title>named zone files to tinydns data</title>
    <link>http://comments.gmane.org/gmane.network.djbdns/14876</link>
    <description>&lt;pre&gt;Hi All -

I'm looking for a script to convert a hellish set of bind zones to
a tinydns data file.

Anyone have an offering or suggestion?

George


&lt;/pre&gt;</description>
    <dc:creator>George Georgalis</dc:creator>
    <dc:date>2010-08-12T03:32:53</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.djbdns/14873">
    <title>hyatt.com spf record and dnscache</title>
    <link>http://comments.gmane.org/gmane.network.djbdns/14873</link>
    <description>&lt;pre&gt;So hyatt.com is serving a huge spf record:

"v=spf1 ip4:140.95.0.0/16 ip4:216.251.252.0/24 ip4:207.211.78.0/24
ip4:216.251.231.0/24 ip4:205.220.108.202 " "ip4:12.129.20.0/24
ip4:12.129.199.61 ip4:12.129.219.155 ip4:63.241.222.0/24
ip4:65.55.88.0/24 ip4:206.16.57.70 ip4:207.46.51.64/26
ip4:207.46.163.0/24 ip4:213.199.154.0/24 ip4:213.244.175.0/24
ip4:216.32.180.0/24 ip4:216.32.181.0/24 a mx ~all"

I'm troubleshooting an issue with a customer being
unable to receive email from hyatt.com; our servers
require either a SPF lookup &amp;amp; match or an SPF lookup
failure on an incoming mail domain to accept the
message, and in this case the dns query times out
with no response, causing the message to be deferred.

hyatt.com's name servers are:

authority: hyatt.com 2385 NS nameserver1.concentric.net
authority: hyatt.com 2385 NS nameserver2.concentric.net
authority: hyatt.com 2385 NS nameserver3.concentric.net
authority: hyatt.com 2385 NS nameserver.concentric.net

But I cannot successfully query any of them using dnsq,
it&lt;/pre&gt;</description>
    <dc:creator>David Hubbard</dc:creator>
    <dc:date>2010-07-28T16:44:20</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.djbdns/14871">
    <title>Dyn's wacky new marketing</title>
    <link>http://comments.gmane.org/gmane.network.djbdns/14871</link>
    <description>&lt;pre&gt;http://dyn.com/dns-is-sexy

&lt;/pre&gt;</description>
    <dc:creator>David Nicol</dc:creator>
    <dc:date>2010-07-27T15:15:29</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.djbdns/14870">
    <title>Bonjour Printing and DNS-SD records</title>
    <link>http://comments.gmane.org/gmane.network.djbdns/14870</link>
    <description>&lt;pre&gt;Hello list,

Some time ago I posted to the list with the subject "unescaped double 
quotes in TXT record".
Just to let know that i cooked up a small perl script the other day to 
create such tinydns records. I shamelessly borrowed code from Anders 
Brownworth's buildRecord.cgi script.

There's a strong probability that it contains bugs, but for the use i 
gave it, it worked.

I should only notice that sometimes specifying the Product attribute 
present in the PPD file doesn't work. However, following the Bonjour 
Printing specification, if you choose to use the generic MFG+MDL 
(manufacturer + model) records, it should work flawlessly.

Attached goes the script. Bug reports, suggestions, etc are welcomed.

Regards,

Hugo Monteiro.

&lt;/pre&gt;</description>
    <dc:creator>Hugo Monteiro</dc:creator>
    <dc:date>2010-07-26T16:42:53</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.djbdns/14854">
    <title>testing record start/end times with tinydns-get?</title>
    <link>http://comments.gmane.org/gmane.network.djbdns/14854</link>
    <description>&lt;pre&gt;Hi, all,

I need to set up some moderately complex record-switching magic using the
ttl/timestamp fields of the data file to cause some records to change at a
particular time.  I've got the datafile changes written and tinydns-data
compiles them.

But how do I test my magic?  tinydns-data will happily query the cdb file, but
I don't see how to tell it what time to to use (so it gets the proper records
and I can test times other than "now") - is this possible?

Thanks,

Charles
&lt;/pre&gt;</description>
    <dc:creator>Charles Cazabon</dc:creator>
    <dc:date>2010-07-21T20:49:51</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.djbdns/14853">
    <title>/etc/dnsrewrite usage poll</title>
    <link>http://comments.gmane.org/gmane.network.djbdns/14853</link>
    <description>&lt;pre&gt; Hello,

 djbdns implements an elaborate qualification mechanism, described at
&amp;lt;URL: http://cr.yp.to/djbdns/qualify.html &amp;gt;, using a djbdns-specific
file named /etc/dnsrewrite (or another file named in the DNSREWRITE
environment variable).

 Given the complexity of the stuff, and the wide usage of the "standard"
alternative (simply using 'domain' and 'search' lines in /etc/resolv.conf
to get an elementary qualification mechanism), my first reaction as a
programmer is "It's too complex for what it does".

 But I'm not using DNS heavily enough to need the /etc/dnsrewrite features,
and DJB rarely forfeits simplicity without a good reason.
 So, I would like to know, from users' viewpoints, how useful this really is.

 If you, as an administrator (or programmer) who uses djbdns, have use
for the /etc/dnsrewrite qualification mechanism, please post (or e-mail
me if you don't want it to be public for any reason):
 - what are you using /etc/dnsrewrite for ?
 - what does it allow you to accomplish that basic /etc/reso&lt;/pre&gt;</description>
    <dc:creator>Laurent Bercot</dc:creator>
    <dc:date>2010-07-19T11:38:10</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.network.djbdns">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.network.djbdns</link>
  </textinput>
</rdf:RDF>
