Error 1016 DNS Error with subdomain that worked correctly for a few days

[Stratonander]

Hello, for a few days this has been working perfectly for me and now suddenly it gives this error:

"Error 1016. Ray ID: 860cf7ae4e5f2fa7 • 2024-03-07 19:24:45 UTC Origin DNS error.

What happened? You’ve requested a page on a website (music.superlaser.es) that is on the Cloudflare network. Cloudflare is currently unable to resolve your requested domain (music.superlaser.es).

What can I do? If you are a visitor of this website: Please try again in a few minutes. If you are the owner of this website: Check your DNS settings. If you are using a CNAME origin record, make sure it is valid and resolvable. Additional troubleshooting information here."

Any help is appreciated. It is with an advertising campaign that has been active for 4-5 days without any problem and suddenly the subdomain landing page does not load."

[Laudian]

What DNS record have you configured for that subdomain?

[Stratonander]

Just a CNAME of “music” (music.superlaser.es) that must redirects to (fanlink.to). It has been working for almost a week and suddenly it stopped working today at 7pm

[Laudian]

The domain fanlink.to isn’t working. That’s something the owner will need to fix.

[Stratonander]

for me it is working perfectly. It redirects to Toneden.io

[Laudian]

Doesn’t resolve for me:

dig +short fanlink.to @8.8.8.8
dig +short fanlink.to @1.1.1.1

 dig fanlink.to @frankfurt.tonic.to

; <<>> DiG 9.18.18-0ubuntu0.22.04.2-Ubuntu <<>> fanlink.to @frankfurt.tonic.to
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 48580
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: 68f63d1f501443f80100000065ea440ea6606d925a9541d0 (good)
;; QUESTION SECTION:
;fanlink.to.                    IN      A

;; AUTHORITY SECTION:
to.                     7200    IN      SOA     to. hostmaster.tonic.to. 2024030812 43200 7200 2592000 7200

;; Query time: 20 msec
;; SERVER: 46.101.233.168#53(frankfurt.tonic.to) (UDP)
;; WHEN: Thu Mar 07 23:47:42 CET 2024
;; MSG SIZE  rcvd: 122

Also tried all the other nameservers for the .to zone.

Curiously though, systemd-resolved can resolve the name. No idea how that works.

dig fanlink.to

; <<>> DiG 9.18.18-0ubuntu0.22.04.2-Ubuntu <<>> fanlink.to
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 462
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;fanlink.to.                    IN      A

;; ANSWER SECTION:
fanlink.to.             55      IN      A       13.52.31.143
fanlink.to.             55      IN      A       13.56.96.205

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Thu Mar 07 23:50:06 CET 2024
;; MSG SIZE  rcvd: 71

[Stratonander]

I cannot understand this lol. When I go to fanlink.to it redirects me to toneden.io as it should be… hmm. What can I do? It has been working the last 5 days… maybe is a Cloudflare problem or a Fanlink/Toneden one? I dont know what to do

[Laudian]

It is a fanlink.to problem. The redirect you see might be cached.

[Stratonander]

Hmm. but this example is done with the same link of landings but redirecting from domain provider to fanlink.to (toneden) and it works perfectly: https://music.rotoamor.com/cuatro-cero

As you can see I did the same DNS routing but passing through Cloudflare instead of domain provider directly. Domain provider DNS to Hosting > Hosting to Cloudflare > Cloudflare routing to fanlink.to

[Laudian]

@Stratonander

Hmm. but this example is done with the same link of landings but redirecting from domain provider to fanlink.to (toneden) and it works perfectly: https://music.rotoamor.com/cuatro-cero

Also not working:

[Stratonander]

I have tested with other mobile devices that doesnt visited that link and it works… I dont know how that is possible

[Laudian]

The domain sometimes resolves and sometimes doesn’t. That is something that the owners of fanlink.to will need to look into.

[Stratonander]

Well, how strange. I have sent an email to Toneden support to see if they can resolve this for me. I’ll let you know as soon as I know something. Thank you so much!

[Laudian]

One of the rare occasions where I would recommend looking at DNSChecker:

DNS Checker - DNS Check Propagation Tool

You can see mostly red for the domain.

[Stratonander]

Great! Thanks!

[Stratonander]

What I am going to change is the musical landing service provider to FeatureFM since I see that the failure comes in the redirection to fanlink.to, today the rest of the artists and their landings are failing me, which yesterday were going well for me.

With FeatureFM you have to redirect to “ffm.to” which from what I see works perfectly

[sjr]

fanlink.to isn’t resolving from the .to root DNS and doesn’t seem to be registered. It may have just been deleted.

music.rotoamor.com CNAMEs to fanlink.to, so will then also fail.