On 4/25/07, Steve Simon <[EMAIL PROTECTED]> 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

Reply via email to