Ben, Thanks for the response. I must be doing something different than you because my system still invokes diald before completing local telnets. Basically, diald makes working locally >>>>useless<<<<. When I turned diald off, all is okay... Here's my /etc/resolv.conf after I made your change. domain SciFi.com order hosts, 192.168.136.1 nameserver 192.168.136.1 See anything that I need to change to get diald to work right? Finally, how do you get a man page on resolv.conf under SuSE? man resolv.conf does not do it, neither does info resolv.conf... BTW, man resolv.conf under FreeBSD 2.2.7 does work!?! Thanks. Steve. On Sun, 29 Nov 1998, Ben Messinger wrote:
Steve Pauly wrote:
Greetings,
I have a problem involving the diald as installed by Yast on my 5.3 system, and >>>>local net<<<<.
Before diald, when I made a telnet connection to one of my local ethernet boxes, the telnet connection was made instantaneously.
Now, diald must start and connect before telnet can complete, even though no internet telnet host was involved.
The problem is in /etc/resolv.conf
[ ...]
Here is the fix. In /etc/resolv.conf add the following line (please correct me if my syntax is wrong, but I have no documentation on this -- anyway it works)
order hosts, 204.203.235.3, 192.220.251.1 #<-- replace with your DNS
Of course you will need to have your nameservers and domain listed in subsequent lines. Adding this line immediately solved my problem. I hope this is your solution as well.
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e