In this guide, we will walk you through the process of configuring a Bind Chroot DNS Server on CentOS 6.2. This tutorial assumes that you have already installed Bind Chroot DNS.<\/p>\n
If you’re looking for the best web servers, you can find a detailed comparison on our best web servers<\/a> page.<\/p>\n To begin, you need to install the Bind Chroot DNS Server. You can do this by running the following command:<\/p>\n Next, create a file at \/var\/named\/chroot\/var\/named\/webhostinggeeks.local with the following configuration:<\/p>\n The configuration should include addresses and other host information, as well as the nameservers and mail servers.<\/p>\n The rndc tool is used to manage the named daemon. You need to generate a keyfile called \/etc\/rndc.key, which is referenced by both \/etc\/rndc.conf and \/etc\/named.conf. To do this, use the following command:<\/p>\n You can view the content of the RNDC key with the following command:<\/p>\n Next, edit the \/var\/named\/chroot\/etc\/named.conf file for webhostinggeeks.local:<\/p>\n The options should include the directory, dump-file, statistics-file, and forwarders. Also, include the \/etc\/rndc.key file.<\/p>\n Start the DNS service using the following command:<\/p>\n You should see a message indicating that the named service has started successfully.<\/p>\n To ensure that the named daemon starts automatically during boot, use the following command:<\/p>\n Before testing, make sure your PC or server is using the Bind Chroot DNS Server that has been set up:<\/p>\n The nameserver should be set to the IP address of your Bind Chroot DNS Server.<\/p>\n Finally, test your DNS service with the following commands:<\/p>\n The output should confirm that your DNS service is correctly handling mail and name server requests for your domain.<\/p>\n [root@centos62 ~]# host -t ns webhostinggeeks.local Configuring a Bind Chroot DNS Server on CentOS 6.2 can seem like a daunting task, but with this step-by-step guide, you should be able to get your server up and running. Remember, each step is crucial for the proper functioning of your DNS server.<\/p>\n If you're interested in learning more about different server types, check out our articles on Apache<\/a>, Nginx<\/a>, and LiteSpeed<\/a>. For more information on different hosting options, you can visit our pages on dedicated server<\/a>, VPS server<\/a>, cloud hosting<\/a>, and shared hosting<\/a>.<\/p>\n What is Bind Chroot DNS Server?<\/p>\n \n Bind Chroot DNS Server is a version of the Bind DNS server that operates in a chroot environment for added security. This means it runs in a restricted part of the filesystem, limiting potential damage in the event of a security breach.<\/span>\n <\/p>\n<\/li>\n What is an RNDC key and why is it needed?<\/p>\n \n RNDC (Remote Name Daemon Control) key is used for controlling a DNS server. It's needed for secure communication between the rndc utility and the named daemon, ensuring that only authorized users can control the DNS server.<\/span>\n <\/p>\n<\/li>\n What is the purpose of the \/etc\/resolv.conf file?<\/p>\n \n The \/etc\/resolv.conf file is used to configure DNS clients. It specifies the IP addresses of DNS servers and the search domain.<\/span>\n <\/p>\n<\/li>\n What does the 'host -t mx' command do?<\/p>\n \n The 'host -t mx' command is used to query the DNS server for Mail Exchange (MX) records associated with a domain. It's a way to test if your DNS server is correctly configured to handle mail for your domain.<\/span>\n <\/p>\n<\/li>\n What does the 'chkconfig named on' command do?<\/p>\n \n The 'chkconfig named on' command is used to make the named daemon (the DNS server) start automatically when the system boots. This ensures that the DNS service is always available when the system is running.<\/span>\n <\/p>\n<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":" In this guide, we will walk you through the process of configuring a Bind Chroot DNS Server on CentOS 6.2. This tutorial assumes that you have already installed Bind Chroot…<\/p>\n","protected":false},"author":6,"featured_media":1554,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"wds_primary_category":0,"footnotes":""},"categories":[1138],"tags":[1228,1244,1280,1337,1536],"class_list":["post-1870","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dns","tag-bind","tag-centos","tag-chroot","tag-dns","tag-linux"],"_links":{"self":[{"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/posts\/1870","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/comments?post=1870"}],"version-history":[{"count":0,"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/posts\/1870\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/media\/1554"}],"wp:attachment":[{"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/media?parent=1870"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/categories?post=1870"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/tags?post=1870"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Step 1: Installing Bind Chroot DNS Server<\/h2>\n
<root@centos62 ~># yum install bind-chroot -y<\/pre>\n
Step 2: Creating a Configuration File<\/h2>\n
<root@centos62 ~># vi \/var\/named\/chroot\/var\/named\/webhostinggeeks.local<\/pre>\n
\r\n;\r\n; Addresses and other host information.\r\n;\r\n@ IN SOA webhostinggeeks.local. hostmaster.webhostinggeeks.local. (\r\n 2011030801 ; Serial\r\n 43200 ; Refresh\r\n 3600 ; Retry\r\n 3600000 ; Expire\r\n 2592000 ) ; Minimum\r\n \r\n; Define the nameservers and the mail servers\r\n \r\n IN NS ns.webhostinggeeks.local.\r\n IN A 192.168.1.44\r\n IN MX 10 mail.webhostinggeeks.local.\r\n \r\nmail IN A 192.168.1.42\r\nns IN A 192.168.1.44\r\n<\/pre>\n
Step 3: Generating an RNDC Key<\/h2>\n
<root@centos62 ~># rndc-confgen -a -c \/etc\/rndc.key<\/pre>\n
\r\n[root@centos62 ~]# rndc-confgen -a -c \/etc\/rndc.key\r\nwrote key file \"\/etc\/rndc.key\"\r\n<\/pre>\n
<root@centos62 ~># cat \/etc\/rndc.key<\/pre>\n
\r\n[root@centos62 ~]# cat \/etc\/rndc.key\r\nkey \"rndc-key\" {\r\n algorithm hmac-md5;\r\n secret \"T6tduqyMQ\/YbIDXOmE0Fzg==\";\r\n};\r\n<\/pre>\nStep 4: Editing the named.conf File<\/h2>\n
<root@centos62 ~># vi \/var\/named\/chroot\/etc\/named.conf<\/pre>\n
\r\noptions {\r\n directory \"\/var\/named\";\r\n dump-file \"\/var\/named\/data\/cache_dump.db\";\r\n statistics-file \"\/var\/named\/data\/named_stats.txt\";\r\nforwarders { 8.8.8.8; };\r\n};\r\ninclude \"\/etc\/rndc.key\";\r\n\/\/ We are the master server for webhostinggeeks.local\r\n\r\nzone \"webhostinggeeks.local\" {\r\n type master;\r\n file \"webhostinggeeks.local\";\r\n};\r\n<\/pre>\nStep 5: Starting the DNS Service<\/h2>\n
<root@centos62 ~># \/etc\/init.d\/named start<\/pre>\n
\r\n[root@centos62 ~]# \/etc\/init.d\/named start\r\nStarting named: [ OK ]\r\n<\/pre>\n
Step 6: Enabling the named Daemon to Auto-start During Boot<\/h2>\n
<root@centos62 ~># chkconfig named on<\/pre>\n
Step 7: Setting Up Your PC or Server to Use the Bind Chroot DNS Server<\/h2>\n
<root@centos62 ~># cat \/etc\/resolv.conf<\/pre>\n
\r\n[root@centos62 ~]# cat \/etc\/resolv.conf\r\nnameserver 192.168.1.44\r\n<\/pre>\n
Step 8: Testing Your DNS Service<\/h2>\n
\r\n<root@centos62 ~># host -t mx webhostinggeeks.local\r\n<root@centos62 ~># host -t ns webhostinggeeks.local\r\n<\/pre>\n
\n[root@centos62 ~]# host -t mx webhostinggeeks.local
\nwebhostinggeeks.local mail is handled by 10 mail.webhostinggeeks.local.<\/p>\n
\nwebhostinggeeks.local name server ns.webhostinggeeks.local.\n<\/pre\n\n\n\nCommands Mentioned<\/h2>\n
\n
Conclusion<\/h2>\n
FAQ<\/h2>\n
\n