From: Jeff Sickel <jas@corpus-callosum.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] dns vs. textrr
Date: Fri, 20 Jan 2012 00:31:33 -0600 [thread overview]
Message-ID: <83ADCC72-11CC-4E4B-89B6-619B6FEB7706@corpus-callosum.com> (raw)
In-Reply-To: <9900fab97779679305fe3fceec64a38d@coraid.com>
On Jan 19, 2012, at 11:17 AM, erik quanstrom wrote:
> On Thu Jan 19 12:08:37 EST 2012, jas@corpus-callosum.com wrote:
>> Haven't seen it. But it does seem that a lot of us
>> are having fun with dns this week (and every week).
>>
>> Mine's more the problem of
>>
>> ndb/dns -sx /net.alt -f /lib/ndb/external
>
> you probablly want -R too, so you ignore the RD flag
> on incoming queries.
not necessarily what I want, but I've tried that too.
>
> the key to getting plan 9 resolution working right is
> to have the proper ipnet configuration that has a
> proper netmask s.t. ndb/ipquery $sys dns gives a
> credible answer. e.g.
yep, I get clean sys, ip, etc resolves for nodes in my
/lib/ndb/external file. It's the next hop out that just
doesn't happen. No pointer to the next dns server to
do a lookup, e.g. sources.cs.bell-labs.com.
Turns out Presotto posted a little comment in 9fans years back
about adding root entries into an ndb file would solve it. It
works, now I can replica/pull and 9fs sources til the cows come
home from a cpu server that spans multiple networks.
So as a reminder:
ndb/dns -sx /net.alt -f /lib/ndb/external
will require the external file to have the ROOT-SERVERS.NET ns
entries defined even if you have the following:
database=
file=/lib/ndb/external
file=/lib/ndb/common
^just copy the *ROOT-SERVERS.NET lines from /lib/ndb/common into
the external file. It may just be more practical to copy
local.complicated to external and edit from there. Researching
the lack of the database reference to /lib/ndb/common is left
to the reader.
-jas
prev parent reply other threads:[~2012-01-20 6:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 16:01 erik quanstrom
2012-01-19 17:00 ` Jeff Sickel
2012-01-19 17:17 ` erik quanstrom
2012-01-19 22:12 ` erik quanstrom
2012-01-19 23:32 ` Lyndon Nerenberg
2012-01-19 23:56 ` erik quanstrom
2012-01-20 0:11 ` Lyndon Nerenberg
2012-01-20 0:14 ` erik quanstrom
2012-01-20 0:39 ` Lyndon Nerenberg
2012-01-20 6:31 ` Jeff Sickel [this message]
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=83ADCC72-11CC-4E4B-89B6-619B6FEB7706@corpus-callosum.com \
--to=jas@corpus-callosum.com \
--cc=9fans@9fans.net \
/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).