(no subject)

[Joseph S D Yao]

On Thu, Nov 11, 1999 at 02:00:36PM -0600, smonoyi at lsu.edu wrote:
> We are trying to upgrade our BIND 4.9.7 to the BIND 8.2.2. version. We have
> the old verion installed on a Linux machine that has Red Hat 6.1

???  IIRC, 6.1 should have both 4.9.7 and 8.2 installed on it, or at
least installable.

> 1. How do I upgrade from the old version to the new one? Do I have to
> uninstall the old version completely and then install the new one, or can I
> just install the new version on top of the old one?

I've done the latter.  Uninstalling the old does save some file space,
and possible confusing conflicts.

> 2. Will Bind 8.2.2 work on this version on Linux?

Should do.  I don't know if there are any new compile problems
introduced.  Be sure to go into the archives and look for all the good
old compile problems, such as forgetting to install the "developer" RPMs
or the "dbm" / "gdbm" RPMs.

> 3. Are there any differences in the way the .db and .rev files are
> structured?

I assume you mean forward and reverse zone files.  The last element of
the SOA no longer menas three different things, it only means the
negative caching time.  You should add a line to give the default TTL:

$TTL	1d	; or however long your default is

If you do not do this, it will assume that you meant the last value in
the SOA record anyway, but will utter a complaint that some find
cryptic.

> 4. Does anyone know where I can find an example of how these files should
> be structured?

Albitz & Liu, "DNS and BIND", O'Reilly & Associates, available from fine
book dealers everywhere.  Get the third edition.

> 5. There is no question that I am new in this, so I would be very grateful
> if someone that already configured the latest version of BIND on a Lunix
> machine can help.

Never did it on Lunix.  ;-)

-- 
Joe Yao				jsdy at cospo.osis.gov - Joseph S. D. Yao
COSPO/OSIS Computer Support					EMT-B
-----------------------------------------------------------------------
This message is not an official statement of COSPO policies.