You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a topis: Despite setting my own DNS servers, Home Assistant is querying servers 1.1.1.1 and 1.0.0.1 on port 853
I have set my own DNS servers in ipv4 network settings. Both DNS servers work all the time and there are no errors on them
See all time this at HA DNS log (below)
Moved from here: home-assistant/core#130685
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?
Duck DNS
What is the version of the add-on?
1.18.0
Steps to reproduce the issue
Just install addon and see this errors
System Health information
System Information
version
core-2024.11.2
installation_type
Home Assistant OS
dev
false
hassio
true
docker
true
user
root
virtualenv
false
python_version
3.12.4
os_name
Linux
os_version
6.6.54-haos
arch
x86_64
timezone
Europe/Warsaw
config_dir
/config
Home Assistant Community Store
GitHub API
ok
GitHub Content
ok
GitHub Web
ok
HACS Data
ok
GitHub API Calls Remaining
5000
Installed Version
2.0.1
Stage
running
Available Repositories
1458
Downloaded Repositories
10
Home Assistant Cloud
logged_in
false
can_reach_cert_server
ok
can_reach_cloud_auth
ok
can_reach_cloud
ok
GIOŚ
can_reach_server
ok
Home Assistant Supervisor
host_os
Home Assistant OS 13.2
update_channel
stable
supervisor_version
supervisor-2024.11.2
agent_version
1.6.0
docker_version
27.2.0
disk_total
234.0 GB
disk_used
30.9 GB
healthy
true
supported
true
host_connectivity
true
supervisor_connectivity
true
ntp_synchronized
true
virtualization
board
generic-x86-64
supervisor_api
ok
version_api
ok
installed_addons
Studio Code Server (5.17.3), Mosquitto broker (6.4.1), Samba share (12.3.2), Duck DNS (1.18.0), NGINX Home Assistant SSL proxy (3.11.1), Zigbee2MQTT (1.41.0-1), ESPHome (2024.10.2), MariaDB (2.7.1), Advanced SSH & Web Terminal (19.0.0), phpMyAdmin (0.10.0), Node-RED (18.1.1), Govee to MQTT Bridge (2024.07.13-82ddc6e9)
Dashboards
dashboards
8
resources
5
views
34
mode
storage
Recorder
oldest_recorder_run
17 września 2024 16:20
current_recorder_run
16 listopada 2024 11:27
estimated_db_size
3955.11 MiB
database_engine
mysql
database_version
10.11.6
Spotify
api_endpoint_reachable
ok
Xiaomi Miot Auto
component_version
0.7.22
can_reach_server
ok
can_reach_spec
ok
logged_accounts
1
total_devices
15
Anything in the Supervisor logs that might be useful for us?
No response
Anything in the add-on logs that might be useful for us?
Describe the issue you are experiencing
As a topis: Despite setting my own DNS servers, Home Assistant is querying servers 1.1.1.1 and 1.0.0.1 on port 853
I have set my own DNS servers in ipv4 network settings. Both DNS servers work all the time and there are no errors on them
See all time this at HA DNS log (below)
Moved from here: home-assistant/core#130685
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?
Duck DNS
What is the version of the add-on?
1.18.0
Steps to reproduce the issue
Just install addon and see this errors
System Health information
System Information
Home Assistant Community Store
Home Assistant Cloud
GIOŚ
Home Assistant Supervisor
Dashboards
Recorder
Spotify
Xiaomi Miot Auto
Anything in the Supervisor logs that might be useful for us?
No response
Anything in the add-on logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: