TIP: Click on subject to list as thread! ANSI
echo: os2user-l
to: Steve McCrystal
from: mark lewis
date: 2004-03-20 16:53:48
subject: RESOLV2

[trim]

 SM> WRT the above, day before yesterday, I used the idea you
 SM> presented about adding to the hosts file, and it seemed to
 SM> work. Yesterday it didn't!  Today, at Mike's suggestion, I
 SM> added a few lines to my RESOLV2 file, in a similar attempt. I
 SM> shut down and rebooted, and the changes were gone!

 SM> It appears as tho RESOLV2 is re-written on each reboot, and
 SM> that the info must come from the "domain" that is listed in
 SM> RESOLV2. This is, of course, conjecture, but not that it is
 SM> rewritten... that's a for sure.

if you use injoy, it rewrites the resolv or resolv2 file on each connect...
i can't remember which one :( most dhcp clients will also rewrite the
resolv files... this is necessary for the possibility of changed dns
servers... this is why i hardcode the dns servers that /i/ want to use and
also generally run my own dns server...

)\/(ark

* Origin: (1:3634/12)
SEEN-BY: 633/267 270
@PATH: 3634/12 106/2000 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.