Re: djbDNS help
On Mon, Jul 25, 2005 at 09:44:06AM +0200, martin f krafft wrote:
>also sprach Ritesh Raj Sarraf <riteshsarraf@users.sourceforge.net> [2005.07.25.0118 +0200]:
>> I had made tinydns run on the public ip. dnscache was running on 127.0.0.1
>> My other servers weren't able to use this DNS server because it was
>> listening only on 127.0.0.1 so I added another dnscache named dnscache-ext
>> and made it run on the same public ip where tinydns was running because I
>> didn't have another public ip on the DNS server.
>
>You cannot have tinydns and dnscache both listen on the public IP!
>Instead, let tinydns run on 127.0.0.1, dnscache on the public IP,
>configure everything to use dnscache and make sure it works, then
>configure dnscache to turn to 127.0.0.1 for the zones that tinydns
>serves.
right, if you are using something like supervise, the port 53
application that starts first will run while the other trying to use
that port will fail, but supervise restarts it, watch the pid change. As
long as you are not using tinydns for external authoritative queries,
ie have it listed in whois records for a domain, you can run it on a
localhost ip, with your dnscache on the external ip.
If you need to provide authoritative and recursive dns service, you need
two external IPs, one for dnscache and one for tinydns, configure all
your resolv.conf files to use the dnscache ip and put the tinydns ip in
the whois records.
Regards,
// George
--
George Georgalis, systems architect, administrator <IXOYE><
http://galis.org/ cell:646-331-2027 mailto:george@galis.org
Reply to: