On Apr 2, 6:58 am, 9f...@hamnavoe.com (Richard Miller) wrote: > > I then tried the line: > > > dnsdomain=amarna.net > > > in my terminal's ndb file, but it keeps failing with unqualified > > names. > > You need something more like this: > > ipnet=localnet ip=10.0.0.0 ipmask=255.255.255.0 > dnsdomain=amarna.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=ezequiel 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=nefertiti dom=nefertiti.amarna.net fs=10.0.0.2 auth=10.0.0.2 dns=10.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?
