On Wed, May 04, 2022 at 01:00:36PM -0700, Linus Torvalds wrote:
> On Wed, May 4, 2022 at 12:51 PM Linus Torvalds
> <[email protected]> wrote:
> >
> > But I don't think that it's the browser, actually. Even 'nslookup'
> > refuses to touch it with
> >
> > ** server can't find א.cc: SERVFAIL
> >
> > and it seems it's literally the local dns caching (dnsmasq?)
>
> Looks like Fedora builds dnsmasq with 'no-i18n', although "dnsmasq -v"
> also shows "IDN2", so who knows.. Maybe it's some default config issue
> rather than the build configuration.
>
> Linus
Which version of Fedora? I use a pretty vanilla Fedora 34 install and it seems to
be working ok for me.
shorne@antec $ dig +short א.cc
147.75.79.213
shorne@antec $ nslookup א.cc
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
Name: א.cc
Address: 147.75.79.213
Name: א.cc
Address: 2604:1380:1:4d00::5
shorne@antec $ /lib64/ld-linux-x86-64.so.2 --version
ld.so (GNU libc) release release version 2.33.
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
shorne@antec $ cat /etc/redhat-release
Fedora release 34 (Thirty Four)
-Stafford
On Wed, May 4, 2022 at 1:12 PM Stafford Horne <[email protected]> wrote:
>
> Which version of Fedora?
F35 here.
But looking further, it's not dnsmasq either. Yes, dnsmasq is built
with no-i18n, but as mentioned IDN2 does seem to be enabled, so I
think it's just "no i18n messages".
It seems to be the upstream dns server.
Using 8.8.8.8 explicitly makes it work for me, and that obviously
bypasses not just the local dns cache, but also the next dns server
hop.
Could be anywhere. Xfinity, Nest WiFi, or the cable router. They all
are doing their own dns thing.
Probably my cable box, since it's likely the oldest thing in the chain.
Linus