AAAA record got lost

In my case it’s not “nextcloud” but just “cloud”. As I mentioned above, I had created a second zone for testing with the same subdomain names. There “cloud” was deleted regularly, too, at exactly the same times.
Right now, “cloud” keeps being deleted every 24h at 22:01 CET. Before it was 21:08 CET. The time changed after I deleted some obsolete A and AAAA records. Coincidence?
What does work: Create a bogus A record pointing to your cloud, and a CNAME record “cloud”, “nextcloud” or whatever pointing to that A record.

Other records disappear randomly, too, but quite seldom.

A word about the script above: Instead of downloading the current status and then parsing it with jq, you can use the “host” or “dig” command for each of your records and see if it’s resolved so you need not install jq. In my case “host” was not an option because I have a local DNS server that always resolves my domains. “dig @ns1.dynv6.com” works, though. So the related code snippet looks like:

for HOST in "${RECORDS_A[@]}"
do
URL=$HOST.$ZONE
RES=$(dig @ns1.dynv6.com $URL A | grep -e ^$URL | grep -w A)
if [ "$RES" == "" ]
then
...

Hope this helps a bit!
BTW, I’m looking for an alternative, too.

Cheers, Thomas

1 Like

Since last week the problem is now occuring for me, too :frowning: . Any new suggestions to resolve it permanently besides scripting a workaround? Has anybody tried to delete a zone entirely and recreate it?

Cheers
Joachim

See my post of Jan 17.
I wanted to avoid deleting my existing zone. The result was weird enough.
Does your record contain “cloud” in its name? Some others, and also myself, reported that.
Best, Thomas

This is one strange issue. My CNAME record cloud is also affected. I tried recreating it automatically with the script above, but it’s not optimal, as it takes some time (between a few minutes and an hour) after recreation until I can reach my server again (which is not the case for all my other CNAME records, those take effect immediately).

1 Like

One entry does contain cloud but another one does not. Strangely these entries have been working for months now. The odd system behaviour has just started lately. Wondering if there is an relation with an incident where records had not been resolved properly (this had been fixed last weekend I thing, see other thread here in this forum)

1 Like

Hello there. I’m affected too. My CNAME record named “cloud” gets deleted every 24 hours. Other entries are not affected. Just this specific one. This behaviour started about 5-7 days ago.

Same here. Entry named cloud is deleted every days since a few days, whether it’s a CNAME or AAAA. This happened already some weeks past, but after creating it again, it stayed. Now, it is deleted every day.

1 Like

@sascha.riemer @jojow71 @someone @thomas @TheFlipside @jan.wichmann @dmke

Could somebody of you determine a timestamp, on which the specific records got deleted?
I just got up early today to check the records I recreated yesterday and it was missing again.

My “cloud” A record is deleted between 21:00 and 21:15 CET.
But additionally it is also deleted at random times.
You can see them in the following list of timestamps when my check script detected the missing record. The script is executed every 15 minutes.
2021-02-01 21:15
2021-02-01 21:30
2021-02-02 21:15
2021-02-03 21:15
2021-02-04 21:15
2021-02-05 21:15
2021-02-06 21:15
2021-02-07 21:15
2021-02-08 21:15
2021-02-09 21:15
2021-02-10 21:15
2021-02-11 21:15
2021-02-12 21:15
2021-02-13 21:15
2021-02-14 21:15
2021-02-15 21:15
2021-02-16 21:15
2021-02-17 02:15
2021-02-17 05:15
2021-02-17 13:30
2021-02-17 21:15
2021-02-18 01:45
2021-02-18 14:30
2021-02-18 21:15
2021-02-20 01:15
2021-02-20 12:00
2021-02-20 21:15
2021-02-21 21:15
2021-02-22 14:15
2021-02-22 21:15
2021-02-23 21:15
2021-02-24 21:15
2021-02-25 21:15
2021-02-26 21:15
2021-02-27 09:15
2021-02-27 13:30
2021-02-28 14:00
2021-02-28 21:15
2021-02-28 21:30
2021-03-01 21:15
2021-03-02 21:15
2021-03-03 21:15
2021-03-04 09:15
2021-03-04 21:15
2021-03-05 05:45
2021-03-05 21:15
2021-03-06 05:15
2021-03-06 21:15
2021-03-07 05:15
2021-03-07 21:15
2021-03-08 05:15
2021-03-08 21:15
2021-03-08 21:45
2021-03-09 05:15
I have another “dummy” record but this has never been deleted. The problem is only on the “cloud” record.

This looks exactly like what I see here. “cloud” is deleted daily at the same time. The time itself changes every couple of days. In the beginning it was 21:00, then 22:00, later on 23:00, 21:15 … Adding or deleting other records seems to have an influence. Right now, it happens regularly in the early morning. From time to time other records of different types (AAAA, CNAME, MX, TXT) disappear at random, too, but much more seldom and not at the same time. Perhaps there are two different issues.

