Linux systemd-resolve占用53端口的解决方法

最新推荐文章于 2025-03-23 13:02:55 发布

神尾观铃酱

最新推荐文章于 2025-03-23 13:02:55 发布

阅读量2.3w

点赞数 9

分类专栏： linux 文章标签： ubuntu

原文链接：https://www.itren.org/319.html

版权

linux 专栏收录该内容

1 篇文章

订阅专栏

在Linux系统中有些软件（如：Dnsmasq解锁Netflix中的Dns等服务）可能要用到53的端口，但有些系统提示已使用（required port 53 already in use ）。

使用**“netstat -tlunp|grep 53**”查看53端口是不是systemd-resolved占用了。如果是，下面是解决方法可以试试看对你有没有帮助。

1、先停用 systemd-resolved 服务

systemctl stop systemd-resolved

2、编辑 /etc/systemd/resolved.conf 文件

vi /etc/systemd/resolved.conf

3、换下面说明更改，然后按一下“esc”键，再输入“:wq”（不要输入引号），回车保存即可。

[Resolve]
DNS=8.8.8.8  #取消注释，增加dns
#FallbackDNS=
#Domains=
#LLMNR=no
#MulticastDNS=no
#DNSSEC=no
#Cache=yes
DNSStubListener=no  #取消注释，把yes改为no

4、最后运行下面命令即可。

ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf

确定要放弃本次机会？

福利倒计时

: :

立减 ¥

普通VIP年卡可用

立即使用

神尾观铃酱

关注关注

9
点赞
踩
40

收藏

觉得还不错? 一键收藏
1
评论
分享

复制链接

分享到 QQ

分享到新浪微博

扫一扫
举报

举报

专栏目录

Linux 服务器上 systemd-r 进程占用53端口解决方案

liulilittle的博客

04-06

2068

编辑配置文件LLMNR=0停止服务禁用服务。

Ubuntu系统，怎么使/etc/resolved.conf生效

PoppuHengheng的博客

03-13

527

因为自己本地需要修改一下/etc//etc/resolv.conf，但是发现每次修改后，重新启动服务，/etc//etc/resolv.conf的修改就会reset。通过上面的命令，可以使对网络配置的修改生效。

1 条评论您还未登录，请先登录后发表或查看评论

linux53端口,53端口被占用，但找不出是哪个程序占用

weixin_32940141的博客

04-30

955

└─[3] <> sudo netstat -anlp | grep -w LISTENtcp 0 0 0.0.0.0:29917 0.0.0.0:* LISTEN 1938/wineservertcp 0 0 127.0.0.1:9000 0.0.0.0:* ...

解决debian 53端口被占用禁用systemd-resolved

热门推荐

xgocn的专栏

04-17

1万+

Linux 开启热点需要使用 dnsmasq 服务，而这个服务使用 53 端口。但是 53 端口可能被占用，这是 dnsmasq 就会报错： Copy failed to create listening socket for port 53: 地址已在使用下面给出该错误的解决方案。查看占用端口情况# 终端命令查看端口占用： Copy sudo netstat -anlp | grep -w LISTEN 可以看到： Copy .......

Debian解决dnsmasq占用53端口问题

qq_46435629的博客

09-14

4383

Debian Linux解决dnsmasq占用端口问题

Linux下监听53号端口捕获DNS查询报文

私のBookShelf

04-23

2509

Linux下监听53号端口捕获DNS查询报文计算机网络课设要求写一个能正常工作的DNS resolver，这就要求写出来的解析器能监听应用程序发出的查询报文。即当应用程序需要查询某个网址对应的IP地址时，它会先往DNS resolver发送一条查询报文。这个解析器会解析这条报文，然后先在本地高速缓存中寻找有无对应的IP地址，若没有则去其他它知道的DNS服务器进行查找。获取结果后，将报文返回。在这其中，53号端口就是解析器和服务器监听的端口。使用sudo netstat -aptn | grep 53

linux53端口,Linux的DNS的53端口

weixin_39629075的博客

04-30

181

天客户那边有台服务器同一个局域网中都无法访问，排除lamp环境问题，发现时服务器中的防火墙没有开启80端口。于是去网上搜索了一下，在脚本之家看到一种添加代码的方法vi /etc/sysconfig/iptables-A INPUT -m state �state NEW -m tcp -p tcp �dport 80 -j ACCEPT(允许80端口通过防火墙)-A INPUT -m state ...

linux dns 53端口,Linux的DNS的53端口

weixin_39913422的博客

05-11

180

天客户那边有台服务器同一个局域网中都无法访问，排除lamp环境问题，发现时服务器中的防火墙没有开启80端口。于是去网上搜索了一下，在脚本之家看到一种添加代码的方法vi /etc/sysconfig/iptables-A INPUT -m state �Cstate NEW -m tcp -p tcp �Cdport 80 -j ACCEPT(允许80端口通过防火墙)-A INPUT -m stat...

YARN Registry DNS启动提示“53端口被占用”错误的解决方法

weixin_30470643的博客

07-05

3858

错误提示： ERROR dns.PrivilegedRegistryDNSStarter (PrivilegedRegistryDNSStarter.java:init(61)) - Error initializing Registry DNSjava.net.BindException: Problem binding to [xxx:53] java.net.BindException: ...

Windows 53端口被占用，虚拟网卡打开失败

freedom2211的博客

10-23

3449

登录vpn失败，提示虚拟网卡打开失败。查看网络适配器，虚拟网卡tap windows adapter v9 网络电缆被拔出怎么也无法启动。经过多方查找解决方法，终于启动成功，记录一下。

linux部署校园网绕过53端口服务脚本

m0_48096446的博客

11-10

1031

适用于Ubuntu、Debian、AlmaLinux、Rocky Linux、CentOS和Fedora的OpenUPN 安装程序。该脚本将在不到一分钟的时间内为您设置自己的虚拟网络服务器，即使您以前没有使用过Open虚拟网络。它被设计为尽可能不引人注目和通用。新建这个脚本，　写入最后的内容。

53端口被占用，ICS服务关不掉 [已解决]

shisanxiang_的博客

10-17

832

解决 53端口被占用，ICS服务关不掉

如何关闭linux系统的53端口,3种关闭linux系统端口方法(示例代码)

weixin_42523389的博客

04-29

6170

下面总结三种关闭linux系统端口的方法1、通过杀掉进程的方法来关闭端口每个端口都有一个守护进程，kill掉这个守护进程就可以了每个端口都是一个进程占用着，第一步、用下面命令netstat -anp |grep 端口找出占用这个端口的进程，第二步、用下面命令kill PID杀掉就行了2、通过开启关闭服务的方法来开启/关闭端口因为每个端口都有对应的服务，因此要关闭端口只要关闭相应的服务就可以了。...

linux Web server failed to start. Port 10023 was already in use 端口被占用 kill -9 不管用杀不吊

02-28

### Linux Web Server Port Already In Use and Kill Command Not Working When encountering a situation where the web server cannot start because port 10023 is occupied by another process, and using `kill -9` does not terminate this process effectively, several strategies can help resolve the issue. A common misconception might lead one to believe that simply killing the offending process would free up the port immediately; however, sometimes processes do not respond as expected or may restart automatically depending on how they are managed within the system. Instead of relying solely on forceful termination methods like `kill -9`, consider these alternatives: #### Verify Process Ownership Firstly, identify which application owns the problematic port with greater precision than just finding its PID (Process ID). This approach ensures no critical services are inadvertently disrupted when attempting resolution actions. ```bash sudo lsof -i :10023 ``` This command lists all connections associated with port 10023 along with detailed information about each connection including owner details[^1]. #### Adjust Kernel Parameters Temporarily If binding issues arise due to kernel restrictions such as those mentioned regarding non-local IP bindings, adjusting relevant parameters temporarily could provide relief without modifying core configurations permanently: ```bash echo "1" | sudo tee /proc/sys/net/ipv4/ip_nonlocal_bind ``` Note that changing certain settings requires administrative privileges and should only occur after careful consideration since it affects network behavior globally across the entire machine. #### Restart Network Services Gracefully Instead of forcefully terminating specific PIDs via `kill -9`, restarting networking components gracefully often resolves lingering socket states more reliably while minimizing potential side effects: ```bash sudo systemctl restart network-manager.service # Or for older systems using init.d scripts instead of systemd units sudo service network-manager restart ``` For cases involving database listeners specifically bound to particular ports similar to what was described concerning Oracle instances listening on custom ports outside default ranges[^2]: - Ensure proper configuration files reflect intended operational modes post-restart. - Validate firewall rules permit necessary traffic patterns through specified endpoints before assuming connectivity problems stem from local resource conflicts alone. By following above suggestions rather than exclusively focusing on brute-force approaches towards managing stuck resources, smoother resolutions become attainable even under challenging circumstances encountered during troubleshooting sessions related to web servers operating inside Linux environments.