Simon,
I see that you are back and wanted to bring this up again. We are using
DNSMasq within AWS to perform DNS whitelisting and I noticed that there is
no log line produced when a domain is NOT configured to be forwarded. I
think this patch should take care of it and would love to have it
> Any news on this one (and the follow up patch)?
Apologies for the radio-silence. Patches applied.
Cheers,
Simon.
signature.asc
Description: OpenPGP digital signature
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
Patch applied, thanks
(and your name is in the git-log, even if it's not in the translation..)
Cheers,
Simon.
On 17/07/17 18:53, Chris Novakovic wrote:
> On 17/07/2017 18:50, Chris Novakovic wrote:
>> Commit 730c6745 makes a number of fixes to typos, among them the
>> messages reporting
Patch tweaked so it's not active with IDN1 either, and applied. Thanks.
Simon.
On 09/08/17 21:28, Petr Menšík wrote:
> Hi Simon,
>
> this issue was fixed in libidn2 release of version 2.0.3. You workaround
> could be disabled for releases with IDN2_VERSION_NUMBER >= 0x0203.
>
> Attaching
On 25/09/17 00:24, Vic wrote:
> Hi, Can I select a domain filter or such:
>
> I send all requests to 8.8.8.8 except for
>
> mydomain1.org and mydomain2.org -- that goes to my local name servers.
>
> Yes? How?
Yes. Something like:
server=/mydomain1.org/ip.address.of.mydomain1.auth.server
