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.
--
Please do not send copies of list mail to me; I read the list!
.''`. martin f. krafft <madduck@debian.org>
: :' : proud Debian developer and author: http://debiansystem.info
`. `'`
`- Debian - when you have better things to do than fixing a system
Invalid/expired PGP (sub)keys? Use subkeys.pgp.net as keyserver!
logik ist analsadismus: gedanken werden gewaltsam
durch einen engen gang gepreßt.
-- frei nach lacan
Attachment:
signature.asc
Description: Digital signature