This content has been marked as final. Show 10 replies
Bind has been available and standard ever since.
Thanks for your answer. Does it mean that there are no differences in making a DNS server in RHEL 5 & RHEL 6? I have noticed that the file /etc/named.conf is readily available in RHEL 6 but it is not so in RHEL 5.
Yes. Bind is available for both RHEL 5 and 6. Just do a
and should get info about available versions.
yum search bind
shows you that this file could come from bind or caching-nameserver or bind97 package ...
yum whatprovides /etc/named.conf
BIND is not installed and configured by default and as such there is no universal named configuration file. Different version of BIND provide different features. The default installation of BIND under RHEL 6 installs a caching only nameserver for localhost. You will always have to configure BIND to your needs in a real world scenario. You need to read the product documentation, such as the RHEL deployment guides, or search for information on the web. There is plenty of resourceful information and examples on how to setup BIND.
Thanks but I did not see the /etc/named.conf in our RHEL 5.8 server even when DNS server is implemented on the server.
Are you using chrooted BIND? In this case, check /var/named/chroot/etc/.
What is your trouble with named.conf? Are you questioning why the default installation of BIND under RHEL 6 comes with a named.conf file and RHEL 5 does not? Well, software and installations evolve and it's noting unusual. I'm afraid you have to ask Red Hat.
RHEL 5 and 6 are obviously using different versions, but the BIND fundamentals remain the same. If named.conf does not exist you may have installed BIND, but you did not configure the service yet. Like I mentined already, you have to create or configure the named.conf file in a real world scenario. There is plenty of documentation and examples if you do not know how.
If you are looking for a OS that comes with everything installed and preconfigured than Enterprise Linux is not the right choice.
Edited by: Dude on Apr 29, 2013 4:00 AM
RHEL 5.8 seems to be having a chrooted BIND.
if you install the chroot package, will be chrooted, otherwise not
Thanks. But, does that mean that BIND has different implementations for a chrooted package and also otherwise? In that case, there must be a different package for a chrooted BIND and one for a normal BIND. Do all these packages come in a default installation of RHEL 5 or RHEL 6?
I hope, there is clarity on the points listed above by me.
This is one of my server using a RHEL 5.6 DVD as repository. So there are these two packages available...
myuser@myserver:~> yum info bind-chroot.x86_64 bind.x86_64 Loaded plugins: rhnplugin, security Available Packages Name : bind Arch : x86_64 Epoch : 30 Version : 9.3.6 Release : 16.P1.el5 Size : 988 k Repo : cd-media Summary : The Berkeley Internet Name Domain (BIND) DNS (Domain Name System) server. URL : http://www.isc.org/products/BIND/ License : BSD-like Description: BIND (Berkeley Internet Name Domain) is an implementation of the DNS : (Domain Name System) protocols. BIND includes a DNS server (named), : which resolves host names to IP addresses; a resolver library : (routines for applications to use when interfacing with DNS); and : tools for verifying that the DNS server is operating properly. Name : bind-chroot Arch : x86_64 Epoch : 30 Version : 9.3.6 Release : 16.P1.el5 Size : 46 k Repo : cd-media Summary : A chroot runtime environment for the ISC BIND DNS server, named(8) URL : http://www.isc.org/products/BIND/ License : BSD-like Description: This package contains a tree of files which can be used as a : chroot(2) jail for the named(8) program from the BIND package. : Based off code from Jan "Yenya" Kasprzak <firstname.lastname@example.org>