ykg
CDCloudflare Developers
•Created by ykg on 11/18/2024 in #general-help
pfSense DDNS via Cloudflare
I thought I had a handle on DDNS, but looking for help
All my entries went RED, yesterday without any change from my side. Upon noticing I went to Cloudflare dash and tried to drill into my Domain DNS entries and Cloudflare threw back an error saying it was having trouble accessing my entries...so I assumed an issue with CF, but didn't see any word of any major outage.
I waited a bit and was able to eventually get into my DNS entries from CF dashboard. I noticed that some IPs changed, so it appears my IP changed. I then I ran a Wha'ts My IP from my side to confirm the updated IP
After a bunch of forcing update and refreshing, 2 services in my DDNS went green and pulled the updated IP, but the rest stayed RED and were still stuck on the old IP
I did a bunch of refreshing and saving and RED entries went from holding the old IP, to N/A, to 0.0.0.0
What is confusing me is why Cloudflare still has the old IPs in their system.
Is this something I can forcefully update from their end?
This feels like a cache issue, but I don't know where/how to clear it from.
Any help is appreciated
13 replies
CDCloudflare Developers
•Created by ykg on 8/12/2024 in #general-help
CNAME Flattening
Hello.
I'm looking for some clarification on something. I will outline my issue below. Originally I was going to piggy back onto a "SSL Handshake failed" 525 error thread:
"I'm piggy-backing onto this because I want to avoid creating a new post if possible. I was seeing this issue as well for my root domain. I see that my root had an A record with "ABCD.com" and a CNAME record with www and the content field being "parking.namecheap.com".
I deleted the A record and now I get the following up top in the "Recommended steps to complete setup..."
Add an A, AAAA, or CNAME record for your root domain so that ABCD.com will resolve.
my question: can I simply convert the CNAME record to an A record or does that CNAME need to stay there as 'parking.namecheap.com'"
... So I answered my own question and I was able to convert the "www" CNAME record to an A record and now my root will resolve.
Now my question is this. When I try to create a CNAME record with "ABCD.com" I get the CNAME flattening info bubble, but yes, the notice about needing a CNAME record for my root domain does go away.
Am I doing something incorrectly? How or why was the previous situation flipped but I didn't get any notice of CNAME flattening?
Thanks in advance for any insight and clarification on this scenario.16 replies