Cloudflare returning 522 while site is UP, because of bug with DNS records

I have a web application that I am able to access from an external network, when bypassing cloudflare.
curl https://82.66.235.227 -k -H "Host: share.skwal.net" -4
-> works
curl https://82.66.235.227 -k -H "Host: share.skwal.net" -4
-> works
I have a dns A record for *.skwal.net pointing to 82.66.235.227. But when I use the domain I get a 522 error, "origin is down".
curl https://share.skwal.net -4
-> fails 522
curl https://share.skwal.net -4
-> fails 522
When I run a DNS query for share.skwal.net I get a Cloudflare IP. This issue appeared after I removed an A record for share.skwal.net pointing to 82.66.235.227, since this entry is made redundant by *.skwal.net
4 Replies
Cyb3r-Jak3
Cyb3r-Jak34mo ago
Are you still having this problem? It seems to be working for me?
Skwal
SkwalOP4mo ago
For now I added the individual records back but no, it's still not working... Sorry for the late response @Cyb3r-Jok3
Cyb3r-Jak3
Cyb3r-Jak34mo ago
So with a wildcard it fails but specific records work?
Skwal
SkwalOP3mo ago
@Cyb3r-Jok3 Yes, it fails if a previous specific record was deleted but works for everything else. Also if i have a working wildcard for a subdomain, it will directly stop working when creating and deleting a specific entry.
Want results from more Discord servers?
Add your server