From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <7871fcf50704261307w712a94d9pa03f10dd7c973596@mail.gmail.com>
Date: Thu, 26 Apr 2007 16:07:25 -0400
From: "Joel C. Salomon" <joelcsalomon@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] dns suddenly not working
In-Reply-To: <74ba48199efecc4ea821f3efb033187a@plan9.bell-labs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <7871fcf50704261209p605e576ud46510b3ca108742@mail.gmail.com>
	<74ba48199efecc4ea821f3efb033187a@plan9.bell-labs.com>
Topicbox-Message-UUID: 4fbebe58-ead2-11e9-9d60-3106f5b1d025

On 4/26/07, geoff@plan9.bell-labs.com <geoff@plan9.bell-labs.com> wrote:
> For a few days, ipconfig needed an explicit verb, like this:
>         ip/ipconfig -g 199.98.16.1 ether /net/ether0 add 199.98.17.238 255.255.248.0

Nope, that doesn't fix anything.

Is there some way to invoke ndb/dns so it tells me more than "can't
find my ip address"?

--Joel