From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@9fans.net
Date: Mon,  2 Apr 2012 13:15:04 +0000
From: Ezequiel Aragon <aragonezequiel@gmail.com>
Message-ID: <75e042ae-ab8a-4655-9a2d-e2a2568eadf3@do6g2000vbb.googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
References: <86596600-97f0-41dc-afa5-a29dc39481a6@b2g2000yqb.googlegroups.com>,
	<8ccf8f24c36f679c176387a685bc17a8@hamnavoe.com>
Subject: Re: [9fans] my plan9 server isn't responding
Topicbox-Message-UUID: 74190a1a-ead7-11e9-9d60-3106f5b1d025

On Apr 2, 6:58=A0am, 9f...@hamnavoe.com (Richard Miller) wrote:
> > I then tried the line:
>
> > dnsdomain=3Damarna.net
>
> > in my terminal's ndb file, but it keeps failing with unqualified
> > names.
>
> You need something more like this:
>
> ipnet=3Dlocalnet ip=3D10.0.0.0 ipmask=3D255.255.255.0
> =A0 =A0 =A0 =A0 dnsdomain=3Damarna.net
>
> > By the way, I am trying to connect as ezequiel with 9fs (the user
> > exists in the server) though I am logged as glenda in the terminal.
>
> I expect you have a p9sk1 password for user=3Dezequiel in your factotum
> on the terminal.

I do have a p9sk1 key.

I think I have isolated the problem.
I configured my server ndb file with auth and fs using the server
fully qualified name.
As a result, now, my terminal ndb info looks more promising:

cat /net/ndb
  sys=3Dnefertiti
  dom=3Dnefertiti.amarna.net
  fs=3D10.0.0.2
  auth=3D10.0.0.2
  dns=3D10.0.0.2

But I can't yet connect to my server using 9fs, I try:

9fs akenaton.amarna.net

And it fails, I then look for debug info and notice the error:

net!akenaton!ticket      dns can't find this

of course, dns can not find akenaton alone. I try some test with cs:

ndb/csquery
> net!akenaton!ticket
   and it give the same error, so cs can't get the info from the 'url'
as dns fails
I then try:

> net!akenaton.amarna.net!ticket
or
> net!akenaton.amarna.net!9fs

And I get proper answers with these.

Why is cs using akenaton instead of akenaton.amarna.net, if I don't
have akenaton alone defined anywhere in the server ndb?
Is there a way to cope with this or to configure dns to solve
unqualified names somehow?