> The applicable line in /rc/term/termrc is
> ip/ipconfig -g 199.98.16.1 ether /net/ether0 199.98.17.238
> 255.255.248.0 > /dev/null >[2=1]
>
> It looks like something's misconfigured -- but this configuration
> *used* to work!
you're not totally lost.
you need to check whether you have any
connectivity at all.
ip/ping 199.98.16.1 # your gateway
ip/ping 199.98.16.9 # your dns server
ip/ping 18.26.4.9 # somewhere on the internet
then see if you can resolve something
using your dns server:
ndb/dnsdebug @199.98.16.9 www.google.com
or someone else's dns server:
ndb/dnsdebug @18.26.4.9 www.google.com
also, this part of your mail looks wrong:
term% ndb/dnsdebug
> www.google.com
!dns: dns failure
dnsdebug doesn't print lines like !dns: dns failure.
only dnsquery does. are you sure you didn't
run dnsquery twice?
dnsdebug prints things like the output below.
even if nothing is working you should get the
'sending to' line.
(the fact that you are typing into the interactive
prompt instead of specifying it on the command
line like in my example is not relevant.)
russ
% ndb/dnsdebug @18.26.4.9 plan9.bell-labs.com
20654.1: sending to 18.26.4.9/18.26.4.9 plan9.bell-labs.com ip
20654: rcvd OK from 18.26.4.9 ( recurse can_recurse)
Q: plan9.bell-labs.com ip
Ans: plan9.bell-labs.com 12 hr ip
204.178.31.2
Auth: bell-labs.com 11 hr 1 min 2 s ns
dirty.research.bell-labs.com
bell-labs.com 11 hr 1 min 2 s ns
crufty.research.bell-labs.com
bell-labs.com 11 hr 1 min 2 s ns
ns1.research.bell-labs.com
bell-labs.com 11 hr 1 min 2 s ns
ns2.research.bell-labs.com
Hint: ns1.research.bell-labs.com 4 hr 27 min 28 ip
204.178.16.6
ns2.research.bell-labs.com 1 hr 16 min 11 ip
204.178.16.49
dirty.research.bell-labs.com 1 hr 16 min 11 ip
204.178.16.6
crufty.research.bell-labs.com 11 hr 1 min 2 s ip
204.178.16.49
----------------------------
answer plan9.bell-labs.com 12 hr ip 204.178.31.2
----------------------------
%
