I can't see wanting to use network traffic and another machine having to serve out information to resolve local hosts, when it is so easy to keep each machine's local copy of /etc/hosts current. Plus I can't see using a relatively non-security-examined dns server, when the standard dns server has had so much security scrutiny. We've already solved the problem of keeping /etc/hosts current throughout a cluster in oscar, let's not change out standard system software for something relatively untried just to get rid of something that already works.

At 10:31 AM 2/7/2003 -0500, Sean Dague wrote:
I just got turned onto a new piece of software, dnsmasq, and I really think
this could make life a lot easier for the oscar environment.
http://thekelleys.org.uk/dnsmasq/doc.html

Basically, it reads /etc/hosts on the node it is run, and serves dns queries
(forward and reverse) from it.  If a query for something not in /etc/hosts
is asked for, it goes just proxies the query out.  It has lots of good
features in it, but mostly, it would mean *not* having to propogate
/etc/hosts to every host every time something changed.  This would be
goodness IMHO.

        -Sean

--
_______________________________________________________________________

Sean Dague                [EMAIL PROTECTED]               http://dague.net

There is no silver bullet.  Plus, werewolves make better neighbors than
zombies, and they tend to keep the vampire population down.
_______________________________________________________________________


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Oscar-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/oscar-devel

Reply via email to