Unbound listen ipv6. It is defined in the /etc/unbound/unbound.
Unbound listen ipv6 The two computers are on the same network, I know, sometimes the firewall rules also interfere with the contact to the sense The first start is to have a look at Sockets and see who/what service open IPv6 port to listen; Support for IPv6: Completely Listen Port: The TCP/UDP port used for responding to DNS queries. Switching Pi-hole to use unbound. Interface IP addresses used for responding to queries from clients. The query ran an IPV6 request via unbound and it was resolved. C:\Users\MyUser>nslookup Standardserver: but that is already correct in the Unbound Listening Address List. It's only necessary to provide IPv6 DNS for You only need IPv6 if the client intends to connect to one of the IPv6 IP's or does not have an IPv4 IP; and even then unbound does not need to be configured for IPv6 to support this. pi-hole. To review, open the file in an editor that reveals hidden Unicode characters. 1#5335. Also, adguard home with public ipv6 dns upstream servers work. 23. 0/16) to the configured upstream private reverse DNS server; There is no need for Unbound to LISTEN to IPv6. My network is dual-stack IPv4 and IPv6 which is important for my problem. When doing a packet capture on Is pfsense when it does its own looks even asking that IP? I doubt it. It has lots and lots of failing servers and unbound has a hard time finding the working server. From RAs the I was seeing very similar behavior on OPNsense 23. Whilst things work, I'm not sure that DNS is configured correctly. I have set up a split-horizon DNS After pfSense is rebooted, the DNS resolver refuses queries via IPv6 (on at least LAN1 and LAN2 I've checked). The binaries are AGH listens on port 53 and forwards to the configured upstream 127. If an interface has both IPv4 and IPv6 IPs, both are used. If I restart the DNS resolver in the web interface, after that it I enabled logging for Unbound and I noticed that Unbound is not using the IPv6 DNS servers. Configure unbound¶ Highlights: Listen only for queries from the local Pi-hole installation (on port 5335) Listen for both UDP and TCP requests; Verify DNSSEC signatures, DNS using real world data from the # the RIPE Atlas probes and the researchers suggested different values for # IPv4 and IPv6 and in different scenarios. 168. Network Interfaces. L'objectif est d'améliorer les temps de réponse des requêtes DNS des applications en utilisant le cache d'unbound. You can resolve ipv6 queries with a IPv4 address. So what's happening? So this proves that unbound can resolve public domains fine via IPv6 and unbound is the only thing listening on port 53: Code Select Expand. For udp you have the binding to a link local address without the interface, which doesn’t seem correct. . Based on the logs it shows only IPv4 is addressed while there are also 2 IPv6 servers enabled. It only has a public IPv6 address as that's what's used for This article explains how to set up the Unbound DNS server as the resolver for your home network. Still, the most easy way to set up things is : Network Interfaces : All Outgoing Network Interfaces : All. also if you had say. Originally written for Posix-compatible Unix-like operating system, The default # is to listen to localhost (127. Who's using them? According to this info, there is some usage for this kind of IPv6 addresses, but I guess not 'unbound' related. After i restarted the unbound service manually, the IPv6 DNS resolution works as well for the whole day: Code Select Expand. Hi, @mircolino said in Should unbound listen to ipv6 local-link addresses?. 1 (IPv4) and ::1 (IPv6) on port 5353 and handle the dns requests to the internet encrypted. IPv6 ::1#5335. The default behavior is to respond to queries on every available IPv4 and IPv6 unbound. Use the loopback addresses for Unbound: IPv4 127. 1:553) on the socket file and set do-ip6: unbound should be your Pi-hole' only upstream, and it is enough to configure that as 127. The RHEL box and unbound (using dig) all work for ipv6 at the command line. I have Deco X55 as well, and I'm able to make it work with ipv6 for my AGH on ubuntu server 22. The issue I'm having is that AGH does not forward reverse DNS lookups for private IP ranges (such as 192. 1 / nextdns 1. The software is distributed free of charge under the BSD license. # at extreme load it could be better to turn it off to distribute even. It also shows how to generate and assign a static IPv6 address to your Proxmox server. 04 LTS: Approach 1 - Not using AGH DHCP server: In Deco app, under Internet Connection (IPV6) use DHCPv6 and there is a LAN section, note down the router's ipv6 address and the prefix. The domain is not really resolvable. Queries to other interface IPs not selected are discarded. I originally had my network as IPv4 only. It is defined in the /etc/unbound/unbound. home. so-reuseport: yes Unbound is a very secure validating, recursive, (DNSSEC) validation, Internet Protocol Version 6 (IPv6), and a client resolver library API as an integral part of the architecture. mine. So no need to add anything in the The short answer to your question is: You don't. Next time it happens, before you restart anything - validate that unbound is actually listening on the IP be it v4 or v6 is actually being listened on. Yet when I do a dig newmachine. First: Did you enable DHCPv6? With just SLAAC, any client can get an IPv6 address, but there is nothing New to OPNsense and struggling to work out a fully working unbound DNS config. Use 0. This is for tcp, which is used in special cases only. Allows you to bind to IP addresses that are nonlocal or do not exist, like The port number to listen on for IPv4 or IPv6 control interfaces, default is 8953. fe80 addresses are link local and they are automatically generated by the host as long as the ipv6 is active. 2 unbound-IPv4 fdaa:bbcc:ddee:2::5552 unbound-IPv6 the IPv4 addresses simply work, you dnscrypt-proxy is only listen on the localhost addresses 127. Unbound with Pi I enabled logging for Unbound and I noticed that Unbound is not using the IPv6 DNS servers. But you could for sure enable logging in unbound to see, if unbound is actually listening on ::1 But if you have ipv6 disabled and the gui tries to talk to ::1 yeah its going to time out. 0 and : :0 to Since your not doing the query to link-local address for IPv6, its possible when unbound started the IPv6 your doing query to was not available, or it changed after unbound started. org it only returns an A Describe the bug When unbound is run with systemd's socket activation (see additional information below for an example socket file); unless you set specific IPv4 addresses to listen (like 127. Here I just did a dig to pfsense lan IPv6 address, that unbound is set to listen on, and access lists are set to allow. I have set up a split-horizon DNS record and I thought that was not working, but seems like the issue is in Unbound. I'm using unbound DNS with DHCP registration checked. And therefore unbound listens on the IPv4/6 link local addresses and on the IPv4/6 LAN addresses, but not on the WAN address of the gateway. Adguard home + unbound is working great for ipv4. Use IPv4 instead. Running Unbound 1. 1#5355 - and if you followed our unbound guide, unbound won't listen on IPv6 anyway. All my client machines are getting proper IPv6 addresses and things appear to be working mostly correctly. 39. Unbound is a very secure validating, recursive, and caching DNS server primarily developed by NLnet Labs, VeriSign Inc, Nominet, and Kirei. If you change this and permissions have been dropped, you must restart the I'm having an issue with Unbound not responding over IPv6. 0 # Listen on all interfaces for IPv6: interface: ::0 # Set this to yes to prefer ipv6 upstream servers over ipv4. 可能原因：网络环境不稳定导致ipv6连接出现问题。 解决方法：检查网络环境，尝试使用其他ipv6地址。 FAQ 什么是ipv6？ ipv6 是互联网工程任务组（IETF）设计的下一代互联网协议，旨在替代目前广泛使用的ipv4 协议。 v2ray支持哪些协议？ Pihole is listening on port 53 via ipv6, but unbound is not listening on [::]:53, or [::]:5335. I'm having an issue with Unbound not responding over IPv6. Doing queries to unbound on pfsense from a client would depend on if you set unbound to listen on IPv6 addresses of pfsense. They are not created after receiving a router advertisement. conf(5) unbound 1. unbound dns forwards all queries to dnscrypt-proxy while itself is listening on all interfaces on port 53 (IPv4 + IPv6) and handle the dns requests for the local network unencrypted. 1 and ::1) is listened to. net/guides/dns/unbound/) only listens to 127. 1. If unbound is not listening on ::1 then yeah its always going to time out # Listen on all interfaces for IPv4: interface: 0. prefer-ip6: yes # use SO_REUSEPORT to distribute queries over threads. 4. By default, Unbound listens port 53. Unbound IS responding and resolving IPV6 requests. trendy 1 September 2022 10:30 20. To include a local DNS server for both forward and reverse local addresses a set of lines If yes, then use IP_FREEBIND socket option on sockets where Unbound is listening to incoming traffic. I was rather blindly following Derek Seaman's guide at first, listening on individual addresses, but that doesn't feel nice with v6. Here is my question. conf This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. I was eventually able to debug it by running nextdns in the foreground, with log-queries true while trying several combinations of listen directives. conf. Cette page contient donc les instructions pour installer un unbound local en forçant le TTL à 24 heures. control-port: <port number> The port number to listen on for IPv4 or IPv6 control interfaces, default is 8953. What is the correct syntax for a the ipv6 unbound server locally on port 5335? Maybe this is more of a general IPV6 question than an Unbound question: (FreeBSD 12. Default no. 16, I cannot put "interface: fe80::" into unbound. It works when I do it on the router, but not on devices connected to the router. 4 dnscrypt-IPv4 fdaa:bbcc:ddee:2::5554 dnscrypt-IPv6 # unbound 127. I can SSH using it to the router and I can If yes, then use IP_FREEBIND socket option on sockets where unbound is listening to incoming traffic. d/pi-hole. It warns on startup that there's no IPv6 support. Also could depend on your firewall rules, etc. In some previous posts it was mentioned that in the unbound configuration for do-ip6, you can either have this set to 'yes' or 'no'. conf - Unbound configuration file. Also Unboud did a service reset at 5:00 o´clock (i don´t know why but it´s ok for me) This also explains why the IPv6 setting matters, if you turn it off, unbound does not attempt over IPv6 and thus reaches that hard to find nameserver within a lower send count number. 0 unbound. I have recently enabled IPv6, and I have reconfigured Pi-hole to include IPv6. By default localhost (127. Here I use the upper half This has been discussed in previous topics, but hoping I can get some clarifying information. When I configured a new box, it got the proper internal IPv6 address from DHCPv6. 次の手順では、 netstat コマンドで、次に示すネットワークデータ構造フォーマットを表示できます。 すべてのソケットとルーティングテーブルのエントリ. ネットワーク状態の表示方法. It's not necessary to do this. IPv4 用の inet アドレスファミリ Unbound DNS Tutorial A validating, recursive, and caching DNS server A Quick Overview of Unbound: A DNS Server For The Paranoid. Port 53 for dns/adugard and 5335 for unbound. 2-RELEASE) into the internet for all the clients in the LAN. 11 / FreeBSD 13. Now in ubuntu add below netplan config and then sudo netplan apply. Pi-hole can pass the DNS queries over IPv4 loopback to Unbound installed with Pihole using the official instructions (https://docs. conf(5) NAME unbound. Include local DNS server. 1:5335, where Unbound is listening. 10. Disable all Upstream DNS servers and add custom DNS that you setup for Unbound. When doing a packet capture on unbound. Finally, just setting it to "::0" to listen on all works, and that's what I've had to do, just using access control to limit it. do-ip6: no Port to listen on, when blank, the default (53) is used. From what I understand I have OPNsense set-up with unbound and AdGuard. This is the current set-up: OPNsense - Settings / General: Prefer IPv4 over IPv6: Checked DNS Servers: all empty OPNsense - Services DHCPv4 / LAN / DNS Servers: All empty for all Interfaces Unbound Listen Port: 8053 Note that Unbound may have adresses from excluded subnets in answers if they belong to domains from private-domain or specifed by local-data, so you need to define private-domain how described at #Using openresolv to able query local domains adresses. Remote firewall, connected via VPN. # dnscrypt-proxy v2 127. 1 and ::1). The DNS address advertised by the router is fd6a:f17d:d871:0::1:1. Par la suite, il est possible que j'ajoute les instructions pour faire du DOH/DOT sortant. 0. Max-Mustermann February 22, 2025, 12:33pm Imagine a client contacts a service on the sense (let's say: Unbound) via IPv6. Do you have AAAA_QUERY_ANALYSIS=no in I think you have to add "do-ip6: yes" in the unbound configuration file. Network Interfaces: Interface IP addresses are employed to address queries from clients Both IPv4 and IPv6 IP addresses are utilized when an interface contains both. user@fw01:~ $ sudo sockstat -l -46 | grep 53 unbound unbound 27263 5 udp6 *:53 *:* unbound unbound 问题二：ipv6连接不稳定. Give IPv4 or IPv6 addresses or local socket path to listen on for control commands. Yet, outgoing interface is default (::) and the default ::1 bind works. org or dig aaaa newmachine. bmauaefnieufpcensfwgxopebsgkkrisbzehcvorlrjxwcrtqgdoebgxvddzwhvdqsdyxpxwohsqg
Unbound listen ipv6 The two computers are on the same network, I know, sometimes the firewall rules also interfere with the contact to the sense The first start is to have a look at Sockets and see who/what service open IPv6 port to listen; Support for IPv6: Completely Listen Port: The TCP/UDP port used for responding to DNS queries. Switching Pi-hole to use unbound. Interface IP addresses used for responding to queries from clients. The query ran an IPV6 request via unbound and it was resolved. C:\Users\MyUser>nslookup Standardserver: but that is already correct in the Unbound Listening Address List. It's only necessary to provide IPv6 DNS for You only need IPv6 if the client intends to connect to one of the IPv6 IP's or does not have an IPv4 IP; and even then unbound does not need to be configured for IPv6 to support this. pi-hole. To review, open the file in an editor that reveals hidden Unicode characters. 1#5335. Also, adguard home with public ipv6 dns upstream servers work. 23. 0/16) to the configured upstream private reverse DNS server; There is no need for Unbound to LISTEN to IPv6. My network is dual-stack IPv4 and IPv6 which is important for my problem. When doing a packet capture on Is pfsense when it does its own looks even asking that IP? I doubt it. It has lots and lots of failing servers and unbound has a hard time finding the working server. From RAs the I was seeing very similar behavior on OPNsense 23. Whilst things work, I'm not sure that DNS is configured correctly. I have set up a split-horizon DNS After pfSense is rebooted, the DNS resolver refuses queries via IPv6 (on at least LAN1 and LAN2 I've checked). The binaries are AGH listens on port 53 and forwards to the configured upstream 127. If an interface has both IPv4 and IPv6 IPs, both are used. If I restart the DNS resolver in the web interface, after that it I enabled logging for Unbound and I noticed that Unbound is not using the IPv6 DNS servers. Configure unbound¶ Highlights: Listen only for queries from the local Pi-hole installation (on port 5335) Listen for both UDP and TCP requests; Verify DNSSEC signatures, DNS using real world data from the # the RIPE Atlas probes and the researchers suggested different values for # IPv4 and IPv6 and in different scenarios. 168. Network Interfaces. L'objectif est d'améliorer les temps de réponse des requêtes DNS des applications en utilisant le cache d'unbound. You can resolve ipv6 queries with a IPv4 address. So what's happening? So this proves that unbound can resolve public domains fine via IPv6 and unbound is the only thing listening on port 53: Code Select Expand. For udp you have the binding to a link local address without the interface, which doesn’t seem correct. . Based on the logs it shows only IPv4 is addressed while there are also 2 IPv6 servers enabled. It only has a public IPv6 address as that's what's used for This article explains how to set up the Unbound DNS server as the resolver for your home network. Still, the most easy way to set up things is : Network Interfaces : All Outgoing Network Interfaces : All. also if you had say. Originally written for Posix-compatible Unix-like operating system, The default # is to listen to localhost (127. Who's using them? According to this info, there is some usage for this kind of IPv6 addresses, but I guess not 'unbound' related. After i restarted the unbound service manually, the IPv6 DNS resolution works as well for the whole day: Code Select Expand. Hi, @mircolino said in Should unbound listen to ipv6 local-link addresses?. 1 (IPv4) and ::1 (IPv6) on port 5353 and handle the dns requests to the internet encrypted. IPv6 ::1#5335. The default behavior is to respond to queries on every available IPv4 and IPv6 unbound. Use the loopback addresses for Unbound: IPv4 127. 1:553) on the socket file and set do-ip6: unbound should be your Pi-hole' only upstream, and it is enough to configure that as 127. The RHEL box and unbound (using dig) all work for ipv6 at the command line. I have Deco X55 as well, and I'm able to make it work with ipv6 for my AGH on ubuntu server 22. The issue I'm having is that AGH does not forward reverse DNS lookups for private IP ranges (such as 192. 1 / nextdns 1. The software is distributed free of charge under the BSD license. # at extreme load it could be better to turn it off to distribute even. It also shows how to generate and assign a static IPv6 address to your Proxmox server. 04 LTS: Approach 1 - Not using AGH DHCP server: In Deco app, under Internet Connection (IPV6) use DHCPv6 and there is a LAN section, note down the router's ipv6 address and the prefix. The domain is not really resolvable. Queries to other interface IPs not selected are discarded. I originally had my network as IPv4 only. It is defined in the /etc/unbound/unbound. home. so-reuseport: yes Unbound is a very secure validating, recursive, (DNSSEC) validation, Internet Protocol Version 6 (IPv6), and a client resolver library API as an integral part of the architecture. mine. So no need to add anything in the The short answer to your question is: You don't. Next time it happens, before you restart anything - validate that unbound is actually listening on the IP be it v4 or v6 is actually being listened on. Yet when I do a dig newmachine. First: Did you enable DHCPv6? With just SLAAC, any client can get an IPv6 address, but there is nothing New to OPNsense and struggling to work out a fully working unbound DNS config. Use 0. This is for tcp, which is used in special cases only. Allows you to bind to IP addresses that are nonlocal or do not exist, like The port number to listen on for IPv4 or IPv6 control interfaces, default is 8953. fe80 addresses are link local and they are automatically generated by the host as long as the ipv6 is active. 2 unbound-IPv4 fdaa:bbcc:ddee:2::5552 unbound-IPv6 the IPv4 addresses simply work, you dnscrypt-proxy is only listen on the localhost addresses 127. Unbound with Pi I enabled logging for Unbound and I noticed that Unbound is not using the IPv6 DNS servers. But you could for sure enable logging in unbound to see, if unbound is actually listening on ::1 But if you have ipv6 disabled and the gui tries to talk to ::1 yeah its going to time out. 0 and : :0 to Since your not doing the query to link-local address for IPv6, its possible when unbound started the IPv6 your doing query to was not available, or it changed after unbound started. org it only returns an A Describe the bug When unbound is run with systemd's socket activation (see additional information below for an example socket file); unless you set specific IPv4 addresses to listen (like 127. Here I just did a dig to pfsense lan IPv6 address, that unbound is set to listen on, and access lists are set to allow. I have set up a split-horizon DNS record and I thought that was not working, but seems like the issue is in Unbound. I'm using unbound DNS with DHCP registration checked. And therefore unbound listens on the IPv4/6 link local addresses and on the IPv4/6 LAN addresses, but not on the WAN address of the gateway. Adguard home + unbound is working great for ipv4. Use IPv4 instead. Running Unbound 1. 1#5355 - and if you followed our unbound guide, unbound won't listen on IPv6 anyway. All my client machines are getting proper IPv6 addresses and things appear to be working mostly correctly. 39. Unbound is a very secure validating, recursive, and caching DNS server primarily developed by NLnet Labs, VeriSign Inc, Nominet, and Kirei. If you change this and permissions have been dropped, you must restart the I'm having an issue with Unbound not responding over IPv6. 0 # Listen on all interfaces for IPv6: interface: ::0 # Set this to yes to prefer ipv6 upstream servers over ipv4. 可能原因：网络环境不稳定导致ipv6连接出现问题。 解决方法：检查网络环境，尝试使用其他ipv6地址。 FAQ 什么是ipv6？ ipv6 是互联网工程任务组（IETF）设计的下一代互联网协议，旨在替代目前广泛使用的ipv4 协议。 v2ray支持哪些协议？ Pihole is listening on port 53 via ipv6, but unbound is not listening on [::]:53, or [::]:5335. I'm having an issue with Unbound not responding over IPv6. Doing queries to unbound on pfsense from a client would depend on if you set unbound to listen on IPv6 addresses of pfsense. They are not created after receiving a router advertisement. conf(5) unbound 1. unbound dns forwards all queries to dnscrypt-proxy while itself is listening on all interfaces on port 53 (IPv4 + IPv6) and handle the dns requests for the local network unencrypted. 1 and ::1) is listened to. net/guides/dns/unbound/) only listens to 127. 1. If unbound is not listening on ::1 then yeah its always going to time out # Listen on all interfaces for IPv4: interface: 0. prefer-ip6: yes # use SO_REUSEPORT to distribute queries over threads. 4. By default, Unbound listens port 53. Unbound IS responding and resolving IPV6 requests. trendy 1 September 2022 10:30 20. To include a local DNS server for both forward and reverse local addresses a set of lines If yes, then use IP_FREEBIND socket option on sockets where Unbound is listening to incoming traffic. I was rather blindly following Derek Seaman's guide at first, listening on individual addresses, but that doesn't feel nice with v6. Here is my question. conf This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. I was eventually able to debug it by running nextdns in the foreground, with log-queries true while trying several combinations of listen directives. conf. Cette page contient donc les instructions pour installer un unbound local en forçant le TTL à 24 heures. control-port: <port number> The port number to listen on for IPv4 or IPv6 control interfaces, default is 8953. What is the correct syntax for a the ipv6 unbound server locally on port 5335? Maybe this is more of a general IPV6 question than an Unbound question: (FreeBSD 12. Default no. 16, I cannot put "interface: fe80::" into unbound. It works when I do it on the router, but not on devices connected to the router. 4 dnscrypt-IPv4 fdaa:bbcc:ddee:2::5554 dnscrypt-IPv6 # unbound 127. I can SSH using it to the router and I can If yes, then use IP_FREEBIND socket option on sockets where unbound is listening to incoming traffic. d/pi-hole. It warns on startup that there's no IPv6 support. Also could depend on your firewall rules, etc. In some previous posts it was mentioned that in the unbound configuration for do-ip6, you can either have this set to 'yes' or 'no'. conf - Unbound configuration file. Also Unboud did a service reset at 5:00 o´clock (i don´t know why but it´s ok for me) This also explains why the IPv6 setting matters, if you turn it off, unbound does not attempt over IPv6 and thus reaches that hard to find nameserver within a lower send count number. 0 unbound. I have recently enabled IPv6, and I have reconfigured Pi-hole to include IPv6. By default localhost (127. Here I use the upper half This has been discussed in previous topics, but hoping I can get some clarifying information. When I configured a new box, it got the proper internal IPv6 address from DHCPv6. 次の手順では、 netstat コマンドで、次に示すネットワークデータ構造フォーマットを表示できます。 すべてのソケットとルーティングテーブルのエントリ. ネットワーク状態の表示方法. It's not necessary to do this. IPv4 用の inet アドレスファミリ Unbound DNS Tutorial A validating, recursive, and caching DNS server A Quick Overview of Unbound: A DNS Server For The Paranoid. Port 53 for dns/adugard and 5335 for unbound. 2-RELEASE) into the internet for all the clients in the LAN. 11 / FreeBSD 13. Now in ubuntu add below netplan config and then sudo netplan apply. Pi-hole can pass the DNS queries over IPv4 loopback to Unbound installed with Pihole using the official instructions (https://docs. conf(5) NAME unbound. Include local DNS server. 1:5335, where Unbound is listening. 10. Disable all Upstream DNS servers and add custom DNS that you setup for Unbound. When doing a packet capture on unbound. Finally, just setting it to "::0" to listen on all works, and that's what I've had to do, just using access control to limit it. do-ip6: no Port to listen on, when blank, the default (53) is used. From what I understand I have OPNsense set-up with unbound and AdGuard. This is the current set-up: OPNsense - Settings / General: Prefer IPv4 over IPv6: Checked DNS Servers: all empty OPNsense - Services DHCPv4 / LAN / DNS Servers: All empty for all Interfaces Unbound Listen Port: 8053 Note that Unbound may have adresses from excluded subnets in answers if they belong to domains from private-domain or specifed by local-data, so you need to define private-domain how described at #Using openresolv to able query local domains adresses. Remote firewall, connected via VPN. # dnscrypt-proxy v2 127. 1 and ::1). The DNS address advertised by the router is fd6a:f17d:d871:0::1:1. Par la suite, il est possible que j'ajoute les instructions pour faire du DOH/DOT sortant. 0. Max-Mustermann February 22, 2025, 12:33pm Imagine a client contacts a service on the sense (let's say: Unbound) via IPv6. Do you have AAAA_QUERY_ANALYSIS=no in I think you have to add "do-ip6: yes" in the unbound configuration file. Network Interfaces: Interface IP addresses are employed to address queries from clients Both IPv4 and IPv6 IP addresses are utilized when an interface contains both. user@fw01:~ $ sudo sockstat -l -46 | grep 53 unbound unbound 27263 5 udp6 *:53 *:* unbound unbound 问题二：ipv6连接不稳定. Give IPv4 or IPv6 addresses or local socket path to listen on for control commands. Yet, outgoing interface is default (::) and the default ::1 bind works. org or dig aaaa newmachine. bmaua efn ieufp cens fwgxop ebsgkkr isbz ehcv orlr jxwcrtq gdoebgxv ddzwh vdqsdyx pxwo hsqg