Unsubscribe me from this list
dndannang at gmail.com
Mon May 16 06:38:52 UTC 2022
On Mon, May 16, 2022, 08:33 Ron Varburg <ronvarburg at yahoo.com> wrote:
> You can got to https://lists.nlnetlabs.nl/mailman/listinfo/unbound-users.
> At the bottom of the page you can read:
> To unsubscribe from Unbound-users, get a password reminder, or change your
> subscription options enter your subscription email address: __________
> and click the unsubscribe button.
> On Monday, May 16, 2022, 08:24:12 AM GMT+3, DANIEL NANGHAKA via
> Unbound-users <unbound-users at lists.nlnetlabs.nl> wrote:
> How do I get off this mailing list?
> Am happy to be removed from it.
> On Sat, May 14, 2022, 06:36 BangDroid via Unbound-users <
> unbound-users at lists.nlnetlabs.nl> wrote:
> Kind of pulling my hair out with this one.. The domain twitterdatadash.com will
> not resolve with unbound recursively. I get SERVFAIL.
> root.hints is up to date, local time on raspi is accurate. No other
> domains are failing.
> Both dig sigfail.verteiltesysteme.net @127.0.0.1 -p 5335 and dig
> sigok.verteiltesysteme.net @127.0.0.1 -p 5335 are as expected.
> Switching to an upstream DNS in Pi-hole will get the domain to
> successfully resolve, as well as using a standard DNS forward-zone in
> name: "."
> forward-addr: 126.96.36.199
> However, if I use a DoT forward zone (because suspected possible? DNS
> hijacking by ISP):
> tls-cert-bundle: /etc/ssl/certs/ca-certificates.crt
> name: "."
> forward-addr: 188.8.131.52 at 853#cloudflare-dns.com
> forward-addr: 184.108.40.206 at 853#cloudflare-dns.com
> forward-ssl-upstream: yes
> Everything works exactly as expected, including https://220.127.116.11/help
> **except** twitterdatadash.com remains SERVFAIL.
> Paste of dig outputs with various unbound configurations:
> pi-hole.conf: https://pastebin.com/szLmcNFj
> unbound logs greped with "twitterdatadash" :
> 'default' pihole.conf : https://pastebin.com/JmgUDSRv
> with DoT: https://pastebin.com/k3UgdZD4
> Accessing that domain is not crucial by any means, I am only concerned it
> may be indicative of a bigger issue. It seems like there must be an issue
> with my configuration somewhere, but every test I run appear to indicate no
> issue. Is it possible the issue is not my end? Anyone have any ideas?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Unbound-users