From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@9fans.net
Date: Mon,  2 Apr 2012 14:22:25 +0000
From: Ezequiel Aragon <aragonezequiel@gmail.com>
Message-ID: <3177fc72-8c0d-4bd0-a7a1-e7e27fc861c8@12g2000vba.googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
References: <86596600-97f0-41dc-afa5-a29dc39481a6@b2g2000yqb.googlegroups.com>
Subject: Re: [9fans] my plan9 server isn't responding
Topicbox-Message-UUID: 7437d09e-ead7-11e9-9d60-3106f5b1d025


> there are two ways you can get a short name to work
> - use a sys=3Dxyz entry. =A0if you also want to use dns to
> reach this node it would be conventional to have sys=3Dxyz dom=3Dxyz.dom.

That was the first thing I did. My tipical entry en ndb looks like:

ip=3D10.0.0.2 ether=3Djhgsfs7sfs788 sys=3Dakenaton dom=3Dakenaton.amarna.ne=
t
ip=3D10.0.0.3 ether=3Djhgsfs45dfdff1 sys=3Dnefertiti
dom=3Dnefertiti.amarna.net

And still doesn;t work for short names.
I even tried something like:

dom=3Damarna.net soa=3D
    refresh=3D3600 ttl=3D3600
    ns=3D10.0.0.2
    cname=3Dakenaton.amarna.net dom=3Dakenaton
    cname=3Dnefertiti.amarna.net dom=3Dnefertiti

To see if using an alias (cname) in the dom info solved the case, but
there is no way the server can solve short names for the terminal

I tried at the terminal:

ndb/dnsquery
> akenaton
!dns: resource does not exist; negrcode 0
> akenaton.amarna.net
akenaton.amarna.net ip 10.0.0.2

See? It seems everything is well configured, but still no short name
resolution.
What puzzles me more is, the same dnsquery used at the server give
identical good results for both the short and large names:

ndb/dnsquery
> akenaton
akenaton.amarna.net ip 10.0.0.2
> akenaton.amarna.net
akenaton.amarna.net ip 10.0.0.2