Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OTBR: Default DNS not able to resolve IPv4 addresses since 2.12.0 #3947

Open
mmarc opened this issue Feb 21, 2025 · 0 comments
Open

OTBR: Default DNS not able to resolve IPv4 addresses since 2.12.0 #3947

mmarc opened this issue Feb 21, 2025 · 0 comments

Comments

@mmarc
Copy link

mmarc commented Feb 21, 2025

Describe the issue you are experiencing

With NAT64 enabled connected Thread devices should be able to resolve IPv4 addresses.
Since 2.12.0 this is no longer working and DNS requests just time out.
When providing a custom external DNS server it works but this way internal IP addresses cannot be resolved.

2.12.2:

matterCli> otcli dns resolve4 google.com
Done
DNS response for google.com. - 
Error 28: ResponseTimeout
matterCli> otcli dns config
Server: [fd58:a2bd:9b49:3111:a35e:6918:3694:fc8f]:53
ResponseTimeout: 6000 ms
MaxTxAttempts: 3
RecursionDesired: yes
ServiceMode: srv_txt_opt
Nat64Mode: allow
Done

2.11.1:

matterCli> otcli dns resolve4 google.com
Done
DNS response for google.com. - fdcb:53cf:537:2:0:0:8efa:b98e TTL:254 
Done
matterCli> otcli dns config
Server: [fd58:a2bd:9b49:3111:a35e:6918:3694:fc8f]:53
ResponseTimeout: 6000 ms
MaxTxAttempts: 3
RecursionDesired: yes
ServiceMode: srv_txt_opt
Nat64Mode: allow
Done

Since 2.12.0 I also see the following errors within addon logs:

00:00:35.353 [W] P-RadioSpinel-: Error processing result: NoAddress
00:00:35.354 [W] P-RadioSpinel-: Error waiting response: NoAddress
00:00:35.506 [W] P-RadioSpinel-: Error processing result: NoAddress
00:00:35.506 [W] P-RadioSpinel-: Error waiting response: NoAddress
00:00:36.100 [W] P-RadioSpinel-: Error processing result: NoAddress
00:00:36.100 [W] P-RadioSpinel-: Error waiting response: NoAddress
00:00:36.164 [W] P-RadioSpinel-: Error processing result: NoAddress
00:00:36.164 [W] P-RadioSpinel-: Error waiting response: NoAddress
00:00:36.382 [W] P-RadioSpinel-: Error processing result: NoAddress
00:00:36.382 [W] P-RadioSpinel-: Error waiting response: NoAddress
00:00:36.838 [W] P-RadioSpinel-: Error processing result: NoAddress
00:00:36.838 [W] P-RadioSpinel-: Error waiting response: NoAddress

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Which add-on are you reporting an issue with?

OpenThread Border Router

What is the version of the add-on?

2.12.0

Steps to reproduce the issue

  1. Update from OTBR addon 2.11.1 to any newer version
  2. Try to resolve IP of any IPv4 host via DNS

System Health information

System Information

version core-2025.2.4
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.13.1
os_name Linux
os_version 6.6.62-haos-raspi
arch aarch64
timezone Europe/Vienna
config_dir /config
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 14.2
update_channel stable
supervisor_version supervisor-2025.02.1
agent_version 1.6.0
docker_version 27.2.0
disk_total 916.9 GB
disk_used 42.0 GB
healthy true
supported true
host_connectivity true
supervisor_connectivity true
ntp_synchronized true
virtualization
board yellow
supervisor_api ok
version_api ok
installed_addons RaspberryMatic CCU (3.79.6.20250220), MariaDB (2.7.2), Nginx Proxy Manager (1.0.1), Mosquitto broker (6.5.0), InfluxDB (5.0.2), Advanced SSH & Web Terminal (20.0.1), Grafana (10.4.2), Vaultwarden (Bitwarden) (0.24.1), OpenThread Border Router (2.13.0), Matter Server (7.0.0)
Dashboards
dashboards 3
resources 0
views 16
mode storage
Network Configuration
adapters lo (disabled), end0 (enabled, default, auto), docker0 (disabled), hassio (disabled), vethc225cc7 (disabled), vethb29a466 (disabled), veth2e82b15 (disabled), veth1119534 (disabled), veth9f3ebb0 (disabled), vethb6708f1 (disabled), veth4baac2f (disabled), veth644e975 (disabled), veth262459e (disabled), vethaca1287 (disabled), vethd2bc4e2 (disabled), wpan0 (disabled)
ipv4_addresses lo (127.0.0.1/8), end0 (192.168.86.2/24), docker0 (172.30.232.1/23), hassio (172.30.32.1/23), vethc225cc7 (), vethb29a466 (), veth2e82b15 (), veth1119534 (), veth9f3ebb0 (), vethb6708f1 (), veth4baac2f (), veth644e975 (), veth262459e (), vethaca1287 (), vethd2bc4e2 (), wpan0 ()
ipv6_addresses lo (::1/128), end0 (fd65:3923:f245:84cd:4849:f181:d794:c17f/64, fe80::fe86:e34e:8ceb:dfa1/64), docker0 (fe80::42:bcff:fe5f:9a20/64), hassio (fe80::42:3bff:fec6:2d80/64), vethc225cc7 (fe80::f4ee:e7ff:fedd:f4d0/64), vethb29a466 (fe80::944e:31ff:fedd:c569/64), veth2e82b15 (fe80::7c40:c0ff:fe25:ed56/64), veth1119534 (fe80::91:71ff:fe38:bd74/64), veth9f3ebb0 (fe80::30fd:78ff:feb4:c050/64), vethb6708f1 (fe80::a1:5dff:fe0e:e71e/64), veth4baac2f (fe80::9842:2aff:fea7:2259/64), veth644e975 (fe80::940d:e5ff:fe64:d24a/64), veth262459e (fe80::24e9:75ff:fe99:4b64/64), vethaca1287 (fe80::24d1:28ff:feff:ba92/64), vethd2bc4e2 (fe80::e4c6:dbff:fe3f:df1e/64), wpan0 (fd58:a2bd:9b49:3111:0:ff:fe00:fc11/64, fdcb:53cf:537:1:a081:2dcb:8d11:e236/64, fd58:a2bd:9b49:3111:0:ff:fe00:fc10/64, fd58:a2bd:9b49:3111:0:ff:fe00:fc38/64, fd58:a2bd:9b49:3111:0:ff:fe00:fc00/64, fd58:a2bd:9b49:3111:0:ff:fe00:dc00/64, fd58:a2bd:9b49:3111:a35e:6918:3694:fc8f/64, fe80::bc46:150f:b517:61d1/64)
announce_addresses 192.168.86.2, fd65:3923:f245:84cd:4849:f181:d794:c17f, fe80::fe86:e34e:8ceb:dfa1
Recorder
oldest_recorder_run 8. Februar 2025 um 15:29
current_recorder_run 17. Februar 2025 um 07:42
estimated_db_size 1796.80 MiB
database_engine mysql
database_version 10.11.6

Anything in the Supervisor logs that might be useful for us?

Anything in the add-on logs that might be useful for us?

Additional information

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant