집에서 Wi-Fi를 사용할 때 네트워크 관리자가 올바른 이름 서버에 대한 연결이 계속 끊어집니다. 완전히 연락이 끊긴 것 같지만,연결을 끊다그리고연결하다수동으로 최소한 몇 분 동안 인터넷에 액세스할 수 있도록 허용했습니다.
이제 내 방법에 문제가 있는 것 같습니다.구성 파일 구문 분석문서.
첫째, 그것들이 많이 있습니다.
find / -name "resolv.conf" ->
/lib/systemd/resolv.conf
/run/NetworkManager/resolv.conf
/run/resolvconf/resolv.conf
/run/systemd/resolve/resolv.conf
/etc/resolv.conf
대부분은 물론 systemd 또는 NetworkManager에 의해 생성되며 다음과 같습니다(/run/NetworkManager/resolv.conf).
# Generated by NetworkManager
search speedport.ip # name of my router
nameserver 127.0.0.53 # sounds weird to me
그러나 /run/systemd/resolve/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 directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# 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 fe80::1%3
nameserver 192.168.2.1
search speedport.ip
내 질문은 다음과 같습니다
- 이 파일 중 어떤 파일이 어떤 역할을 하는지 아는 사람이 있나요?
- 모두가 동일한 네임서버를 가리키도록 하려면 어떻게 해야 합니까?
- 복잡성을 덜 제어하기 위해 그 수를 줄일 수 있습니까?
일부 항목은 journalctl --follow다음과 같습니다.
Dez 30 14:49:18 name_machine: NetworkManager[1157]: <info> [1546177758.3092] manager: NetworkManager state is now CONNECTED_GLOBAL
Dez 30 14:49:18 name_machine: nm-dispatcher[6450]: req:3 'connectivity-change': new request (1 scripts)
Dez 30 14:49:18 name_machine: systemd[1]: Started Network Manager Script Dispatcher Service.
Dez 30 14:49:18 name_machine: systemd[1]: Starting resolvconf-pull-resolved.service...
Dez 30 14:49:18 name_machine: systemd[1]: Started resolvconf-pull-resolved.service.
Dez 30 14:49:18 name_machine: nm-dispatcher[6450]: req:3 'connectivity-change': start running ordered scripts...
Dez 30 14:49:18 name_machine: dhclient[6437]: DHCPACK of 192.168.2.100 from 192.168.2.1
Dez 30 14:49:18 name_machine: NetworkManager[1157]: <info> [1546177758.4251] dhcp4 (wlp3s0): address 192.168.2.100
Dez 30 14:49:18 name_machine: NetworkManager[1157]: <info> [1546177758.4251] dhcp4 (wlp3s0): plen 24 (255.255.255.0)
Dez 30 14:49:18 name_machine: NetworkManager[1157]: <info> [1546177758.4252] dhcp4 (wlp3s0): gateway 192.168.2.1
Dez 30 14:49:18 name_machine: NetworkManager[1157]: <info> [1546177758.4252] dhcp4 (wlp3s0): lease time 1814400
Dez 30 14:49:18 name_machine: NetworkManager[1157]: <info> [1546177758.4252] dhcp4 (wlp3s0): nameserver '192.168.2.1'
Dez 30 14:49:18 name_machine: NetworkManager[1157]: <info> [1546177758.4252] dhcp4 (wlp3s0): domain name 'speedport.ip'
Dez 30 14:49:18 name_machine: NetworkManager[1157]: <info> [1546177758.4252] dhcp4 (wlp3s0): state changed unknown -> bound
Dez 30 14:49:18 name_machine: avahi-daemon[1073]: Joining mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.2.100.
Dez 30 14:49:18 name_machine: avahi-daemon[1073]: New relevant interface wlp3s0.IPv4 for mDNS.
Dez 30 14:49:18 name_machine: avahi-daemon[1073]: Registering new address record for 192.168.2.100 on wlp3s0.IPv4.
Dez 30 14:49:18 name_machine: NetworkManager[1157]: <info> [1546177758.4271] policy: set 'WLAN-235212' (wlp3s0) as default for IPv4 routing and DNS
Dez 30 14:49:18 name_machine: nm-dispatcher[6450]: req:4 'dhcp4-change' [wlp3s0]: new request (1 scripts)
Dez 30 14:49:18 name_machine: nm-dispatcher[6450]: req:4 'dhcp4-change' [wlp3s0]: start running ordered scripts...
Dez 30 14:49:18 name_machine: dhclient[6437]: bound to 192.168.2.100 -- renewal in 854872 seconds.
Dez 30 14:49:18 name_machine: systemd[1]: Starting resolvconf-pull-resolved.service...
Dez 30 14:49:18 name_machine: systemd[1]: Started resolvconf-pull-resolved.service.
Dez 30 14:49:18 name_machine: NetworkManager[1157]: <info> [1546177758.5837] audit: op="statistics" arg="refresh-rate-ms" pid=2520 uid=1000 result="success"
Dez 30 14:49:18 name_machine: avahi-daemon[1073]: Registering new address record for 2003:ec:2bd0:b0a8:110f:592c:4811:b09a on wlp3s0.*.
Dez 30 14:49:19 name_machine: packagekitd[2722]: Starting pkgProblemResolver with broken count: 0
Dez 30 14:49:19 name_machine: packagekitd[2722]: Starting 2 pkgProblemResolver with broken count: 0
Dez 30 14:49:19 name_machine: packagekitd[2722]: Done
Dez 30 14:49:19 name_machine: PackageKit[2722]: get-updates transaction /10897_cdbececd from uid 1000 finished with success after 442ms
Dez 30 14:49:19 name_machine: NetworkManager[1157]: <info> [1546177759.9389] audit: op="statistics" arg="refresh-rate-ms" pid=2520 uid=1000 result="success"
Dez 30 14:54:17 name_machine: kernel: wlp3s0: AP bc:30:d9:8a:2e:8c changed bandwidth, new config is 2462 MHz, width 1 (2462/0 MHz)
NetworkManager가 말하는 곳: dhcp4 (wlp3s0): nameserver '192.168.2.1'그리고 dhcp4 (wlp3s0): domain name 'speedport.ip'.
127.0.0.53이것이 의미가 있는지, 서로 얼마나 관련이 있는지는 모르겠습니다 . 192.168.2.1그것은 무엇을 fe80::1%3의미 합니까 127.0.0.53? 이 경우 특정 파일의 네임서버 순서에 어떻게 영향을 미치나요? 어떤 아이디어라도 환영합니다.
답변1
표준 파일은 /etc/resolv.conf심볼릭 링크일 수 있습니다.
예를 들어 CentOS 7의 경우:
% ls -l /etc/resolv.conf
-rw-r--r-- 1 root root 70 Dec 9 10:57 /etc/resolv.conf
% cat /etc/resolv.conf
# Generated by NetworkManager
search spuddy.org
nameserver 10.0.0.134
데비안 9에서
% ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 35 Dec 21 23:05 /etc/resolv.conf -> /var/run/NetworkManager/resolv.conf
% cat /etc/resolv.conf
# Generated by NetworkManager
search spuddy.org
nameserver 10.0.0.134
systemd-resolved이제 127.0.0.53은 스텁 DNS 수신기가 제공하는 특수 항목 systemd이며 컴퓨터의 DNS 서버 역할을 합니다. 그래서예이는 귀하의 컴퓨터에 대한 올바른 DNS 항목일 수 있습니다.
다음 명령을 사용하여 사용 중인 서버를 알 수 있습니다. 예를 들어 nslookup또는dig
% nslookup www.google.com
Server: 10.0.0.134
Address: 10.0.0.134#53
Non-authoritative answer:
Name: www.google.com
Address: 216.58.217.100
% dig www.google.com | grep SERVER
;; SERVER: 10.0.0.134#53(10.0.0.134)
두 경우 모두 10.0.0.134DNS 확인을 사용하고 있음을 알 수 있습니다.
fe80::1IPv4 주소가 아닌 "링크-로컬" IPv6 주소입니다.