On Saturday 04 October 2003 06:11, Carlos E. R. wrote:
The 03.10.02 at 22:46, Bernd Koepsell wrote:
THANKS SO VERY VERY MUCH TO EVERYONE!!!!!!!!!
Well, I'm glad :-)
I would like to know what was the cause of all this, but... the important think is that it works.
About your the dns problem you were having, it could be that those two dns servers your ISP used where down - it can be checked with dig, I think. I have seen your message with a log report from wvdial, and I would think it is a problem with the resolv file not being modified properly by the ip-up script, as Joe Morris said. But this is academic now :-)
Actually, dns wasn't working after fresh system install with default modem string. When I changed the init string it began working. I tested this out a couple of times. I'm almost afraid of my modem now. It wasn't the resolve file itself, its' location, or permissions. I looked at it in several ways before I dumped the system, then again when dns wasn't working, after I reinstalled. It was the modem init string. Strange but true!
I prefer to use a local dns server configured as a cache - there is a default config in the suse packages for this. It makes for some faster connections over a modem.
Where and how? Thanks again, Bernd -- "If you want to build a ship, don't drum up the men to gather wood, divide the work, and give orders. Instead, teach them to yearn for the vast and endless sea." Antoine de St. Exupery