9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, lucio@proxima.alt.za
Subject: Re: [9fans] ndb and FQDNs.
Date: Mon, 26 Dec 2005 13:31:39 -0600	[thread overview]
Message-ID: <20051226193139.1886F1B1D67@dexter-peak.quanstro.net> (raw)
In-Reply-To: <8520d4545310b16f131a16385c8564bf@proxima.alt.za>

lucio@proxima.alt.za writes

| 
| > how do i enter things so the second query works? also,
| 
| 	dom=dexter-peak.quanstro.net
| 
| but the querry ought to be for "dom", not "sys".  I don't know if
| multiple "sys" entries would be logical or permissible.

clearly i misread the example. i should have had sys=dexter-peak dom=dexter-peak.quanstro.net


| 
| > how do i enter a multi-homed machine?
|
| Multiple "dom" entries?  Nothing that I'm aware of says that "sys" is
| a more significant key than "dom".

multi-homed as in a machine with addresses 192.168.0.1/16, 10.0.0.1/8
and fe80::240:f4ff:febf:3a75/64. for example in bind syntax:

dexter-peak.quanstro.net.	in a	192.168.0.1
			in a	10.0.0.1
			in aa	fe80::240:f4ff:febf:3a75/64

before posting i read the ndb(7) page and tried things like this:

ip=192.168.0.4 ip=10.0.0.1 sys=dexter-peak dom=dexter-peak.quanstro.net
	smtp=dexter-peak.quanstro.net
	mx=dexter-peak.quanstro.net

but ndbmkdb drops this on the floor.

| 
| Experimenting, of course, may be the way to figure some things out.
| But as I understand it, there are very few special treatments applied
| to NDB entries, all of them documented in ndb(6).
| 
| ++L


  reply	other threads:[~2005-12-26 19:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-26 17:32 erik, quanstrom <quanstro
2005-12-26 18:43 ` lucio
2005-12-26 19:31   ` erik quanstrom [this message]
2005-12-27  3:20 ` Russ Cox
2005-12-27  3:51   ` lucio
2005-12-27  4:02     ` erik quanstrom
2005-12-27  4:07       ` Russ Cox
2005-12-27  3:57   ` erik quanstrom

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=20051226193139.1886F1B1D67@dexter-peak.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@cse.psu.edu \
    --cc=lucio@proxima.alt.za \
    /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).