Dear Geert,
On Fri, 2022-04-15 at 10:17 +0200, Geert Stappers via Dnsmasq-
discuss wrote:
> > - log_query_mysockaddr(F_NOEXTRA | F_DNSSEC,
> > daemon->namebuff, >addr,
> > - "dnssec-retry", (forward-
> > >flags & FREC_DNSKEY_QUERY) ? T_DNSKEY :
On Sun, Apr 17, 2022 at 12:51:42PM +0200, Dominik Derigs wrote:
> On Fri, 2022-04-15 at 10:17 +0200, Geert Stappers wrote:
> > 2022-04-10, Dominik Derigs wrote:
} } } Subject: [PATCH] Also log upstream port for dnssec-retry
} } there should be more text about the why.
> > > -
On Sat, Apr 16, 2022 at 08:13:27PM +0300, Анна Тихомирова via Dnsmasq-discuss
wrote:
> Hello.
>
> I'm using dnsmasq version 2.86.
>
> I've found that address option works incorrectly if the target domain is a
> cname.
>
> Here is an example:
>
> 1) Add a domain to dnsmasq configuration:
>
>
17.04.2022 12:36, Geert Stappers via Dnsmasq-discuss пишет:
1) Add a domain to dnsmasq configuration:
address=/api.ott.kinopoisk.ru/::
???
Is
address=/api.ott.kinopoisk.ru/::1
meant?
No, :: is meant (null address). It is used to selectively block IPv6 for
specific domains.
Thanks to the list for the suggestions, I was indeed able to get the TXT
request working properly. I tried to reply to the list but it appears
that now having DKIM on my domain is blocking messages to the list
(maybe, we'll see if this one goes through) or otherwise the list policy
has gotten
