LINUX.ORG.RU
решено ФорумAdmin

Не работает локальный dns

 , ,


0

1

В resolv.conf оригинальный dns заменил на адрес локалхоста. dnsmasq на месте. Но пинг по нему не проходит: ping: yandex.ru: временная ошибка в разрешении имен Уже голову сломал. Я по ходу что-то очень важное пропустил, хотя в гайде, на который ориентируюсь, все ровно так же и работает

Upd: все заработало, благодарствую.



Последнее исправление: Mr_Hydus (всего исправлений: 1)

Ответ на: комментарий от Entmatix

Содержимое /var/log/syslog:

Apr 27 16:37:04 tor-gate kernel: [ 0.000000] Linux version 5.10.0-13-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.106-1 (2022-03-17) Apr 27 16:37:04 tor-gate kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-13-amd64 root=UUID=2148b192-ee70-4374-8874-6e9a62610fee ro quiet Apr 27 16:37:04 tor-gate kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: ‘x87 floating point registers’ Apr 27 16:37:04 tor-gate kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: ‘SSE registers’ Apr 27 16:37:04 tor-gate kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: ‘AVX registers’ Apr 27 16:37:04 tor-gate kernel: [ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Apr 27 16:37:04 tor-gate kernel: [ 0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using ‘standard’ format. Apr 27 16:37:04 tor-gate kernel: [ 0.000000] BIOS-provided physical RAM map: Apr 27 16:37:04 tor-gate kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable Apr 27 16:37:04 tor-gate kernel: [ 0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved Apr 27 16:37:04 tor-gate kernel: [ 0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved Apr 27 16:37:04 tor-gate kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000003ffdffff] usable Apr 27 16:37:04 tor-gate kernel: [ 0.000000] BIOS-e820: [mem 0x000000003ffe0000-0x000000003fffffff] reserved Apr 27 16:37:04 tor-gate kernel: [ 0.000000] BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved Apr 27 16:37:04 tor-gate kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved Apr 27 16:37:04 tor-gate kernel: [ 0.000000] NX (Execute Disable) protection: active Apr 27 16:37:04 tor-gate kernel: [ 0.000000] SMBIOS 2.8 present. Apr 27 16:37:04 tor-gate kernel: [ 0.000000] DMI: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014 Apr 27 16:37:04 tor-gate kernel: [ 0.000000] Hypervisor detected: KVM Apr 27 16:37:04 tor-gate kernel: [ 0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00 Apr 27 16:37:04 tor-gate kernel: [ 0.000000] kvm-clock: cpu 0, msr 226b8001, primary cpu clock Apr 27 16:37:04 tor-gate kernel: [ 0.000000] kvm-clock: using sched offset of 10169479888 cycles Apr 27 16:37:04 tor-gate kernel: [ 0.000005] clocksource: kvm-clock: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns Apr 27 16:37:04 tor-gate kernel: [ 0.000010] tsc: Detected 3192.604 MHz processor Apr 27 16:37:04 tor-gate kernel: [ 0.000670] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved Apr 27 16:37:04 tor-gate kernel: [ 0.000672] e820: remove [mem 0x000a0000-0x000fffff] usable Apr 27 16:37:04 tor-gate kernel: [ 0.000675] last_pfn = 0x3ffe0 max_arch_pfn = 0x400000000 Apr 27 16:37:04 tor-gate kernel: [ 0.000697] MTRR default type: write-back Apr 27 16:37:04 tor-gate kernel: [ 0.000698] MTRR fixed ranges enabled: Apr 27 16:37:04 tor-gate kernel: [ 0.000699] 00000-9FFFF write-back Apr 27 16:37:04 tor-gate kernel: [ 0.000700] A0000-BFFFF uncachable Apr 27 16:37:04 tor-gate kernel: [ 0.000700] C0000-FFFFF write-protect Apr 27 16:37:04 tor-gate kernel: [ 0.000701] MTRR variable ranges enabled: Apr 27 16:37:04 tor-gate kernel: [ 0.000702] 0 base 0080000000 mask FF80000000 uncachable Apr 27 16:37:04 tor-gate kernel: [ 0.000702] 1 disabled Apr 27 16:37:04 tor-gate kernel: [ 0.000703] 2 disabled Apr 27 16:37:04 tor-gate kernel: [ 0.000704] 3 disabled

Sockstat:

USER PROCESS PID PROTO SOURCE ADDRESS FOREIGN ADDRESS STATE avahi avahi-daemon 1307 udp4 :5353 : CLOSED avahi avahi-daemon 1307 udp6 :::5353 ::: CLOSED avahi avahi-daemon 1307 udp4 :39647 : CLOSED avahi avahi-daemon 1307 udp6 :::50167 ::: CLOSED root NetworkManager 1359 raw6 :::58 :::* CLOSED root NetworkManager 1359 udp4 192.168.122.183:68 192.168.122.1:67 ESTABLISHED root cupsd 1411 tcp6 ::1:631 :::* LISTEN root cupsd 1411 tcp4 127.0.0.1:631 : LISTEN root cups-browsed 1431 udp4 :631 : CLOSED root saned 1461 tcp6 :::6566 ::: LISTEN root tor 3438 tcp4 127.0.0.1:9050 : LISTEN root tor 3438 udp4 *:5353 : CLOSED root tor 3438 udp4 127.0.0.1:5353 : CLOSED root tor 3438 tcp4 *:9040 : LISTEN root tor 3438 tcp4 127.0.0.1:9040 : LISTEN root dnsmasq 3878 udp4 :53 : CLOSED root dnsmasq 3878 tcp4 :53 : LISTEN root dnsmasq 3878 udp6 :::53 ::: CLOSED root dnsmasq 3878 tcp6 :::53 ::: LISTEN

resolve.conf:

nameserver 127.0.0.1

Mr_Hydus
() автор топика
Ответ на: комментарий от Mr_Hydus

И давай из journald лог на юнит dnsmasq. Можно еще dig на какой нибудь google.com.

Entmatix
()

dnsmasq не умеет в корневые сервера, ему нужен какой-то сервер типа бинда который это умеет.

anc ★★★★★
()
Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.