How to configure DNS configuration for RHEL 5?

Linux and Unix-Like Red Hat
1

I wanted to know how to configure DNS configuration for RHEL 5.

I hope, my query is clear of how to setup DNS for RHEL 5.

Please revert with the reply to my query

Regards

2

Do you want to set up the RHEL host as a DNS server or set it as a client to use an existing DNS server?

What have you tried so far?

Robin
Liverpool/Blackburn
UK

3

Thanks for your answer. I was looking at a DNS cache naming server. Request you to please give the steps for setting up the RHEL host as a DNS server and the RHEL host as a client to use an existing DNS server.

Regards

4

I would guess that you just want to be a client then, given that you already have an existing DNS server. Have a read of the manual page for resolv.conf - note that there is no e at the end of resolv.

Robin

5

Hi,

I listed out the following steps to create a DNS server on RHEL 5, we have RHEL 5.8 in our production environment:

1) Install Bind
2) Make named.conf
3) Configure zone file
4) Edit /etc/resolv.conf

Are these steps correct or there are a different set of steps to follow?

Please revert with the reply.

Regards

6

So, you want to be a DNS server now? It seems a sensible list to proceed with, but you have to so these too:-

  • Decide if it is stand-alone, master-slave (do we even have that concept any more) or peer.
  • Ensure other DNS servers are configured to communicate with this one (zone transfer etc.)
  • Start the service
  • Test function
  • Define DNS record update process
  • Test function
  • Decide your domain(s)
  • Input your A-records (name to IP)
  • Input your CNAME-records (service name to host name alias)
  • Test function
  • Encourage everyone to use the alias names. It makes future migration so much easier.

There may be more, but I assume you have some documentation to work with already.

Thinking about using a service alias name everywhere, you are best having one for each service you use that is a discreet block that you might migrate. You can then group them to a hostname and then have an A-record for the hostname to point to the IP address:-

serivce1  alias to  host-A
service2  alias to  host-A
service3  alias to  host-A
host-A defined as 123.123.123.123

You can then change to:

serivce1  alias to  host-A
service2  alias to  host-B
service3  alias to  host-A
host-A defined as 123.123.123.123
host-B defined as 321.321.321.321

...and all uses of service2 will be re-directed.

You need to spend time to plan your naming conventions. Get to know the applications and what they are able to reference and work out what discreet processes you can define, then make sure everyone sticks to it. We're had terrible trouble where people use the hostname assuming it will never change or just have the "well, it works for service1, so I can just re-use that rather than adding service4" which leaves you unable to separate them, so you have to move lots together and if one bit fails, you have to move them all back whilst you unpick it.

Robin

7

Hi,

Thanks but an example with the complete steps could help.

Regards