Dynamic DNS fails

[Bo Berglund]

On Fri, 19 Mar 2021 14:03:58 +0100, Volker Wysk <post at volker-wysk.de> wrote:

>Hello
>
>After a day, it suddenly works again. Without me doing anything. 
>
>This makes me think again, that it was probably a problem with the name
>server of the dyndns provider (now-dns.com).

Not working properly here:

Windows:
--------
ping vwysk.now-dns.net
Ping request could not find host vwysk.now-dns.net. Please check the name and
try again.

Raspberry Pi:
-------------
$ ping vwysk.now-dns.net
ping: vwysk.now-dns.net: Temporary failure in name resolution

Ubuntu:
-------
$ ping vwysk.now-dns.net
... waiting like a minute or so ...
PING vwysk.now-dns.net (79.210.28.81) 56(84) bytes of data.
64 bytes from p4fd21c51.dip0.t-ipconnect.de (79.210.28.81): icmp_seq=1 ttl=47
time=34.7 ms

Finally checked with tracert on Windows:
----------------------------------------
tracert vwysk.now-dns.net

Tracing route to vwysk.now-dns.net [79.210.28.81]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  asus-main [192.168.119.1]
  2     2 ms     1 ms     1 ms  gw5.a465.priv.bahnhof.se [46.59.126.129]
  3    29 ms     3 ms     3 ms  172.16.0.231
  4    13 ms     2 ms     9 ms  a465-gw-c.bahnhof.net [46.59.118.179]
  5     2 ms     2 ms     2 ms  a465-gw.bahnhof.net [46.59.118.178]
  6     2 ms     2 ms     2 ms  sto-ste-er1.sto-cr1.bahnhof.net [46.59.112.42]
  7    14 ms     3 ms     4 ms  ae51.edge4.stockholm2.level3.net
[213.249.107.93]
  8    26 ms    26 ms    26 ms  ae-1-3107.edge6.dusseldorf1.level3.net
[4.69.161.194]
  9     *       27 ms    27 ms  dtag-level3-dusseldorf1.level3.net [4.68.71.114]
 10    31 ms    31 ms    32 ms  p5b17c5e1.dip0.t-ipconnect.de [91.23.197.225]
 11    35 ms    35 ms    35 ms  p4fd21c51.dip0.t-ipconnect.de [79.210.28.81]

Trace complete.

Does your ddns service update the DNS servers around the world?
If not then the ddns is pointless.
If it does but provides sketchy service you should change ddns provider.


-- 
Bo Berglund
Developer in Sweden