[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fedora-devel-list
Subject:    Re: Fedora 33 System-Wide Change proposal: systemd-resolved
From:       Andreas Tunek <andreas.tunek () gmail ! com>
Date:       2020-09-01 17:41:54
Message-ID: CALbwU3LM9uWy7OX18m_9J91zp=QysxMhf1dAdZQbL0uPCZbwTQ () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Den mån 31 aug. 2020 kl 22:40 skrev Michael Catanzaro <mcatanzaro@gnome.org
>:

> On Mon, Aug 31, 2020 at 10:19 pm, Andreas Tunek
> <andreas.tunek@gmail.com> wrote:
> > I can't get that command to do anything useful in either F32 or F33.
>
> You should see something like:
>
> $ resolvectl query example.com
> example.com: 2606:2800:220:1:248:1893:25c8:1946 -- link: tun0
>              93.184.216.34 -- link: tun0
>
> -- Information acquired via protocol DNS in 86.4ms.
> -- Data is authenticated: no
>
> And that should be working out-of-the-box in F33.
>
> > However, if I write "http://nas-name.local in F32 in either Firefox
> > or Gnome Web I can connect to my NAS, but if I write the same in F33
> > in the same programs I get an error.
>
> Ah, I bet this your NAS is mDNS, which is broken right now:
> https://bugzilla.redhat.com/show_bug.cgi?id=1867830
>
>
Thanks, I added the little info I have to the bug report.

/Andreas


> Until the root cause is diagnosed, here is a workaround you can try. As
> root, open up /etc/authselect/user-nsswitch.conf and look at the hosts
> line. In a freshly-installed F33 system, it should look like this:
>
> hosts: resolve [!UNAVAIL=return] myhostname files mdns4_minimal
> [NOTFOUND=return] dns
>
> This says: "if resolved is running, and it doesn't return a hostname,
> then STOP and don't try anything else." Everything else is listed only
> for the case where resolved is not running. But since resolved is
> currently not resolving mDNS as expected, let's change it to check with
> avahi first, then check with resolved second, like this:
>
> hosts: mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return]
> myhostname files dns
>
> Then, as root, run:
>
> # authselect apply-changes
>
> and then restart your browser. That's not the configuration we want to
> use in F33, but hopefully it will "fix" your problem. Please let me
> know if it works!
>
> Michael
>
> _______________________________________________
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-leave@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>

[Attachment #5 (text/html)]

<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">Den mån 31 aug. 2020 kl 22:40 skrev Michael Catanzaro &lt;<a \
href="mailto:mcatanzaro@gnome.org">mcatanzaro@gnome.org</a>&gt;:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">On Mon, Aug 31, 2020 at 10:19 pm, Andreas Tunek \
<br> &lt;<a href="mailto:andreas.tunek@gmail.com" \
target="_blank">andreas.tunek@gmail.com</a>&gt; wrote:<br> &gt; I can&#39;t get that \
command to do anything useful in either F32 or F33.<br> <br>
You should see something like:<br>
<br>
$ resolvectl query <a href="http://example.com" rel="noreferrer" \
target="_blank">example.com</a><br> <a href="http://example.com" rel="noreferrer" \
target="_blank">example.com</a>: 2606:2800:220:1:248:1893:25c8:1946 -- link: tun0<br> \
93.184.216.34 -- link: tun0<br> <br>
-- Information acquired via protocol DNS in 86.4ms.<br>
-- Data is authenticated: no<br>
<br>
And that should be working out-of-the-box in F33.<br>
<br>
&gt; However, if I write &quot;<a href="http://nas-name.local" rel="noreferrer" \
target="_blank">http://nas-name.local</a> in F32 in either Firefox <br> &gt; or Gnome \
Web I can connect to my NAS, but if I write the same in F33 <br> &gt; in the same \
programs I get an error.<br> <br>
Ah, I bet this your NAS is mDNS, which is broken right now: <br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1867830" rel="noreferrer" \
target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1867830</a><br> \
<br></blockquote><div><br></div><div>Thanks, I added the little info I have to the \
bug report.</div><div><br></div><div>/Andreas<br></div><div>  </div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"> Until the root cause is diagnosed, here is a \
workaround you can try. As <br> root, open up /etc/authselect/user-nsswitch.conf and \
look at the hosts <br> line. In a freshly-installed F33 system, it should look like \
this:<br> <br>
hosts: resolve [!UNAVAIL=return] myhostname files mdns4_minimal <br>
[NOTFOUND=return] dns<br>
<br>
This says: &quot;if resolved is running, and it doesn&#39;t return a hostname, <br>
then STOP and don&#39;t try anything else.&quot; Everything else is listed only <br>
for the case where resolved is not running. But since resolved is <br>
currently not resolving mDNS as expected, let&#39;s change it to check with <br>
avahi first, then check with resolved second, like this:<br>
<br>
hosts: mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] <br>
myhostname files dns<br>
<br>
Then, as root, run:<br>
<br>
# authselect apply-changes<br>
<br>
and then restart your browser. That&#39;s not the configuration we want to <br>
use in F33, but hopefully it will &quot;fix&quot; your problem. Please let me <br>
know if it works!<br>
<br>
Michael<br>
<br>
_______________________________________________<br>
devel mailing list -- <a href="mailto:devel@lists.fedoraproject.org" \
target="_blank">devel@lists.fedoraproject.org</a><br> To unsubscribe send an email to \
<a href="mailto:devel-leave@lists.fedoraproject.org" \
target="_blank">devel-leave@lists.fedoraproject.org</a><br> Fedora Code of Conduct: \
<a href="https://docs.fedoraproject.org/en-US/project/code-of-conduct/" \
rel="noreferrer" target="_blank">https://docs.fedoraproject.org/en-US/project/code-of-conduct/</a><br>
 List Guidelines: <a href="https://fedoraproject.org/wiki/Mailing_list_guidelines" \
rel="noreferrer" target="_blank">https://fedoraproject.org/wiki/Mailing_list_guidelines</a><br>
 List Archives: <a href="https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org" \
rel="noreferrer" target="_blank">https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org</a><br>
 </blockquote></div></div>


[Attachment #6 (text/plain)]

_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic