> I'd suggest SQLite as a possibility. Easy to include, and as they
> say: "Small. Fast. Reliable. Choose any three."
SQLite was my first option, but it doesn't replicate "automatically".
Easy to set up with rsync or something like it, of course, but that
wouldn't enable two dnsmasq servers to co
On Fri, May 25, 2012 at 01:17:57PM +0200, Jan-Piet Mens wrote:
> Being very lightweight, dnsmasq must not be bloated by having
> a huge MySQL or other database attached to it.
I'd suggest SQLite as a possibility. Easy to include, and as they
say: "Small. Fast. Reliable. Choose any three."
http:/
On 25/05/12 12:17, Jan-Piet Mens wrote:
> Starting just a few days before the day the machine running dnsmasq in
> my SOHO died, I was giving some thought to how I'd go about ensuring
> a backup copy of dnsmasq could take over if my only running instance
> died. Needless to say, the death of the ma
On 25/05/12 12:14, Jan-Piet Mens wrote:
>> relaxing the hex parsing to make colons and leading zeros optional gets
>> the possibility of something that's almost an natural encoding in this
>> case, and may be generally useful if less easy to use.
>>
>> dns-rr=44,2:1:123456789abcdef67890123456789abc
On 25/05/12 14:00, Modem Man wrote:
> Can anyone tell me, if and where I can get a Debian "testing" version of
> IPv6 enabled DnsMasq for Squeeze 2.6.38.8 armv5tel?
> I don't like to compile it by myself, so I hope anybody here has contact
> to the .deb packet maintainer here , or just knows about
Can anyone tell me, if and where I can get a Debian "testing" version of
IPv6 enabled DnsMasq for Squeeze 2.6.38.8 armv5tel?
I don't like to compile it by myself, so I hope anybody here has contact
to the .deb packet maintainer here , or just knows about the state.
Same question aplies for SlugOS/
1,$s/Tryant/Tyrant/g
-JP
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Starting just a few days before the day the machine running dnsmasq in
my SOHO died, I was giving some thought to how I'd go about ensuring
a backup copy of dnsmasq could take over if my only running instance
died. Needless to say, the death of the machine left my small network in
shambles, because
> relaxing the hex parsing to make colons and leading zeros optional gets
> the possibility of something that's almost an natural encoding in this
> case, and may be generally useful if less easy to use.
>
> dns-rr=44,2:1:123456789abcdef67890123456789abcdef67890
>
> Opinions?
Go for it!
I recom
On 24/05/12 19:17, Jan-Piet Mens wrote:
>> keys as "SSHFP-Record"s, so that I'm able to call via <> user@remotehost-o "VerifyHostKeyDNS=yes">> and get a result line like
>> "Matching host key
>> fingerprint found in DNS".
>
> This may or not be painful, if you're not using DNSSEC. (You may like to
10 matches
Mail list logo
