HP Bind 8.2.5

[paul fritzsche_1]

Hi,

Does anyonme know where to find details about how hp bind 8.2.5 works? Need to learn about it.. Logfiles to check out, the specific dns-service logfiles and config-files..

Thnx for help
Paul

[Sunil Sharma_1]

Hi Paul,

This doc may help you.

http://docs.hp.com/hpux/pdf/B2355-90147.pdf

Sunil

[Geoff Wild · Accepted solution]

HP's bind is the same as the source - a lot of docs here:

http://www.isc.org/products/BIND/

BTW - I would upgrade to 9.2....

http://software.hp.com/portal/swdepot/displayProductInfo.do?productNumber=BIND9.2

Rgds...Geoff

[paul fritzsche_1]

Hi Geoff,

Why do you think I should upgrade to Bind 9.1.2?

Regards
Paul

[Geoff Wild]

Why Bind 9.2?

BIND version 9 is a major rewrite of nearly all aspects of the underlying BIND architecture. The Internet Software Consortium strongly recommends that you upgrade to BIND 9.2. This will avoid having to upgrade later as Bind 8 is no longer being developed and it is only a matter of time where, like it's predecessor Bind 4, will no longer be supported.

Some of the important features of BIND 9 are:

Features


DNS Security
DNSSEC (signed zones)

TSIG (signed DNS requests)
IP version 6
Answers DNS queries on IPv6 sockets
IPv6 resource records (A6, DNAME, etc.)
Bitstring Labels
Experimental IPv6 Resolver Library
DNS Protocol Enhancements
IXFR, DDNS, Notify, EDNS0
Improved standards conformance
Views
One server process can provide multiple "views" of the DNS namespace, e.g. an "inside" view to certain clients, and an "outside" view to others.
Multiprocessor Support
Improved Portability Architecture

Differences between Bind 9 and 8





BIND 8 is single-threaded, and does not answer queries during the start-up process. BIND 9 is natively multi-threaded, and doesn't have this problem.
Because BIND 8 is single-threaded, it cannot take advantage of multiple CPUs in a server. Because BIND 9 is natively multi-threaded, it can take advantage of multiple CPUs.
BIND 8 handles zone transfers through an external program, which may cause significant fork()/exec() overhead if used on the master. BIND 9 handles zone transfers internally, and does not have this problem.
BIND 8 only partially supports some of the security and IPv6 related extensions, while BIND 9 is the reference implementation for these features.
BIND 8 is the last in a long line of hacks on top of hacks on top of hacks, whereas BIND 9 is a complete ground-up rewrite, using new programming methods that try to help ensure that the kind of security bugs you could have with the old version simply are not possible any more.

RGds...Geoff