Domain xxx.dedyn.io stop working

dynDNS at dedyn.io
1

hi, I had a domain created for few weeks and today just stop working, trying to ping and I got : no address associated with hostname. I have tried to run ddclient but no luck :frowning:

so, I’ve recreated domain and still does not work - not sure what to do

using let’s enc for this domain

Removed all subdomains and then I did run declient with just one domain- but still can not get this work

karcio@debian-4gb-hel1-2:~$ sudo ddclient -force
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:–:-100 12 100 12 0 0 65 0 --:–:-- --:–:-- --:–:-- 65
SUCCESS: updating xxx.dedyn.io: good: IP address set to xx.xx.xx.xx

2

Hi karcio,

Thank you for your message, and welcome to deSEC! :slight_smile:

It’s hard to tell what’s going on without knowing the domain name. Please contact support with more details, and we’ll try to help you.

Stay secure,
Peter

2 Likes
3

Same issue and symptoms. Until yesterday, the recently configured subnames of my domain were working, but now I can still ping the hostnames — nothing more.
I also added the subnames as type AAAA without any changes. Both IPv4 and IPv6 resolve correctly.

curl -6 -vk https://nextcloud.my_domain.dedyn.io
* Host nextcloud.my_subdomain.dedyn.io:443 was resolved.

curl -4 -vk https://nextcloud.my_domain.dedyn.io
* Host nextcloud.my_domain.dedyn.io:443 was resolved.
4

@molenex & @karcio I don’t see any indications of DNS problems in the output you provided.

If you can ping your host then chances are good that DNS is working fine.

Unless there are in fact problems with DNS you will need to check other aspects of your servers, such as the webserver, the TLS certificate, possibly port forwarding on your router, firewall settings, etc. Remember that deSEC only provides a DNS service. You are responsible for the actual services on your servers.

Use DNS centric tools such as dig(1) (on *NIX) to test DNS. You can also use web tools such as DNSViz to check that your domain is setup correctly for DNSSEC. (But note that subdomains of dedyn.io are always set up correctly by deSEC. You only need to check if you brought your own domain.)

HTH
fiwswe

5

I have fixed this using: sudo ddclient --force

so, created domain: digitalhub.dedyn.io

then using lets encrypt I run following:
sudo certbot -v certonly --nginx -d digitalhub.dedyn.io -dupload.digitalhub.dedyn.io-dconference.digitalhub.dedyn.io-dxmpp.digitalhub.dedyn.io-dturn.digitalhub.dedyn.io

I think I set up almost all but I have a problem with SRV - can anyone point me how to:

  • create srv for prosody
  • setup ddclient to call ip4 ip6 - or maybe it is better to use something different

this is my /etc/ddclient.conf

protocol=dyndns2 
use=cmd, cmd='curl https://checkipv4.dedyn.io/' 
ssl=yes 
server=update.dedyn.io 
login=digitalhub.dedyn.io password='xxx' digitalhub.dedyn.io,upload.digitalhub.dedyn.io,conference.digitalhub.dedyn.io,xmpp.digitalhub.dedyn.io,turn.digitalhub.dedyn.io

Also when I check dns in prosody all looks fine:

Checking DNS for component ``conference.digitalhub.dedyn.io``…
Checking DNS for host ``digitalhub.dedyn.io``…
Checking DNS for component ``upload.digitalhub.dedyn.io``…
All checks passed, congratulations!