From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom To: 9fans@cse.psu.edu, Russ Cox References: <20051226173259.3B5AC1B1D67@dexter-peak.quanstro.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 In-Reply-To: Subject: Re: [9fans] ndb and FQDNs. Message-Id: <20051227035740.ED8D41B1D6D@dexter-peak.quanstro.net> Date: Mon, 26 Dec 2005 21:57:40 -0600 Cc: Topicbox-Message-UUID: cb0a1afa-ead0-11e9-9d60-3106f5b1d025 Russ Cox writes | | > on a unix machine: | > ; host dexter-peak | > ; host dexter-peak.quanstro.net | > | > both return a value. | | because both look up dexter-peak.quanstro.net, | the first one only implicitly. i've worked for more than one registrar and more than one registry. please don't remind me how it works. ;-) | dom is for dns names. sys is for local system names | (yes there is life without dns). thanks. i've got that straight, now. | | > also, how do i enter a multi-homed machine? | | put in a second ip= attribute. didn't work for me. that's why i asked. ndb/mkdb drops the entry on the floor. i must be doing something wrong. here's what i had: ip=192.168.0.4 ip=192.168.0.1 sys=dexter-peak dom=dexter-peak.quanstro.net how should it be? | why are you using ndb on unix? besides plan9 envy, upas is pretty tight with ndb. (as are many other plan9 applications.) i thought that it'd be easier to port ndb than to completely rearrange upas. i was not planning on using ndb to store much data. just enough to get by and then have a magic word in the ndb database that does a call out to the host system's dns (or yp or whatever). - erik