How to setup own dns server

->>>> Click Here to Download <<<<<<<-

I'm assuming you want to setup a windows DNS server, but the principals will work for most servers. The first thing you need to do is create your new domain entry. In windows this is called a "Zone" and you will have one for every domain name you have.

Add your main domain in the forward lookup zone as a Primary zone, which will be in the format "Domainname. Any changes you make to the forward lookup should have the "Update Reverse Lookup" option ticked if its available, if not you must update the reverse zone manually This is very important. Now edit the "NS" entry in your forward zone to "NS0.

Com", and set it to the relevant IP address. Add another NS record and set it to "NS1. Now you need to configure the SOA entry in the forward lookup zone. The primary server will be the "NS0. The refresh interval should be set somewhere between to seconds, the retry should be between seconds and the expires after should be around weeks I'll let you work out the seconds for that.

The minimum TTL is quite important, and depending on what you are going to do with the domain, you might need to tweak this a bit. Typically a value between hours should be used. Now go to your "Name server" settings in your SOA record In windows this is a tab in the same window remove the defaults, and add your two Name servers that you just setup. We will come back to the SOA record later, but for now we need to do some more stuff.

If you want a website, then your going to want the WWW. We will set it up as an "A" record, which means it is a separate top level record and will be populated separately from other entries.

So add an "A" to your forward lookup zone and put the entry as "WWW", and set the IP address to wherever you want the website to be. This will be where the domain always goes, and it could be anywhere.

Running your own DNS server gives you more control over your network. One common motivation is being able to configure network-level domain mappings, such as web-server to Configuring your router to use your DNS would result in any of your connected devices being able to access An in-house DNS server can also improve performance and provide an extra layer of resilience. Wide-scale DNS outages are not unheard of ; using a custom server with a long-lived cache for critical services you interact with could help you ride out downtime at your selected upstream provider.

Everything behind your router will end up making DNS queries via Dnsmasq. However, it is worth noting that all popular desktop and mobile operating systems support setting a DNS server, so you could configure individual devices to use Dnsmasq without enabling it at the router level.

Your host should have a static IP assigned. From hereon, the IP This is pre-populated with initial settings. Some changes need to be made for Dnsmasq to work effectively in a local network scenario. Remove the character from the start of each line. This instructs Dnsmasq to forward unresolved queries to 8. Next adjust the cache size. This defaults to a relatively low value of cached requests. Skip to content. Introduction Despite my woeful knowledge of networking, I run my own DNS servers on my own websites run from home.

Here I share how and why I persist in this endeavour. I: got a domain from an authority a. Log on and set up root password SSH to the servers and set up a strong root password. Buy in a bundle here. Share this: Email. Like this: Like Loading Published by zwischenzugs. Published January 26, May 16, THanks, Ian. Does this make my website whois check return me as the web host provider? What is the rate of your service? And do you feel comfortable with Erlang? Leave a Reply Cancel reply Enter your comment here Fill in your details below or click an icon to log in:.

Email required Address never made public. Name required. Follow Following. Sign me up. Already have a WordPress. Log in now. Loading Comments