Hi ! > > I have a big problem with the name resolving in my tiny network: > Does it work when it is *not* connected to your ISP? I don't use dns for my internal network. All of my computers have /etc/hosts files for name resolving. DNS is only used for the internet.
Next bad thing: I know nearly nothing about dns. Sorry :( > > Eddie: # route > > Kernel IP routing table > > Destination Gateway Genmask Flags Metric Ref Use Iface> > localnet * 255.255.255.0 U 0 0 0 eth0 > > default Marvin.galaxy.h 0.0.0.0 UG 0 0 0 eth0> > Hm. The uppercase hostname is a bit unusual.. Both Eddie and Marvin in > initcaps!? "initcaps" means "initial captial letters" ? Thats the way they stand in /etc/hosts... If that's unusual, i'll change that... ... Did so, no effect. > > Eddie: # cat /etc/resolv.conf > > search galaxy.home > > domain galaxy.home > > nameserver 192.168.42.99 > Hm. According to "man resolv.conf", specifying both "search" and > "domain" with the same value is redundant. But it shouldn't cause a > breakage though... (actually seems to work fine for me!) > > I presume that you have a nameserver of sorts running on marvin? Me too ;) Well, ps says: Marvin: # ps ax | grep name 181 ? S 0:07 /usr/sbin/named > > Until yesterday, everything worked fine. But now, on both eddie and > > zaphod name resolving doesn't work anymore :( > > > > [EMAIL PROTECTED]: > ping www.fhm.edu > > ping: unknown host www.fhm.edu > > Did this take a long time? I.e. is the response instant or does it seem> to "time out"? It took a long time -> timeout I think. > There may be local caching involved, try a hostname that > you haven't tried before, e.g. "host somemachine.non-existent-domain" Never was before. But I'll try... > Also: Was marwin connected to your ISP at the time? Yes, it was. All experiments were with marvin online. I tried the ping (quoted below) alternating with name and ip. > > [EMAIL PROTECTED]: > ping 129.187.244.84 > > PING 129.187.244.84 (129.187.244.84): 56 data bytes > > 64 bytes from 129.187.244.84: icmp_seq=0 ttl=251 time=181.3 ms > But does WinNT use marwin for DNS? Double-check.... (is it > the "winipcfg" that is used on windows? dunno..) Never heard "winipcfg"... > I would expect DNS lookups to fail when marvin is not connected, and > succeed once marvin's link to the outside world is up. No. The "ip-ping" was working (= connection is up), but the "name-ping" didn't. > I am far away from beeing a network guru > Neither am I. Please take the above with a suitable amount of salt. The whole thing is strange: Everything works fine on wednesday. Name resolving is broken on thursday. Nothing changed on at least one of the computers where it doesn't work => Error should be on server side Nothing changed on the server and everything's perfect on a different client=> Error should be on client side. That's a behaviour I expect from windows, not from linux. Still need help, pleeeease! -- Markus Grunwald Registered Linux User Nr 101577 http://counter.li.org http://www.grunwald.2xs.de
