Many thanks to all the people who responded. These include:
Richard Jackson
Pat Wilson
Allan Simeone
Kym Schwarz
Brian Parkhurst
John Speno
Bryan Lavelle
Stephen LaBelle
Mark Allen
My original observation was:
I just applied all of patch kit 3 to a plain vanilla DU 4.0D setup
(upgraded only a few weeks ago). The patch process seemed to go OK,
with
no special instructions given, or clashes with layered products
called out
(haven't installed any layered products yet).
All seemed to go well until the reboot after the kernel rebuild.
Now name
resolution does not work. ping, telnet, ftp etc. cannot find
machine
names - IP addresses work fine. Curious thing is that NFS mounts go
ahead
OK - guess they use a different method to resolve names, and PINE
works OK
too even though its accessing a mail server across campus.
Any ideas what might have killed the name resolution - I even
de-installed
patches 98 and 101 from the distribution but to no avail. Has
anyone
else done this install and/or seen this behavior?
This is apparently a known problem - in fact there's supposed to be a patch
out for the BIND setup. The short term fix is to do what Pat Wilson
suggested:
Don't know what it was, but changing the 'hosts' order in svc.conf
to
"local, bind" seems to fix it. I understand that a patch is
forthcoming.
This did indeed fix the problem. However it is probably prudent to install
the new
patch when it is available.
I would also like to apologize to John Speno who had posted a summary on
essentially this very issue just last Thursday, under the subject line:
SUMMARY: problems with 4.0d patch kit #3 (DNS lookups)
- should have checked the archive first. Thanks again to all who responded.
Paul A. Scowen
Assistant Research Scientist
Department of Physics & Astronomy
PO Box 871504
Arizona State University
Tempe, AZ 85287-1504
Tel: (602) 965-0938
FAX: (602) 965-7954
Email: paul.scowen_at_asu.edu
WWW:
http://tycho.la.asu.edu/scowen.html
Received on Tue Jan 12 1999 - 16:44:00 NZDT