I don’t think the “cloud” alone is responsible. I often (but not regularly/daily) loose both my “nextcloud” and my “cloud” entries, but “owncloud” stays around forever. Maybe owncloud is simply more stable than nextcloud? :wink:

Would you mind to share you’re script? I’d like to monitor my records and report the results here :slight_smile:

Hmm today I lost a TXT record, that was created yesterday to obtain a wildcard certificate from Let’s Encrypt. Record was named “_acme-challenge.cloud..”.

See my posts of Jan 15 and Feb 27.

1 Like

Ah, the ‘cloud’ again… It seems there is a statistical correlation at least.
But don’t worry about the _acme-challenge record: It’s checked by letsencrypt just once to verify if you are the legitimate owner of your domain and should be deleted afterwards, anyway. You can do it automatically with the option --manual-cleanup-hook in your renewal script, but this is off-topic here.

Jep, I know that validation has to occur just once, but I was curious what will happen to that record…
I created some records like cloud1… cloud2… now for testing and some other records not containing the phrase ‘cloud’.

I did the same: “foocloud”, “barcloud”, “ownclud”, “nextcloud” - they all remained stable, except of “cloud”.
BTW, my “regular” deletion time is now 21:00 CET again, but this morning at 5:30 all of my “cloud” records got lost, not only the A one.

Should we rename our records to “nuage”, “nube”, “nuvola”, “nuvem”, “wolke”, or “chmura” ? :wink:
Or what about “klowd” ?

New surprise: This morning at 8:30 all of my “cloud” records disappeared: A, AAAA, CNAME (I have the CNAME as a backup). After recreating them ns1, ns2, and ns3 answer correctly again,
but they don’t appear in the REST interface (nor on the web frontend that uses the REST interface).

Again, only “cloud” is affected.

Jep, I can confirm this. Lost an A + CNAME today :frowning:
Have to check that with the REST-API, don’t use that regulary.

Achtung, der kommt flach, again my “cloud” wurde geklaut… :stuck_out_tongue_closed_eyes:

1 Like

My CNAME cloud records also keep disappearing. Yesterday I put together a shell script that I run every 5mins to check if the record still exists and, if not, recreate it. All via the REST v2 API.

You can find the script in a gist at GitHub: https://gist.github.com/movd/03febb3ab6435db46452fb55f3a44d65
Check the comment below for a short instruction on how to use it.

This how it looked from my end in the last 23 hours:

$ grep "No record for" ~/logs/dynv6-record-fixer.log
Mar 10 11:55:10 dynv6-record-fixer.sh: No record for 'cloud.mytld.com' found! I will create a new one...
Mar 10 15:15:13 dynv6-record-fixer.sh: No record for 'cloud.mytld.com' found! I will create a new one...
Mar 10 15:20:03 dynv6-record-fixer.sh: No record for 'cloud.mytld.com' found! I will create a new one...
Mar 10 15:25:02 dynv6-record-fixer.sh: No record for 'cloud.mytld.com' found! I will create a new one...
Mar 10 15:30:05 dynv6-record-fixer.sh: No record for 'cloud.mytld.com' found! I will create a new one...
Mar 10 15:35:02 dynv6-record-fixer.sh: No record for 'cloud.mytld.com' found! I will create a new one...
Mar 10 17:00:16 dynv6-record-fixer.sh: No record for 'cloud.mytld.com' found! I will create a new one...
Mar 11 04:30:14 dynv6-record-fixer.sh: No record for 'cloud.mytld.com' found! I will create a new one...
Mar 11 05:10:06 dynv6-record-fixer.sh: No record for 'cloud.mytld.com' found! I will create a new one...
Mar 11 05:30:10 dynv6-record-fixer.sh: No record for 'cloud.mytld.com' found! I will create a new one...
Mar 11 07:10:09 dynv6-record-fixer.sh: No record for 'cloud.mytld.com' found! I will create a new one...
Mar 11 08:15:09 dynv6-record-fixer.sh: No record for 'cloud.mytld.com' found! I will create a new one...
Mar 11 08:30:12 dynv6-record-fixer.sh: No record for 'cloud.mytld.com' found! I will create a new one...
Mar 11 09:00:14 dynv6-record-fixer.sh: No record for 'cloud.mytld.com' found! I will create a new one...
Mar 11 09:10:09 dynv6-record-fixer.sh: No record for 'cloud.mytld.com' found! I will create a new one...
Mar 11 10:00:19 dynv6-record-fixer.sh: No record for 'cloud.mytld.com' found! I will create a new one...
Mar 11 10:15:08 dynv6-record-fixer.sh: No record for 'cloud.mytld.com' found! I will create a new one...
Mar 11 11:10:17 dynv6-record-fixer.sh: No record for 'cloud.mytld.com' found! I will create a new one...
1 Like