Por que o resolv.conf tem padrões incorretos e por que ele sempre reordena os nomes incorretos primeiro?

Instalei o resolv.conf e basicamente agora adiciona os "bons" ns à lista, mas apenas no final.

127.0.0.53 está (por exemplo) travando e expirando no github. Meu laptop na mesma rede nunca teve esse problema e parece pegar automaticamente em 192.158.1.1. Isso é apenas sorte?

Quer entender por que o padrão parece ser tão ruim aqui? E por que tantas pessoas precisam intervir manualmente. O que eles descobriram em outros sistemas?

EDITAR/ATUALIZAR:

$ ls -al /etc/resolv.conf
lrwxrwxrwx 1 root root 29 Nov 30 10:27 /etc/resolv.conf -> ../run/resolvconf/resolv.conf


$ time nslookup github.com 192.168.1.1
Server:     192.168.1.1
Address:    192.168.1.1#53

Non-authoritative answer:
Name:   github.com
Address: 192.30.253.112
Name:   github.com
Address: 192.30.253.113


real    0m0.073s
user    0m0.006s
sys 0m0.005s

$ time nslookup github.com 127.0.0.53
Server:     127.0.0.53
Address:    127.0.0.53#53

Non-authoritative answer:
Name:   github.com
Address: 192.30.253.112
Name:   github.com
Address: 192.30.253.113
;; connection timed out; no servers could be reached


real    0m15.012s
user    0m0.008s
sys 0m0.004s

$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

nameserver 127.0.0.53
nameserver 192.168.1.1

Atualização 2 após algumas sugestões de chili555:

$ ls -al /etc/resolv.conf
lrwxrwxrwx 1 root root 37 Dec  1 15:45 /etc/resolv.conf -> /run/systemd/resolve/stub-resolv.conf

$ nslookup github.com
Server:     127.0.0.53
Address:    127.0.0.53#53

** server can't find github.com: SERVFAIL

$ nslookup github.com 192.168.1.1
Server:     192.168.1.1
Address:    192.168.1.1#53

Non-authoritative answer:
Name:   github.com
Address: 192.30.253.112
Name:   github.com
Address: 192.30.253.113

$ cat /etc/resolv.conf
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "systemd-resolve --status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 127.0.0.53