Re: [9fans] my plan9 server isn't responding

[Ezequiel Aragon <aragonezequiel@gmail.com>]

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

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

ip=10.0.0.2 ether=jhgsfs7sfs788 sys=akenaton dom=akenaton.amarna.net
ip=10.0.0.3 ether=jhgsfs45dfdff1 sys=nefertiti
dom=nefertiti.amarna.net

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

dom=amarna.net soa=
    refresh=3600 ttl=3600
    ns=10.0.0.2
    cname=akenaton.amarna.net dom=akenaton
    cname=nefertiti.amarna.net dom=nefertiti

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