On 14/01/2023 19:43, Barry wrote:
> On 14 Jan 2023, at 17:02, lejeczek via users <users(a)lists.fedoraproject.org>
wrote:
>
>
>
>> On 11/01/2023 13:15, Jouk via users wrote:
>> Hi all,
>>
>> Today I upgraded my kernel form 6.0.16 to 6.0.18 on a F37 system. After rebooting
no nameservers are found at the end of /run/systemd/resoilve/resolv.conf.
>>
>> I found 2 ways to get the name resolve work again:
>> -reboot in kernel 6.0.16
>> -Change the internet adapter configuration from DHCP to Manual (and
inserting the same info as before)
>>
>> This looks to me to be a bug. (or am I wrong?)
>>
>> regards
>> Jouk
>>
> I too think - something to do with recent updates, kernel or components/services.
>
> -> $ host wp.pl
> ;; communications error to 127.0.0.53#53: connection refused
> ;; communications error to 127.0.0.53#53: connection refused
> ;; no servers could be reached
>
> Default systemd' resolver (as service) runs in stub mode.
> Suffices to:
>
> -> $ systemctl stop systemd-resolved
>
> and:
>
> -> $ host wp.pl
> wp.pl has address 212.77.98.9
> wp.pl mail is handled by 5 mx5.wp.pl.
> wp.pl mail is handled by 0 mx.wp.pl.
>
> start it again:
> -> $ systemctl start systemd-resolved
> -> $ host wp.pl
> ;; communications error to 127.0.0.53#53: timed out
> ;; communications error to 127.0.0.53#53: timed out
> ;; no servers could be reached
>
> I think it's candidate for Bugzilla report - if the author of the thread filed
one then let us know so we can chip in.
What does resolvectl report? It shows what systemd-resolved has configured.
Barry
reports as I expect it, okey.
I missed a few copy&paste, I rushed. (with multiple ifaces &
dnses in my box)
I wonder now, if it is possible, nowadays, to "bypass"
systemd's resolver - except if a separate DNS server is ran
locally.
I think DNSes - whether it is your local one or public ones
- might play a role here and I suggest you guys play with that.
perhaps the Internet(dns) is under attack :)