DYNV6 deleting records

Same issue. Two TXT records needed for ProtonMail domain verification just disappeared a couple of days ago.

See the thread about AAAA records getting lost. My TXT record for google site verification keeps getting booted on a regular basis as well.

Hey there!
Got the same issue since a couple of weeks. In my case i got a few A and AAAA records. At some point a few records disappeared but i can’t really remember which. Since that point one A and an identical named AAAA record just dissapear. In my experience it is not a problem to use one hostname for one A and AAAA host.
However i never really had any issues with this dynv6.com! Thanks for the years of good and reliable Service.
Would be nice if it continues this way :wink:

Hi,
for me it sems like it is removing specific names.
I have one CNAME which is cloud. This is always removed after some minutes.
All other CNAMEs have no problems.

Same for me, I am also using “cloud” as CNAME. And things getting worse: Last week I’ve written a small script which recreates the records if its missing. It worked very nice for a few days, but since yesterday I get permission errors and the trouble starts again.

I always loose my nextcloud A record.
So +1 for cloud

It’s “cloud” for me as well. See also AAAA record got lost, as mentioned by @tncom.
As for your permission issue:
I have a script that does basically the same as yours, but uses ‘dig @nsX.dynv6.com’ (X={1,2,3}) in order to check for the records. So it needs to login via the REST API only if a record got actually lost. This works for me so far.
For script examples check the above link.
Thomas

And… my TXT record got hosed again.

i also have the same problem. My subdomain is named cloud and i also point to a nextcloud installation. I have set some other records as well.

A-Record to cloud.blabla.tld ← disapears automatically
A-Record to docsrv.blabla.tld
A-Record to blabla.tld ← disapears automatically
same for ipv6:
AAAA-Record to cloud.blabla.tld
AAAA-Record to docsrv.blabla.tld
AAAA-Record to blabla.tld

I can’t say, how often the A-records get lost. It’s a testing domain only. But every morning, i try to connect, the cloud record is disapeared.
My update client is a AVM Fritz Box 6591 Cable. It’s a 500/50 dual stack account.
The router reports a successfully login for IPv4 and IPv6.

I really appreciate any help on this issue.

1 Like

I’m having a similar problem. My MX records keep being deleted.

It looks like I ran into this problem today… 3 times already.

I have a homeserver that runs Traefik and thus can create multiple sub-domains. So instead of having to update each and every one of them I added a wildcard-CNAME for my domain that points to the AAAA-Record.

However today I noticed none of my subdomains work. After a bit of checking I found that the CNAME was missing. I added it (at around 11:00 CET), checked again 5 minutes later and it was gone . After I added it again it appeared to stick, but I just checked again (13:30 CET) and it’s gone again.

Anyone knows why this happens and how to prevent it? It’s rather annoying as I just switched to this service like a week ago and everything worked fine until today.

I’ve just noticed that MX records seem to have been deleted for all of my domains, and for domains owned by friends who are also using dynv6.com

Has anyone else found that their MX records aren’t working any more?

I was just wondering, why I can’t access my services any more and noticed, that my whole old account got deleted. Not only my records - I was sure, when I tried to reset the password and the system told me ‘not found’.

Update: 19:30 Wildcard-CNAME gone again.

If this doesn’t get fixed I might need to migrate to somewhere else :frowning:

Same here for an AAAA-Record today, exactly when service needed. Updated, fine so far, but can’t be really a solution, right?

I just made a simple shell script to check if my CNAME was deleted and if so, recreate it via API
wild_dynv6.sh
requisites:

  1. API token
  2. curl
  3. jq

edit: the record is being deleted too frequently… it may not be a good solution

That script works pretty well!

But yea, I found that my record was deleted sometimes in 5 minutes sometimes in 30 minutes… I probably can’t keep calling this every few minutes… there must be another solution

In my account all CNAME @ entries (for the zones itself) vanished. Happens about once every 3 months.

happened to me for a A record i setup last night

Happened to me on 2022-04-08 again, but just for one zone this time. One “@” entry, type CNAME, vanished.