Re: [9fans] dns suddenly not working

Re: [9fans] dns suddenly not working

[Joel C. Salomon]

On 4/25/07, erik quanstrom <quanstro@coraid.com> wrote:
> you may still have _ipconfig around.  this may get you far enough
> to get the new ipconfig.

I reverted both ip/ipconfig and ndb/dns; now I get
	ndb/dns: can't read my ip address
at bootup, and ndb/dnsquery complains
	can't open /srv/dns: '/srv/dns' file does not exist
I suppose that's progress, of a sort.

--Joel

Re: [9fans] dns suddenly not working

[geoff]

Do you have your machine's ip and ether addresses in ndb?  E.g.,

ip=199.98.17.238 sys=laptop dom=laptop.cooper.edu
	ether=00d037abcdef
	bootf=/386/9pcf

Lack of this is the usual reason that dns can't figure out its IP
address.

Re: [9fans] dns suddenly not working

[Steve Simon]

not sure I really understand the problem but it looks as though
you didn't get a dns= record in /net/ndb (with the new ipconfig).
If this is all it is then you should be able to just do:

	echo '	dns=1.2.3.4' >> /net/ndb

where 1.2.3.4 is your DNS server's address.
I am pretty sure this will work, though I haven't
tried it since the days I used ppp and dialup...

you will also need to get dns to reread its config:

	echo refresh > /net/dns

----------

You could also check that ip/cs is able to
find a dns server for your machine:

	ndb/ipquery sys $sysname dns

and try repeating this using

	ndb/ipquery ip 1.2.3.4 dns

where 1.2.3.4 is your IP address

-Steve

Re: [9fans] dns suddenly not working

[Joel C. Salomon]

On 4/25/07, Steve Simon <steve@quintile.net> wrote:
> not sure I really understand the problem but it looks as though
> you didn't get a dns= record in /net/ndb (with the new ipconfig).

Actually, as maters stand now, when /rc/bin/termrc calls ndb/dns -rf
$NDBFILE, I get the message
	ndb/dns: can't read my ip address
My /lib/ndb/local (which $NDBFILE properly resolves to) includes the
following lines:
	…
	ip=199.98.17.238 sys=hymie dom=hymie.cc.cooper.edu
		ether=00d0…
		dns=paperweight dnsdom=paperweight.cooper.edu
		…
	ip=199.98.16.9 sys=paperweight dom=paperweight.cooper.edu
	…
I've checked with the school network administrators; the dns server is
paperweight.cooper.edu at an ip address of 199.98.16.9, and thins
invocation kept dns happy until this week.

What should I change those lines to?

Side question:  In general, do I use
	sys=name dom=name.dom.org
or
	sys=name dom=dom.org
to make dns recognize the enry correctly?

> You could also check that ip/cs is able to
> find a dns server for your machine:
>         ndb/ipquery sys $sysname dns
> and try repeating this using
>         ndb/ipquery ip 1.2.3.4 dns
> where 1.2.3.4 is your IP address

In both cases I get
	dns=paperweight
-- is that what it should read?

--Joel

Re: [9fans] dns suddenly not working

[geoff]

You want

	sys=hymie dom=hymie.cc.cooper.edu

dom is the FQDN of sys.

What's the output of

	cat /net/ether0/addr
	echo
	ndb/query sys $sysname

?  Are you starting dns after running ipconfig?

Re: [9fans] dns suddenly not working

[Joel C. Salomon]

On 4/26/07, geoff@plan9.bell-labs.com <geoff@plan9.bell-labs.com> wrote:
> You want
>         sys=hymie dom=hymie.cc.cooper.edu
> dom is the FQDN of sys.

Thanks.

> What's the output of
	term% cat /net/ether0/addr
	00d059ca4e8eterm%
-- same as in the ether= line in /lib/ndb.local, and is correct for my
network card.

>         ndb/query sys $sysname
	term% ndb/query sys $sysname
	ip=199.98.17.238 sys=hymie dom=hymie.cc.cooper.edu ether=00d059ca4e8e
dns=paperweight dnsdom=paperweight.cooper.edu ntp=ntp.cooper.edu
ipmask=255.255.248.0 ipgw=199.98.16.1
	term% ndb/query sys paperweight
	ip=199.98.16.9 sys=paperweight dom=paperweight.cooper.edu

> ?  Are you starting dns after running ipconfig?

That's the way it is in /rc/bin/termrc; I uncommented the ipconfig
line and edited it to read:
	ip/ipconfig -g 199.98.16.1 ether /net/ether0 199.98.17.238 255.255.248.0 >…
Is that right?

--Joel

Re: [9fans] dns suddenly not working

[Joel C. Salomon]

On 4/26/07, Joel C. Salomon <joelcsalomon@gmail.com> wrote:
> My /lib/ndb/local includes the following lines:
>         …
>         ip=199.98.17.238 sys=hymie dom=hymie.cc.cooper.edu
>                 ether=00d000d059ca4e8e
>                 dns=paperweight dnsdom=paperweight.cooper.edu
>                 ntp=ntp.cooper.edu
>                 ipmask=255.255.248.0 ipgw=199.98.16.1
>
>         ip=199.98.16.9 sys=paperweight dom=paperweight.cooper.edu
>         …

Should I be using paperweight's IP address when referring to it in
hymie's entry?

--Joel

Re: [9fans] dns suddenly not working

[Russ Cox]

> Should I be using paperweight's IP address when referring to it in
> hymie's entry?

no need

russ

Re: [9fans] dns suddenly not working

[geoff]

	ip/ipconfig -g 199.98.16.1 ether /net/ether0 199.98.17.238 255.255.248.0 >…

That should be fine as long as you're running the latest ipconfig or
an old one.  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

Re: [9fans] dns suddenly not working

[Joel C. Salomon]

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

Re: [9fans] dns suddenly not working

[geoff]

myipaddr() calls readipifc(), so "cat /net/ipifc0/?/status" might be
revealing, particularly if you put it in termrc just before starting dns.