Tom Massey wrote: > > What do your /etc/host* files look like? And when you say that you have > to use IP for some programs, do you mean that machines on your internal > network can't access external resources without using the IP number > (probably a problem with the machines on your internal network - where > are they looking for DNS lookups, and is where they're looking a valid > address?) or that you have to use IP numbers to access machines on your > internal network from your Linux box (probably a problem with the > /etc/host* files). Or something else? No the problem is some programs cannot seem to map internal host names to internal IP. Seems they try and use DNS exclusively, not host then bind as set. Whilst not something normally done, nslookup (on my 7.1, in which a cacheing DNS was manually set up), nslookup of the local DNS would not return a local machine. - nslookup cannot see the local DNS under 7.2 at all. On 7.2, this can sometimes mean that when ppp0 dies, netscape cannot find the local webserver (internally visible only) etc. Other programs that try and access internal resources may some times also give host not found unless using the IP number. Its also somewhat random which makes it hard to trace. Whilst this is not really a valid test, this is the same symptom as other programs can give (and I cannot remember which ones until I can start testing this again). This is also the same problem the person who started this thread has. I think that setting up a full DNS may be the only solution here. > > I think you can fix this by going into linuxconf, Networking, > PPP/SLIP/PLIP, ppp0, Networking, and unselecting 'Use the DNS of the > provider'. After this, PPP sessions shouldn't alter /etc/resolv.conf at > all, just use the DNS entries that are already there. There does seem to > be some bug with this feature, where DNS entries are added but not > removed if it's selected. Doesn't seem to effect DNS lookups for me, but > yeah, the file just keeps getting bigger. Potentially quite a nice > feature, but it doesn't seem to work properly for me. > Thanks, trying this and will see how it goes. > I think this is actually how things are meant to work, kppp shouldn't > override the default route unless it's specifically told to. Again, go > into linuxconf, ppp0 and check that under the Networking tab 'Set > default route' is selected. Personally I don't like kppp much, I prefer > to use scripts and 'ifup ppp0', but I think that in 7.2 kppp should load > the settings that have been set up by linuxconf. Nope, according to the kppp docs, kppp should replace the default route with the ppp interface once up. In most cases, the system will not work if your internal lan card is set as the gateway, and ppp0 is the interface to the outside world! Whilst setting the DNS as above, I checked the route setting (again!) and decided to delete the internal address set as the default route by the system - I will see how that goes next time I reboot. Thanks for the suggestions, BillK
Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
