How to create your own DNS to resolve URL to IP addresses

Hey friends I am starting this thread to share the workaround for creating your own DNS to resolve URL to IP addresses. This example is for windows DNS server but the same method will work for other servers as well. You just need to have domain name with full control, DNS server software, one fixed IP address, services that you desire to use on the server. Once you are ready with the same then you can follow the below steps:

Creating new domain entry:
For every domain name there is something called Zone in windows, so here you have to add your main domain as Primary zone in forward lookup zone in "Domainname.com" format or .co.uk format. If this is just a local network DNS then make sure you are not allowing dynamic updates. You will have two entries under new domain after creating the same. The entries will be named as "SOA" and "NS" where SOA stands for Start of Authority where as NS stands for Name server. You will have to follow the same process and add a domain as a reverse lookup zone if you are willing to create 100% compliant DNS. If you make any changes to forward lookup then "Update Reverse Lookup" option should be checked marked as well. If it is not then it will be must to change the reverse zone manually.

Editing "NS" entry in your forward zone:
Here you have to edit entry to "NS0.DomainName.Com" and set the same to a relevant IP address. When you are done with the same then you can proceed further and add another (NS) record and set the same to to "NS1.DomainName.Com". After that you will have to configure SOA entry in forward lookup zone. You can change the serial number in "YYYYMMDDnn" format but it is not compulsory. You should also set refresh interval between 1200 to 43200 seconds, retry between 120-7200 seconds where as expiry should between 2-4 weeks. Depending on the use of domain, setting minimum TTL is a very important task, normally value between 2-3 hours is recommended. You can just go to "Name server" settings in SOA record and add two Name servers that you have created after removing the defaults. If you are willing to get a website then you can set it up as “A” record, this record will get populated separately as it is a top level record. After adding "A" to your forward lookup zone, set entry as "WWW" and set IP address for the website, you just have to keep in mind that you are having a web server waiting for it.

Setting up mail on domain:
If you want then you can set up a mil on your domain, it is not recommended but it can be helpful for keeping track of potential issues that can occur later. There are a number of mail servers and you can get anyone of them for free, if you want then you can get webmail as well but you will have to spend some bucks for the same. So if you are interested in mail server or webmail then you can proceed further for configuring MX records. For that you have to add "A" name for your mail server and you can call it as “abc. domainname.com" letting it point to one of your IP addresses. After that you need to add an "MX" record in the Forward Lookup zone giving it full "A" record of “abc. domainname.com" . You should make sure that you are not setting up the same as host or child and leaving that field blank.

Adding more records:
Even this is not recommended but I think adding the same will be quite helpful as well, you have to add a "RP" entry and "MB" entry where "RP" entry will be a contact point for domain complaints and a Responsible Person where as "MB" entry is just a mailbox entry. The "RP" should have host or domain and must be set up to your mail box. For eg if server is "xyz.Domainname.com" then the mailbox should be set to "MB" record that you will make. When you are done with the same then you can go to SOA and switch the responsible person to the new "RP" record.

Checking out the performance of server:
For checking the performance of your server you can go to www.dnsreport.com and run report on your domain "domainname.com" to know if there is any issue or not. Basically you will get a list of issue if it is there with the workaround for fixing them. If at all you are having a new domain name which is not yet hosted then you can re-point the domain to your new server. You can contact the provider owning the domain for the same, you basically have to enter 2 name servers and one ip addresses which in your case is "NS0.domainname.com" and "NS1.domainname.com" after updating the same you are done!!!

If you want to check if the settings you have provided are working or not then you can perform a whois on the main DNS server of your domain provider and you can even track progress of the domain changes using below commands:

c:\nslookup ns0.domainname.com NS0.yourprovidersdns.com (with this you will come to know about the entries your domain provider might be having)
c:\nslookup www.domainname.com ns0.domainname.com (With this you will come to know about the changes that your domain might have gone)

Lastly I just wanted to add that make sure you are changing the refresh or update value after making any changes to the DNS and always having a back up of the server.