DNS ppp0 glitch with lynx on tomsrtbt 4350

Snip...

Thanks for replying; as I told Bill, I realize it isn't a barnburner. :)

Yeah--AFAIK it's never been a showstopper for me heretofore. ISTR Tom did mention setting up a loopback in one of his FAQs, but I couldn't find any references to that in his latest version.

As you mentioned, I don't see anything obviously wrong with my hosts file or the nameservers--which is consistent with ping-telnet-wget working for both ppp0 and eth0.

...and remarkably useful support modules for (older) ethernet cards, from either the stock single floppy install, or the add-ons (below). I've used tomsrtbt to identify ethernet cards on some very old boxes, when manually setting up networking for recent SuSE distros on them.

I got pppd (and required slhc support) from the add-ons subdirectory from one of the Toms mirrors (like Tux.org). I have these auxiliary apps along with some housekeeping and file system expansion on a second floppy which I load manually from a gzipped floppy tarball after booting Toms.

ISTR I also found lynx in one of these add-on mirrors, but I can't locate it on them at the moment.

But this lynx has always worked with this latest Toms until I tried using it again this past week or so (i.e.; lynx DNS was never flaky as now).

Thanks for reminding me; it completely slipped my mind.

Toms host.conf looks the same as SuSE 9.3. There is no Toms nsswitch.conf but copying the SuSE 9.3 version to the Toms setup didn't seem to fix the ppp0 DNS glitch.

That works fine, too, AFAICT (line-wrapped so slrn won't whine):

traceroute to google.com (216.239.57.99), 30 hops max, 40 byte packets 1 * * * 2 67.95.86.97 (67.95.86.97) 170.075 ms 168 plus 1.586 ms 168 plus 1.961 ms 3 64.1.2.97 (64.1.2.97) 159.99 ms 159.832 ms * 4 65.106.4.193 (65.106.4.193) 160.064 ms 168 plus 1.785 ms 150.003 ms 5 65.106.4.182 (65.106.4.182) 159.952 ms 168 plus 1.797 ms 159.995 ms 6 193.251.248.17 (193.251.248.17) 159.952 ms 159.839 ms 159.955 ms 7 193.251.128.102 (193.251.128.102) 199.952 ms 219.784 ms 209.964 ms 8 193.251.240.122 (193.251.240.122) 209.995 ms 199.834 ms 199.957 ms 9 193.251.249.18 (193.251.249.18) 199.952 ms 199.836 ms 199.959 ms 10 66.249.94.10 (66.249.94.10) 209.903 ms 199.884 ms 199.957 ms 11 216.239.49.170 (216.239.49.170) 209.904 ms 66.249.94.25 (66.249.94.25) 199.886 ms 209.787 ms 12 216.239.49.2 (216.239.49.2) 249.95 ms 216.239.49.93 (216.239.49.93) 219.883 ms 216.239.49.5 (216.239.49.5) 209.837 ms 13 216.239.57.99 (216.239.57.99) 209.832 ms 219.785 ms 210.003 ms

So it seems to be lynx specific, and I may just need to rethink it...

Thanks again for taking the time to look at this.

-- Regards, Weird (Harold Stevens) * IMPORTANT EMAIL INFO FOLLOWS * Pardon any bogus email addresses (wookie) in place for spambots. Really, it's (wyrd) at airmail, dotted with net. DO NOT SPAM IT. Kids jumping ship? Looking to hire an old-school type? Email me.