Looking for a Name Resolution solution

[Eric "Shubes"]

Hey L,

I understand (I think). I'd love to see a WRT54GL that does what you want,
and I can see the need.

In my case though, I prefer a more robust firewall, and use VPN capability
that IPCop provides (along with some other things I'd rather not mention).
The logging is nice too. This is beyond what most home users *need* though.
Small offices, OTOH, would find more benefit with IPCop.

In addition, I like putting perfectly good old hardware to use, even if it
is more likely to fail than something new. I certainly wouldn't waste a P4
on an IPCop. FWIW, the components most likely to fail (imo) are the HD and
PS, which are easy to replace.

Of course, one size doesn't fit all.

Take care.

Dazed_75 wrote:
> Eric,
> It may not be a big deal power wise but it seems silly to waste the
> electricity for no significant benefit.  I used to run one system all
> the time until I thought better of it.  The other side of the coin is
> this being consumer grade equipment it certainly bcomes less reliable
> over time, etc.  Even if I said ok, there are others who resist doing so
> without some good reason which I can't really give them.
> 
> On 12/20/06, *JT Moree* <moreejt at pcxperience.com
> <mailto:moreejt at pcxperience.com>> wrote:
> 
> Dazed_75 wrote:
>> In fact the first two  sentences of the reference you provide
> states it
>> DOES support local network name lookups:
>> Dnsmasq is a lightweight, easy to configure DNS forwarder and DHCP
>> server. It is designed to provide DNS and, optionally, DHCP, to a
> small
>> network. It can serve the names of local machines which are not in the
>> global DNS.
>> and I am not expecting full blown DNS.  proxying sounds like
> exacly what
>> the doctor ordered.
> 
> you do need proxy dns but you also need to add the local dns which would
> technically not be proxied.  I think that is the point he is making
> about dns proxy services not being what you want. 
> 
> 
>> Actually the dnsmasq solution does both.  All you do is some setup so
>> the DHCP Server and dnsmasq work together.  The result is that dnsmasq
>> is updated with the LAN names and IP and responds to dns queries for
>> them and acts as a proxy to forward dns requests for other things out to
>> the ISPs dns servers.  Thats why it seems so ideal.  It is exactly what
>> I would have designed as I described in an earlier email of this
>> thread.  Hell, even if the cable connection fails or the cable modem
>> dies the LAN stuff should all still function.  Using the internet fails
>> in that case but it would have anyway.
> 
>> My only concern is whether the implementation is dependable and whether
>> I would have trouble with configuration (or building from source if needed).
> 

--
-- 
-Eric 'shubes'