Category: BIND

Domain Name System – Propagation

May 10, 2018
BINDDomain Name SystemNetwork

I recently decided to test a Domain Name System (DNS) provider expansion with GoDaddy and  ClouDNS (link here) for a proof of concept using the domain name noelalvarez.org. The initial configuration and testing were successful. However, after I made the decision to host all DNS service with GoDaddy (again, it was a proof of concept) I found a large quantify of name server around the globe contained name server (NS) records for noelalvarez.org with entries pointing to ClouDNS name servers (ns21.cloudns.net, ns22.cloudns.net, ns23.cloudns.net, and ns24.cloudns.net) using Whats My DNS? (link here). I found this odd due to the fact that the GoDaddy DNS management interface only contained (2) NS records (ns57.domaincontrol.com and ns58.domaincontrol.com) which are the authoritative for the domain noelalvarez.org and the ClouDNS name servers are no longer hosting zone files or responding to DNS queries for noelalvarez.org. Additionally, the Time to Live (TTL) was a maximum of (1) hours. So, I didn’t expect to find inconsistencies days later.

So, what could be causing the lack of synchronization in the NS records (remember, DNS is a distributed and hierarchial system by nature)? Upon basic troubleshooting I found that the GoDaddy name servers ns57.domaincontrol.com and ns58.domaincontrol.com did not contain the same NS records for noelalvarez.org using the nslookup utility (please see the screen shots below). I have contacted GoDaddy support and they have provided me with assurance that they will manually delete the NS records of ns21.cloudns.net, ns22.cloudns.net, ns23.cloudns.net, and ns24.cloudns.net from ns57.domaincontrol.com.

Red Hat Enterprise Linux 7 – BIND Installation and Configuration

November 17, 2016
BINDDomain Name SystemLinuxNetworkRed Hat Enterprise Linux 7

Domain Name System (DNS) is an integral component of any Information Technology (IT) infrastructure. This is a step by step guide for configuring a Red Hat Enterprise Linux 7 public facing DNS server using the BIND software package. Additionally, I would like to add that, for the purposes of this demonstration the zone file created for noelalvarez.net is not pointing to the genuine Internet Protocol (IP) address of the website.

  1. Enter the command yum update -y to update the server.01
  2. Enter the command yum install bind-chroot bind-utils -y to install bind and DNS utilities.02-0102-0202-03
  3. Enter the command systemctl start named-chroot to start the DNS server.03
  4. Enter the command systemctl status named-chroot to verify the DNS server is running.04
  5. Enter the command rndc status to verify the name server control utility is running (i.e. server is up and running).05
  6. Enter the command journalctl -u named-chroot to verify there are no errors.06-0106-02
  7. Enter the command systemctl enable named-chroot to configure BIND to start automatically after a reboot.07
  8. Enter the command cd /etc to navigate to the etc directory.08
  9. Enter the command cp named.conf named.conf.2016111700 to create a copy of the named.conf file.09
  10. Using a text editor, edit the following fields in the name.conf file.
    1. listen-on port 53 { 127.0.0.1; }; NOTE: Add the Internet Protocl (IP) address of the host.10-01
    2. allow-query     { localhost; }; NOTE: delete localhost; and add any;.10-01
    3. Add a forward lookup zone.10-02
    4. Add a reverse lookup zone.10-02
  11. Enter the command named-checkconf to verify the named.conf file has not syntax errors.11
  12. Enter the command cd /var/named/chroot/var/named/ to navigate to the named directory.12
  13. Using a text editor create the zone file for a forward lookup. In this example it is noelalvarez.net.13
  14. Using a text editor create the zone file for reverse lookup. In this example it is the 67.205.160.0/24 IP address range.14
  15. Enter the command rndc reload to read the changes made to the named.conf and zone files.15
  16. Enter the command cd /etc to navigate to the etc directory.16
  17. Using a text editor, edit the resolv.conf file by adding configuring the server to use it’s IP address for name resolution.17
  18. Enter the command dig noelalvarez.net to query the name server for the A record of noelalvarez.net.18
  19. Additionally, you may use nslookup to query the name server for the various records that were created.19
  20. Lastly, you may query the name server from a host on an external network to verify it is a public facing DNS server.20

BIND – Create a Bind Zone File

February 25, 2014
BINDDomain Name SystemLinux

You may use the following website to automatically create a BIND zone file.

Enjoy!

Linux – Configure a BIND Zone File

January 31, 2014
BINDDomain Name SystemLinuxNetwork

Domain Name System (DNS) is an essential part of any network. Berkeley Internet Name Domain (BIND) may be installed and configured on Linux CentOS and provide DNS name resolution. The configuration of BIND includes zone files. Below you will find a sample zone file for the domain name example.com. You may use this sample as a template and input the DNS records for your corresponding domain name.
01