Hey Simon,
I was assuming dnsmasq was sending the address to the client as it was able to
resolve the page (as in able to access it). However, this could very well have
been caused by the client sending out multiple queries and at least one of the
were answered with IPs.
This seems to be the
On 01/03/2019 20:33, Simon Kelley wrote:
>
> What's worrying is that Cloudflare and Google are both quite happy that
> the answer is _not_ bogus, but dnsmasq thinks it is. I shall poke around
> some more to try and understand that.
>
>
>
Answering myself, this appears to be a cloudflare bug,
On 01/03/2019 18:56, Dominik DL6ER wrote:
> Dear list members,
>
> to my understanding, dnsmasq should not return any valid records for BOGUS
> domains.
> However, using Cloudflare (1.1.1.1 / 1.0.0.1) as upstream, I see a domains
> being
> validated as BOGUS in the log, however, the A query
Dear list members,
to my understanding, dnsmasq should not return any valid records for BOGUS
domains.
However, using Cloudflare (1.1.1.1 / 1.0.0.1) as upstream, I see a domains being
validated as BOGUS in the log, however, the A query still succeeds and the
client
receives valid IP addresses.
