Hi Simon,
Thank you for your quick reply and explanation :-)
FYI, I've found one of your answer about this topic, 5 years ago :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579536#10
About changing the behavior, I think adding an option allowing to choose
which kind of queries must be
Sorry, didn't get correct understanding of your setup from first mail,
though now it seems to have good enough description.
Anyway, I believe it is local apps (or rather a name resolving library ?)
that are issuing original query for dupaa.com.mhouse.lh, not the caching
dnsmasq on your PC.
Hi Simon;
Thanks for the response below. I have a following question for 2.
1: I am thinking about how best to utilize dnsmasq in an amazon cloud
deployment.
I don't think I can circumvent Amazons DHCP system. Any idea how I'd mate the
aws
DHCP system to the dnsmasq dns solution ?? Perhaps
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/08/2016 07:46 AM, Ptits de Barbe wrote:
> I believe you've wrongly interpreted the log. Let me describe how do I
> understand it.
>> 15:45:32.035381 IP 127.0.0.1.18520 > 127.0.2.1.5353: 1536+ A (QM)?
>> dupaa.com. (27)
> Something running on
Hi,
On Sat, Sep 6, 2014 at 6:55 PM, Simon Kelley wrote:
> On 29/08/14 08:59, Rene Bartsch wrote:
>> Hi,
>>
>> I'm running Dnsmasq with DNSSEC-validation and "--dnssec-check-unsigned"
>> enabled. "server=/onion/127.0.0.1#9053" forwards .onion-queries to the
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/08/2016 03:30 PM, wkitt...@gmail.com wrote:
> On 01/08/2016 07:29 AM, Mikhail Morfikov wrote:
>>> Also, though I don't see further log, I suspect that there were no requests
>>> like
>> That's the full log. I mean, this is what happened after
On 01/08/2016 07:29 AM, Mikhail Morfikov wrote:
Also, though I don't see further log, I suspect that there were no requests like
That's the full log. I mean, this is what happened after trying to use
"ping dupaa.com".
perhaps you should have used "ping dupaa.com." instead?
in one of my other