From: geoff@collyer.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ftpd
Date: Wed, 16 Jan 2002 15:22:55 -0800 [thread overview]
Message-ID: <20020116232532.66B2E19A57@mail.cse.psu.edu> (raw)
Actually, Plan 9 dns returns resource records of types A, MX and NS
only in random order. This is the relevant fragment from ndb/dn.c:
/* just randomize addresses and mx's */
for(x = rp; x; x = x->next)
if(x->type != Ta && x->type != Tmx && x->type != Tns)
return rp;
In particular, PTR records are returned in the order in which the dom=
clauses that they are generated from were read, if I remember it
right. This doesn't help much if you have DNS secondaries running
BIND, since they will randomise all RRs, but can sometimes be of help
locally.
next reply other threads:[~2002-01-16 23:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-16 23:22 geoff [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-17 3:24 presotto
2002-01-16 15:17 presotto
2002-01-16 15:17 presotto
2002-01-16 15:20 ` Boyd Roberts
2002-01-16 15:07 presotto
2002-01-16 15:08 ` Boyd Roberts
2002-01-16 14:21 presotto
2002-01-16 14:22 ` Boyd Roberts
2002-01-16 10:36 arisawa
2002-01-16 12:01 ` Boyd Roberts
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020116232532.66B2E19A57@mail.cse.psu.edu \
--to=geoff@collyer.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).