kmself@ix.netcom.com writes: > on Wed, Nov 29, 2000 at 10:54:37PM -0500, Giulio Morgan ([EMAIL PROTECTED]) > wrote: > > After upgrading, I am unable to connect to mailserver with fetchmail, to > > remore > > hosts with apt, telnet, ssh, irc, lynx or mozilla. Messages are: > > unable to resolve host... > > something wicked happened... > > domain name could not be confirmed... > > it appears that there is a problem with DNS and I have no idea how to > > resolve > > it. > > Is your named daemon running? I've found that several daemons fail to > restart after upgrades. DNS resolution tends to be poor without a > running named....
Thank you Karsten, I can't determine if my "named" is running. I checked logs to see if I could find any meaningful indication, and comparing pre- and post-upgrade logs, I noted that in the post-upgrade syslog, there is an entry: ...inetd[1731]: smtp/tcp: bind: Address already in use which does not appear in my pre-upgrade logs In the ppp.log, there is a line: ...ppd[324]: not replacing existing default route to tap0 [0.0.0.0] and then further down, after immediately after connection is established, the following lines appear: ...ppd[324]: local address... ...ppd[324]: remote address 198.6.71.8 (correct address, line not copied verbatim) ...ppd[324]: script /etc/ppp/ip-up started up to here, everything as before, then, ...diald[207]: calling site 192.168.0.2 (don't know whose address) ...diald[207]: Error opening device /dev/modem: no such file or directory ...diald[207]: No devices free to call out on In pre-upgrade log, the next line after script /etc/ppp/ip-up started, I don't remember exactly, but some indication of the successful completion of the script, diald not invoked. >From here, I don't know what has caused this problem nor any good idea how to solve it. I will be grateful for any help, Peter ps. to explain why someone who can't manage networking at this level needs to use woody: xfree86 4. Support for my riva tnt, makes a big difference. -- Giulio Morgan [EMAIL PROTECTED]
