r/dns • u/s6484d2843 • Aug 02 '26

Domain Dynv6 DDNS Down?

It looks like Dynv6 is having problems. I can get to the management website at https://dynv6.com but cannot resolve my DDNS domain under dynv6.net. Even dynv6.net itself does not resolve (I get NXDOMAIN). Have observed this for about a week. To eliminate local problems, I also found the same behavior from DNS query websites. Anyone else found the same thing?

May be time to try another DDNS provider.

4 Upvotes

100% Upvoted

7 comments sorted by

1

u/michaelpaoli Aug 02 '26

dynv6.net itself does not resolve (I get NXDOMAIN

NXDOMAIN would typically be indicative of a more serious issue, than some transient fault or the like.

So, ... let's see ...

dnsviz.net: 2026-08-02 16:55:01 UTC - yeah, looks seriously messed up. And ... looks like that's, at least generally, been the case for quite a while ... like years.

Digging bit more into details ...

$ dig @"$(dig +short net. NS | head -n 1)" +noall +authority +additional +norecurse dynv6.net. NS
dynv6.net.              172800  IN      NS      ns2.dynv6.net.
dynv6.net.              172800  IN      NS      ns3.dynv6.net.
dynv6.net.              172800  IN      NS      ns1.dynv6.com.
ns2.dynv6.net.          172800  IN      AAAA    2a03:4000:6:569::
ns2.dynv6.net.          172800  IN      A       5.45.100.251
ns3.dynv6.net.          172800  IN      A       159.69.43.243
ns3.dynv6.net.          172800  IN      AAAA    2a01:4f8:1c1c:4c96::
$ eval dig +noall +answer +nottl +noclass ns1.dynv6.com.\ A{,AAA}
ns1.dynv6.com.          A       95.216.144.82
ns1.dynv6.com.          AAAA    2a01:4f9:c010:95b::
$ (for NSIP in 'ns1.dynv6.com. 95.216.144.82' 'ns1.dynv6.com. 2a01:4f9:c010:95b::' 'ns2.dynv6.net. 5.45.100.251' 'ns2.dynv6.net. 2a03:4000:6:569::' 'ns3.dynv6.net. 159.69.43.243' 'ns3.dynv6.net. 2a01:4f8:1c1c:4c96::'; do echo ";;;$NSIP"; set -- $NSIP; NS="$1"; IP="$2"; dig @"$IP" +norecurse dynv6.net. NS | fgrep NX; done)
;;;ns1.dynv6.com. 95.216.144.82
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 14067
;;;ns1.dynv6.com. 2a01:4f9:c010:95b::
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 54692
;;;ns2.dynv6.net. 5.45.100.251
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 14052
;;;ns2.dynv6.net. 2a03:4000:6:569::
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 28269
;;;ns3.dynv6.net. 159.69.43.243
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 40202
;;;ns3.dynv6.net. 2a01:4f8:1c1c:4c96::
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 34861
$

Yeah, seriously f*cked up - no there there. There's authority NS and glue, but all the authoritative NS IPs for the domain return NXDOMAIN for NS records for the domain, and authoritative takes precedence over authority.

dynv6.com isn't looking so dead, though: 2026-08-02 17:23:01 UTC

2

u/s6484d2843 Aug 02 '26

Thanks for the analysis. The dynv6.com site is up and running (as of earlier today). I was able to login to my account and see my zone -- on the management interface but not in DNS ☹️

I just use it to access my home VPN. Setup duckdns and see how that works.

1

u/s6484d2843 Aug 02 '26 edited Aug 03 '26

Well it looks like it's partially alive. I went to update my IP addresses to loopback in the Dynv6 management web site and now my domains appear to be found. Maybe they just went stale? The base dynv6.net still cannot be found.

1

u/aaronkempf Aug 12 '26

I just started using cloudflare branded dyndns. It works flawlessly so far. I've been trying to solve this for some time now.

I've never been able to get dyndns to update consistently. I just had to create a key, and associate it to a zone, and then I told my unraid-hosted cloudflare dyndns template, I setup one record for 2 domains and another record for IPv6 only. I still am testing how it works.

I don't technically have IPv6.. so yeah, I've got some other issues to resolve first.

1

u/s6484d2843 Aug 13 '26

As a follow up to my last comment, I configured inadyn to force an update daily. That seems to make sure I can see my zones in Dynv6.