On 9/18/2007, xerces8 (xerc...@butn.net) wrote:
Simple : Do not do any changes to a working system, except the really
necessary ones.
This is so in any serious system.
Of course, I agree that you shouldn't just update willy nilly for no
reason at all, but when there is a *reason* - like, for
Simon Kelley wrote:
HOWEVER, if a situation arises where DHCP requests are being delayed,
then dnsmasq temporarily abandons doing the ping checks, so under no
circumstances will DHCP transaction be delayed long enough for a
client to time-out.
Ahh, cool... thanks!
--
Best regards,
Charles
Thanks to everyone for answering my questions about DNSMasq...
It looks like I'll definitely have to plan on installing djbdns+dnscache
alongside DNSMasq, but I think it'll be a good fit for our us...
The only real issue I see is the fact that the DHCP side is not
multi-threaded - any plans f
I started, but never sent this message, but am still curious as to the
answers I might get...
Releases before 2.35 will choke reading a file this big. The code was
re-written in 2.35 to make it usable. (and also to re-size the hash
table based on the size
Edson wrote:
Then try this approach:
Internet <-> OpenDNS <-> [DNSmasq<->SMTP+SAMBA]
\-> DNSMasq <->LAN
This is not what I want, but your graphical representation helped to
clarify what I *do* want. The main point is, I do NOT want my smtp
server to use the OpenDNS serve
Hi Jon,
Thanks for the reply... I'd like to keep this on list if you don't mind...
Jon wrote:
Not sure if I fully understand your question, but the killer feature of
DNSMasq for me is that it will return addresses from the /etc/hosts file
as responses to DNS queries from machines on the networ
Hello,
Hopefully this isn't too dumb of a question (I'm kind of new to running
my own smtp server)...
I have been lurking for a couple of weeks, and am convinced that I just
have to deploy DNSMasq on a test server and see if it will be an
excellent!! option for use on a new Samba server I wi
