Hello Managers,
I thought my mistake was in not choosing to install the subset(s)
for bind in my original os installation. (Please see my original
posting at the end of this message.) I now believe that that would
have made no difference. My BIGGEST blunder was in failing to go
more carefully through the checklist for configuring and setting up
a new system. This popped up in GUI form at the console after we
completed the os installation. I should have clicked on the one that
said something about setting up bind. I believe that this would have
invoked bindconfig. Then, in answer to its questions, I could have
indicated that this host would be a resolver only (which is not true).
This (I think) would have caused bindconfig to create these three
files:
/etc/svc.conf
/etc/resolv.conf
/etc/svcorder
The six people mentioned below were very helpful with the needed
information about the first two files and their contents. Someone
here in my department realized that bindconfig had not been run
and that one of the things it would do would be to create this
svcorder file. (We had previously created svc.conf & resolv.conf,
although their contents weren't correct). Running bindconfig
and answering its questions (telling it resolver only) resulted
in the creation of our missing /etc/svcorder file. It only had
three lines in it, the first of which was a blank line. The other
two were simply:
local
bind
THE BIND RESOLVER WILL NOT WORK WITHOUT THIS FILE. I get the
impression from some of the unix aficionados here that this
svcorder file is not a "standard" bind file in other brands
of unix.
MANY thanks to the following six people who responded VERY
QUICKLY with information I needed on the files svc.conf and
resolv.conf:
Burch Seymour RTPS <bseymour_at_ns.encore.com>
Sheila Hollenbaugh <shollen_at_cs.wright.edu>
"Leonard, Roger" <rleonard_at_cvty.com>
John Speno <speno_at_isc.upenn.edu>
Matthew Huff <Matthew.Huff_at_ox.com>
"Christopher L. Davis" <cld_at_prin.edu>
In summary, here is what they told me:
The file /etc/svc.conf must have this line:
hosts=local,bind
And the file /etc/resolv.conf must have these two lines:
domain yourdomain.com
nameserver 127.0.0.1
----------------------------------------------------------
---------Original Posting Follows-------------------------
----------------------------------------------------------
Paul N. Youngblood [mailto:youngbp_at_email.uah.edu]
Sent: Thursday, April 08, 1999 12:38 PM
To: Tru64 UNIX Managers
Subject: BIND 8.1.2 resolver won't work on DU 4.0D
Hello Managers,
Does anybody know what files or config options are required
to make the resolver in BIND v8.1.2 work?
I did an install (not an upgrade, but a custom install) of
DU v4.0D and made the mistake of not installing the subset for
bind. I figured who needs the old version of bind that ships
with 4.0D if I'm going to install BIND 8.1.2, right? Anyway
I then installed jumbo patch 3, and then BIND 8.1.2.
The nslookup command works fine, but because the resolver is
not working, I'm unable to telnet, ftp, sendmail, etc.,
unless I specify IP addresses. I'm sure (almost) that I did
the BIND installation correctly because I did the same to another
AlphaServer that had been running an earlier BIND, and had been
UPGRADED to DU 4.0D. The 8.1.2 resolver works fine on that
machine.
Is my only choice to add the missing BIND subset(s) that I
failed to ask for when I did the custom install of DU 4.0D?
Or is there an easier fix?
Thank you in advance. I'll summarize.
Paul Youngblood
Univ of Alabama in Huntsville
e-mail: youngbp_at_email.uah.edu
Received on Tue Apr 13 1999 - 21:29:12 NZST