This is hostname-resolution in view mode; [Up]
Date: Sun 25-Sep-1989 14:03:39 From: Unknown Subject: hostname resolution Thanks to Pascal Chesnais and Doug Brenner for pointing out that, sadly, this behavior is a documented feature and is part of the version of BIND that NeXT uses. The BIND appendix in the SysAdmin section of the manuals says that the domain in the boot file (or resolv.conf file) is appended to names which do not contain a dot in them (hence, F.WORD does not qualify even though if BIND did append the domain it would find the name). Workarounds exist, but a better BIND would be on my wishlist for 1.1. ...eric
Date: Sun 26-Sep-1989 16:50:13 From: Unknown Subject: Re: hostname resolution In article <6262@pt.cs.cmu.edu> eht@f.word.cs.cmu.edu (Eric Thayer) writes: >Workarounds exist, but a better BIND would be on my wishlist for 1.1. > BIND 4.8 will be in the next release. --morris Morris Meyer NeXT, Inc. Software Engineer 3475 Deer Creek Road NeXT OS Group Palo Alto, CA 94304 mmeyer@next.com 415-780-4683
Date: Sun 27-Sep-1989 09:09:55 From: Unknown Subject: Re: hostname resolution In article <86@entropy.next.com> mmeyer@next.com (Morris Meyer) writes: >BIND 4.8 will be in the next release. THANK YOU! THANK YOU! THANK YOU! -=EPS=- >From: roger@gtisqr.UUCP (Roger Droz)
These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Marcel Waldvogel and Netfuture.ch.