Problems with DNS services

Installation
1

I have 2 DNS services installed, DuckDNS and dynu dns.
Both are working well, but very often one of the services don’t work.

Dynu is not working for 2 weeks now, sometimes it works again after a few weeks, they work both, and sometimes duckdns don’t work, this cal also takes some weeks.
It is very annoying.

Does somebody know what causes this problems, i can’t find them.

2

There are many possible causes, but the most likely suspects are:

  1. Your WAN IP changes and the service(s) aren’t updated with the new IP
  2. There’s an outage at DuckDNS or DynuDNS
3

The wan ip adress isn’t changed, so that can not be the problem.

And i think there is also no outage at both services.
When i access the dynu website, they don’t speak of an outage.

4

When it next happens:

  1. Check to see what your WAN IP is, as shown by your router
  2. Check to see what IP your hostnames resolve to
  3. Check to see if your port still shows as open
  4. Check that the IP of the computer running Home Assistant hasn’t changed
5

1 - checked, not changed
2 - Checked, still the same
3 - Port is open, duckdns opens the same port
4 - Ip adres is not changed (raspberry pi 4)

Also checked the token in the configuration of dynu addon, also correct
I dont understand.
sometimes it is working sometimes not, never changed anything

6

Right, but you need to check when it’s not working

Checking when it’s working isn’t going to help :wink:

7

But It isn’t working

I have 2 DNS services to my homeassistant
1 - Duckdns.org:8123
2 - Dynu.com:8123

The duckdns is now working.
and the Dynu dns isn’t working

The open port on the router is port 8123, and it lets the duckdns trough
But not the Dynu dns.

I checked al the Dynu dns adresses and settings. not the duckdns.

Logbook messages from the duckdns addon:
[16:59:31] INFO: OK
185.113.173.196
NOCHANGE

Logbook messages from the dynu dns addon:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started

INFO: Using main config file /data/workdir/config

  • Account already registered!
    [15:21:03] INFO: Renew certificate for domains: dynudns.com and aliases:

INFO: Using main config file /data/workdir/config

Processing dynudns.com

  • Checking domain name(s) of existing cert… unchanged.
  • Checking expire date of existing cert…
  • Valid till Apr 7 16:48:02 2023 GMT (Longer than 30 days). Skipping renew!
8

So, it doesn’t let either through.

You enter example.duckdns.org and the computer turns that into an IP address (DNS resolution). Then your computer connects to that IP.

Are you using different ports for each service? If not do you have a proxy server that’s handling the SSL correctly?

9

I don’t have a proxy server.

Both servecis are using the same port.

10

Well… then… I have to ask… just how are you expecting SSL to work?

You’re going to have certificates for either the DuckDNS hostname or the DynuDNS hostname.

one of those will result in errors when you connect

11

Yes i understand that, that was what i thougt also.

But how is it than possible that both services for weeks side by side has functioned, with no problems.
So i thought it was possible to have both services working.

12

Either you never enabled SSL, or you’ve been ignoring the warnings in the browser, or … it never worked.

13

Thanks,

That is proberly the reason.

14

Good evening.
I have a problem… if the router disconnects and changes IP I can no longer access HA. Do I need to reboot? can you tell me why?
in this case I can’t even log in locally…
It is operational because it continues to send notifications. and be available in ssh

15

Please start your own topic