DNS ошибка в конце настройки (connection timed out; no servers could be reached)

0

1

Настроил DNS, конфиги. Впервые в жизни. Тут проблема:

Пишу команду dig vk.com ответ ; «» DiG 9.16.20-RH «» vk.com ;; global options: +cmd ;; connection timed out; no servers could be reached

в sudo systemctl status named ошибок нет

named.service - Berkeley Internet Name Domain (DNS) Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled) Active: active (running) since Thu 2021-09-16 13:06:03 +05; 13min ago Main PID: 46320 (named) Tasks: 8 (limit: 4664) Memory: 24.2M CPU: 97ms CGroup: /system.slice/named.service └─46320 /usr/sbin/named -u named -c /etc/named.conf

сен 16 13:06:03 fedora named[46320]: zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6> сен 16 13:06:03 fedora named[46320]: zone 1.0.0.127.in-addr.arpa/IN: loaded serial 0 сен 16 13:06:03 fedora named[46320]: zone localhost.localdomain/IN: loaded serial 0 сен 16 13:06:03 fedora named[46320]: zone dns01.fedora.local/IN: loaded serial 2011071001 сен 16 13:06:03 fedora named[46320]: zone 5.168.192.in-addr.arpa/IN: loaded serial 2011071001 сен 16 13:06:03 fedora named[46320]: all zones loaded сен 16 13:06:03 fedora named[46320]: running сен 16 13:06:03 fedora systemd[1]: Started Berkeley Internet Name Domain (DNS). сен 16 13:06:03 fedora named[46320]: managed-keys-zone: Key 20326 for zone . is now trusted (acceptance timer> сен 16 13:06:03 fedora named[46320]: resolver priming query complete

sudo nano /etc/named.conf

options { listen-on port 53 { 192.168.5.1; 192.168.122.214; }; listen-on-v6 port 53 { ::1; }; directory «/var/named»; dump-file «/var/named/data/cache_dump.db»; statistics-file «/var/named/data/named_stats.txt»; memstatistics-file «/var/named/data/named_mem_stats.txt»; secroots-file «/var/named/data/named.secroots»; recursing-file «/var/named/data/named.recursing»; allow-query { localhost; 192.168.122.214;};

    /*
     - If you are building an AUTHORITATIVE DNS server, do NOT enable recursion.
     - If you are building a RECURSIVE (caching) DNS server, you need to enable
       recursion.
     - If your recursive DNS server has a public IP address, you MUST enable access
       control to limit queries to your legitimate users. Failing to do so will
       cause your server to become part of large scale DNS amplification
       attacks. Implementing BCP38 within your network would greatly
       reduce such attack surface
    */
    recursion yes;

   recursion yes;

    dnssec-validation yes;

    managed-keys-directory "/var/named/dynamic";
    geoip-directory "/usr/share/GeoIP";

    pid-file "/run/named/named.pid";
    session-keyfile "/run/named/session.key";

    /* https://fedoraproject.org/wiki/Changes/CryptoPolicy */
    include "/etc/crypto-policies/back-ends/bind.config";

};

logging { channel default_debug { file «data/named.run»; severity dynamic; }; }; zone «dns01.fedora.local» IN { type master; file «forward.fedora.local»; allow-update { none; }; };

zone «5.168.192.in-addr.arpa» IN { type master; file «reverse.fedora.local»; allow-update { none; }; };

include «/etc/named.rfc1912.zones»; include «/etc/named.root.key»;

sudo nano /etc/resolv.conf

nameserver 192.168.5.1 options edns0 trust-ad search isc.org

Также этот адресс (из конфига) не пингуется с другой виртуалки в той же сети