DNS IP integration URL is out of date 2025

[mgguinne]

The problem

As per https://github.com/home-assistant/core/issues/129602

I am getting a ton of errors in my logs saying DNSIP can't connect to myip.opendns.com

What version of Home Assistant Core has the issue?

core-2025.5.1

What was the last working version of Home Assistant Core?

core-2025.5.1

What type of installation are you running?

Home Assistant OS

Integration causing the issue

DNS IP

Link to integration documentation on our website

https://www.home-assistant.io/integrations/dnsip

Diagnostics information

As per the previous issue, the url "myip.opendns.com" no longer resolves.

opendns now advise to use "https://myipv4.p1.opendns.com/get_my_ip"

https://support.opendns.com/hc/en-us/articles/227986687-How-can-I-determine-my-public-IP-Address

Example YAML snippet

Anything in the logs that might be useful for us?

Logger: homeassistant.components.dnsip.sensor
Source: components/dnsip/sensor.py:111
integration: DNS IP (documentation, issues)
First occurred: 6:14:04 AM (75 occurrences)
Last logged: 8:42:04 AM

Exception while resolving host: (1, 'DNS server returned answer with no data')

Additional information

I noted in the previous issue it might be working for some users, but this has been giving me errors for quite some time now.

JSON - {"ip":"192.150.x.x"}

[home-assistant[bot]]

Hey there @gjohansson-st, mind taking a look at this issue as it has been labeled with an integration (dnsip) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of dnsip can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign dnsip Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

dnsip documentation dnsip source _{^{(message by IssueLinks)}}

[hobbypunk90]

i've a similar/related problem since 2025.5.X (perhaps earlier 😅), when i try to add a new dnsip entry i always get "invalid hostname" https://github.com/user-attachments/assets/f9ba1d9b-3552-4fc0-a531-7b89959dc59b

[123billybob321]

I have the same issue with "invalid hostname" when trying to add a new host. I'm not sure when it started, but it's worked for me in the past as I have a few entries.

[cyberpunk2350]

Glad I'm not the one only one getting the invalid hostname error...thought I was doing something wrong.

[ndanyluk]

Getting the same here - invalid hostname.

New user so can't say if it's working on older installs

[MiRen76]

Same issue here since ha version 2025.5

[tbclark3]

This is probably related: I can no longer change the DNS servers in the configuration panel. Any DNS server I put in results in an error "invalid ip address or port for resolver".

[johanels]

I cannot find any open pull requests mentioning this issue so looks like this is not being looked into. Also missing this feature a lot for monitoring my ISP services.

[Rewindbb33]

Issue is still valid for me as well. Latest haos version

[TheDK]

Same here - cannot change resolver and lots of errors as the now Cisco-owned OpenDNS doesn't seem to resolve reliably anymore.

[DasLetzteEinhorn]

In case you're looking for a workaround: I deleted the integration a few days ago and implemented a simple sensor to poll an API that returns the IP of the requesting system:

sensor:
  - platform: rest
    name: "WAN IP Address"
    resource: https://api.ipify.org?format=json
    value_template: "{{ value_json.ip }}"
    scan_interval: 120 # time in seconds
    unique_id: ipv4

[gjohansson-ST]

Sorry it took some time to get looked at but it's going to be resolved with next release.

[DasLetzteEinhorn]

Nice, thanks!

[fevo21]

@gjohansson-ST could you give a short summary what the fix was for the DNS IP integration? Does it have any relation to the update to aiodns 3.4.0? I also experience above issue since 2025.5, amongst other DNS issues see 145708 and noticed the DNS IP integration issues are not there when the aiodns in 2025.5.x is downgraded to 3.2.0.

It might give us some valuable insight for the other DNS issues 145708