Hi Simon,
> Answered here:
>
> http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2017q1/011068.h
> tml
Thanks for the pointer. Is there any chance I can convince you to revisit this?
I work in a high-latency office for a big company with lots of internal apps.
each on its own domain. They
On 02-Feb-2017 22:55, Simon Kelley wrote:
Modulo that, and Neil's quible, I'd love to take this as a diff.
That's what she said ?!?
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listin
Thank you Simon!
Much appreciated.
And your 2.77test1 tar along with the localise fix has just gone into
LEDE master, things should get a bit more testing there :-)
Cheers,
Kevin
On 02/02/17 16:57, Simon Kelley wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
http://thekelleys.org.u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
This may explain the Entire State of the World Today.
Simon.
On 02/02/17 17:05, Jim Alles wrote:
> Careful, we could have a fatal recursion:
>
> quible is speeled wrong.
>
> (smiley face)
>
> .ja.
>
> On Thu, Feb 2, 2017 at 8:30 AM, Simon Kell
Careful, we could have a fatal recursion:
quible is speeled wrong.
(smiley face)
.ja.
On Thu, Feb 2, 2017 at 8:30 AM, Simon Kelley
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Wow, what a lot of typos!
> ...
>
>
> Modulo that, and Neil's quible, I'd love to take this as a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=d42d4706bbcce3
b5a40ad778a5a356a997db6b34
Have fun.
Cheers,
Simon.
On 01/02/17 13:41, Kevin Darbyshire-Bryant wrote:
>
>
> On 17/01/17 04:05, Eric Luehrsen wrote:
>> Hi Kevin,
>>
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Some possible confusion here between DNS servers and DHCP servers. If
the two _DNS_ servers the OP refers to are both also DHCP servers,
then Jim's advice is good. If the OP has two DNS servers, one of which
is dnsmasq which is also acting as the DHC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I looked at this, and the man page LIES. --interface-name returns all
the addresses associated with an interface.
Question: is openWRT associating the same name with more than one
interface (which would be the only way that localise-queries would
ma
Hello Will,
You would need a wireshark capture to see the issue here, the log does not
tell the whole story.
It would appear that both DHCP servers are answering the clients's requests.
We don't know your network configuration, or how the ISP's 'router' is set
up to be able to say for sure.
But
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Wow, what a lot of typos!
A couple of observations from a random sampling:
1) I don't want the code changes - if I missed vowels out of variable
names, I want them to stay missed out :)
2) I found two changes to proper names, Falempin and Murname.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Answered here:
http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2017q1/011068.h
tml
Cheers,
Simon.
On 02/02/17 11:23, Aaron Jacobs wrote:
> Hi all,
>
> I've found what seems to me an odd behavior in dnsmasq related to
> CNAME caching,
Hi all,
I've found what seems to me an odd behavior in dnsmasq related to CNAME
caching, and am wondering if it's a bug, or just a subtlety of the DNS standard
that I don't understand.
I'm using dnsmasq 2.76, invoking in a way that should enable caching:
% ./src/dnsmasq -v
Dnsmasq versio
Neil Jerram wrote:
> https://github.com/jsoref/dnsmasq/commit/56dc618b840dd893a65f02df2fb14752bb7ef33d
> is wrong; the word should be 'amended'.
thanks. serves me right for occasionally doing things by hand instead
of always letting my browser suggest a correction.
updated.
https://github.com/jsoref/dnsmasq/commit/56dc618b840dd893a65f02df2fb14752bb7ef33d
is wrong; the word should be 'amended'.
Original Message
From: Josh Soref
Sent: Thursday, 2 February 2017 06:58
To: dnsmasq-discuss@lists.thekelleys.org.uk
Subject: [Dnsmasq-discuss] Spelling fixes for dnsmasq
14 matches
Mail list logo
