From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] dns vs. textrr
Date: Thu, 19 Jan 2012 12:17:10 -0500 [thread overview]
Message-ID: <9900fab97779679305fe3fceec64a38d@coraid.com> (raw)
In-Reply-To: <87B8E7AD-7956-4F2F-8F59-566651922EED@corpus-callosum.com>
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.
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.
ladd; ndb/query ipnet athensnat
ipnet=athensnat ip=192.168.0.0 ipmask=/120 fs=aska.quanstro.net ipgw=192.168.0.4 gw=dexter-peak.quanstro.net dns=192.168.0.136 dnsdomain=quanstro.net authdom=plan9.quanstro.net auth=ladd cpu=ladd smtp=ladd
ladd; ndb/ipquery sys ladd dns
dns=192.168.0.136
ladd; ndb/query sys ladd
ip=192.168.0.136 sys=ladd ether=001d92350045 dom=ladd.quanstro.net proto=il
- erik
ps. the limit is 214 characters in that particular textrr. one
would expect 256, evidently the difference is the meaning
of life.
next prev parent reply other threads:[~2012-01-19 17:17 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 [this message]
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
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=9900fab97779679305fe3fceec64a38d@coraid.com \
--to=quanstro@labs.coraid.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).