March 21st, 2002, 07:47 PM
don't understand DNS with djndns...
Let's say, I am pretty lost with understand how DNS works.. I wanted to install and use djbdns, so do I have to use dnscache to make tinydns works? Because, it said that dnscache and tinydns can't have same IP, so I only has one static IP and a box.
From what I understand follows:
Install daemontools then create /var/service and copy startup script & put in rc.d..
1) Install djbdns
2) create three user (djncache, tinydns and dnslog) with no login in djbdns group.
3) follow http://cr.yp.to/djbdns/faq/cache.html#config
4) follow http://cr.yp.to/djbdns/faq/tinydns.html#config
5) edit /etc/resolv.conf
6) edit /etc/namedb/namedb.conf .. should I bother namedb.root too?
setup ns.domain.com in my domain's setting..
I think, I am going to start all over again and read then try it again to see if I will understand it more clearly..
March 21st, 2002, 08:06 PM
If you can't use the same ip, I'm personally not sure why, why don't you setup dnscache with 127.0.0.1. Is this computer a gateway for a network that needs dnscache to resolve domains? I was setting this up at school and found this tutorial the most helpful yet. Just to get started with it, after that you need to go to www.lifewithdjbdns.org to see how to add domains and everything.
Here's the link:
March 23rd, 2002, 10:15 AM
>> so do I have to use dnscache to make tinydns works?
No. dnscache is caching nameserver for /etc/resolv.conf. You can never put tinydns's authoritative nameserver into /etc/resolv.conf.
If you run tinydns for a domain to be reachable by others, you need to run it on your external IP, and on UDP 53, no others. Then you can't run dnscache on UDP 53 any longer because it's already in use by tinydns.
Though you can run dnscache on 127.0.0.1 but that's DNS queriable only within the same box (LAN machines can't).
If you run dnscache on 192.168.0.1, you need to run multiple tinydns (if you read my other posts, I called that localdns instead), one for external and one for 192.168.0.x. You don't need to run master+slave for localdns, since it's for local-use only.
Because running tinydns on LAN requires you to use 192.168.0.1 as well, therefore localdns can't coexist with dnscache on the same IP (192.168.0.1). If you don't have another box for localdns, you can set alias to your NIC to create 192.168.0.2 for that.
March 24th, 2002, 02:16 PM
ok, thanks! All I will using tinydns just to reach my domain, that's all..