Tinydns - Here is an example
I have looked around on the web and could not find hardly any documentation on setting up hosts in tinydns, any examples I found were pretty bad or incorrect to say the least so I am going to post what I got to work with the explaination in hopes of saving someone the hours I just wasted trying to find documentation.
Code:
########################################################################################## Code:
# |
I posted yesterday on software re: tinydns... I
d like to capture the DNS task on my little setup. All i want to do is do the external DNS for 2-3 websites I host. Maybe do this "split horizon" and put it right on the firewall box? any thoughts? Which box are you doing it on? firewall, webserver or ?, I just want to head out in the right direction before I begin to try to implemnent it. thanks for the post, was clear and to the point. Piratebiter |
You can do the dns on anything that has a live ip address and is running linux, I have 2 dedicated dns servers but I am hosting several hundred websites, but you can run tinydns on just about anything, I handle about 2-3 thousand queries per minute and it only takes about 1% of my cpu on a 800 MHz server.
Now if you want to do it correctly you will need to have 2 dns servers as most registars like network solutions require this, your config file will be identical for the two servers so you don't have to worry about that. If you want any more info post back here, I feel bad that tinydns is not used more as it is so much better than Bind ever dreamed of being, I have written a nice web based frontend for tinydns I will be releasing open source on freshmeat in the near future that makes using tinydns almost brainless and makes it easier to manage a couple thousand domains but it probably wouldn't be worth it for you if you are only running a few domains. |
I also wanted to post a more compleate example of the records you need to setup a domain in tinydns so I am pasting one of the domains from my config.
Code:
.233.174.63.in-addr.arpa::dns1.yourdomain.net::259200 Also if you are in control of the ip address' for your subnet then you need to be able to do reverse lookups for mail coming in and ect. That is what the first line is so in the example above I am saying I am in control and can answer for any ip address' in the 63.174.233.0-255 range, you just have to list the ip backwards as you see and just not put in the last number (the 0). Also one more thing that is in here that was not in my first example is the line: +domain1.com:63.174.233.151:86400:::: This line is here so you can just go to http://domain1.com in case someone doesn't put in the www or you are too lazy to type in the whole thing. |
All times are GMT -5. The time now is 04:03 AM. |