Re: DNS wierdness on a TiBook running unstable

2001-09-24 Thread Gregory P. Keeney
It turned out to be nscd. It was not the mozilla bug (I was aware of that one...). Everything works smoothly now. Colin, thanks for the pointer to whereami; I will try it out tonight. Thanks to all for the help. Gregory P. Keeney Mad Computer Scientist

Re: DNS wierdness on a TiBook running unstable

2001-09-21 Thread Wilhelm *Rafial* Fitzpatrick
A minor follow up: I noticed from reading the reference Mozilla bug that some work had been done on rereading resolv.conf when toggling on and off line, and I in fact confirmed with 0.9.4 that after switching networks I could get Mozilla working again by toggling it off and online using the co

Re: DNS wierdness on a TiBook running unstable

2001-09-21 Thread Colin Walters
Tuomas Kuosmanen <[EMAIL PROTECTED]> writes: > FYI, there is work being done on Ximian Setup Tools > (ximian-setup-tools on gnome CVS) to make a "location tool" similar > to the macos location switcher. So you could define stuff like nfs > mounts, network setup, whatnot and their cat that gets swi

Re: DNS wierdness on a TiBook running unstable

2001-09-21 Thread Tuomas Kuosmanen
On Fri, 2001-09-21 at 19:53, Gregory P. Keeney wrote: On Fri, 2001-09-21 at 08:55, Josh Huber wrote: > > do you have nscd installed? Doh! Ok... With that gone everthing should be quite happy. (Now all I need to do is write a network switching applet for the gnome panel

Re: DNS wierdness on a TiBook running unstable

2001-09-21 Thread Josh Huber
"Gregory P. Keeney" <[EMAIL PROTECTED]> writes: > Ok... With that gone everthing should be quite happy. (Now all I > need to do is write a network switching applet for the gnome > panel...) I knew it. This caused strange name service problems for me too, and it took a little while to track it do

Re: DNS wierdness on a TiBook running unstable

2001-09-21 Thread Colin Walters
Wilhelm *Rafial* Fitzpatrick <[EMAIL PROTECTED]> writes: > I find that after switching networks, stuff like telnet adapts to the > new regime just fine, but Mozilla stubbornly refuses to see the new > DNS servers until it is restarted. But I only have to restart the > app, not the 'book. This is

Re: DNS wierdness on a TiBook running unstable

2001-09-21 Thread Gregory P. Keeney
On Fri, 2001-09-21 at 08:55, Josh Huber wrote: > > do you have nscd installed? Doh! Ok... With that gone everthing should be quite happy. (Now all I need to do is write a network switching applet for the gnome panel...) Thank you. Gregory P. Keeney Mad Computer Scientist

Re: DNS wierdness on a TiBook running unstable

2001-09-21 Thread Michel Dänzer
"Gregory P. Keeney" wrote: > (I hate to restart a Debian box for anything other than a new kernel... It > just seems... wrong). Absolutely! Something apparently needs to be restarted here, but certainly not the box. :) -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer

Re: DNS wierdness on a TiBook running unstable

2001-09-21 Thread Josh Huber
"Gregory P. Keeney" <[EMAIL PROTECTED]> writes: [snip] do you have nscd installed? ttyl, -- Josh Huber | [EMAIL PROTECTED] |

Re: DNS wierdness on a TiBook running unstable

2001-09-21 Thread Adam Lazur
Gregory P. Keeney ([EMAIL PROTECTED]) said: > Recently, however, DNS does not seem to work after the switch. I can > ping the DNS servers (or any numeric address), but ping cannot resolve > any names. Galeon cannot seem to resolve any names either. The bizare > thing is that dig, host, and the depr

Re: DNS wierdness on a TiBook running unstable

2001-09-21 Thread Wilhelm *Rafial* Fitzpatrick
can ping the DNS servers (or any numeric address), but ping cannot resolve any names. Galeon cannot seem to resolve any names either. The bizare thing is that dig, host, and the deprecated nslookup have no problems... ... Any ideas? Have you tried just restarting Galeon? I'm doing something sim

Re: DNS wierdness on a TiBook running unstable

2001-09-21 Thread David N. Welton
"Gregory P. Keeney" <[EMAIL PROTECTED]> writes: > I can ping the DNS servers (or any numeric address), but ping cannot > resolve any names. Galeon cannot seem to resolve any names > either. The bizare thing is that dig, host, and the deprecated > nslookup have no problems... Try running tcpdump t