Dynamic DNS (DDNS) fails to obtain public IP
-
@70tas To note it here as well, I used the script posted in the other thread only for debugging purposes. While you can use it with a cron job, it is not necessary. The DDNS GUI works fine for cloudflare. The important thing is to use the Zone ID for the user name, not the email address. In the past, the email address must have worked because that is what I had in there before. It worked for years but now no longer.
-
@revengineer we sure global doesn't work? My main pfsense running 24.11 is using global and it still works. Just double checked.
Clearly they are moving away from it - it is legacy. I have one, but not sure if they let you create one if you didn't already have one?
Global API key is the previous authorization scheme for interacting with the Cloudflare API. When possible, use API tokens instead of Global API key.
But you can view it if you have one. So he could try using that - but from what he posted, unless he edited for posting - what he has in username isn't valid for either a global key or api token.
-
@revengineer Unfortunately, there is something wrong in my configuration, which causes it not to be able to find my real IP. I'm not going to spend a lot of time on it, since I can use the script via Cron. I just need to modify it so it doesn't update needlesly.
Thanks for all the help
I appreciate it -
@70tas Doesn't matter if it did or we don't even know - maybe it can, but since you have the wrong settings it never going to work.
-
@johnpoz I think we are talking about two different things, and I may not have been clear. For the username, it states for cloudflare: "Enter email for Global API Key or (optionally) Zone ID for API token." I could not get this to accept my email address, and I had to use the Zone ID. If the email address works for you, then I wonder whether my problem is that I changed my cloudflare email address to a different one than I used when I opened the account and established the global api key.
In any case it sounds like @70tas has other issues but has found a solution.
-
@revengineer said in Dynamic DNS (DDNS) fails to obtain public IP:
and I had to use the Zone ID
what was posted from his xml is not a zone id. So how do we know what problem he is actually having - because what he posted is never going to work be it using global key or a api token.
-
@johnpoz I'm sorry John, how do you assume I have the wrong settings. If I had the wrong settings, then the script wouldn't work either, yes?
-
@johnpoz Exactly. You have hit the proverbial nail on the head. I just can't figure out where it is coming from. It doesn't make much sense does it. But like you said earlier, I don't need to spend more time on it. I've modified the script, or rather Google Gemini provided the script for me. ;)
Hey thanks for all of the help sir. I really appreciate it. If there is any way I can help in future, please let me know.
Tas -
@70tas said in Dynamic DNS (DDNS) fails to obtain public IP:
how do you assume I have the wrong settings.
Don't have to assume anything - your xml you posted has the wrong username.. you have your domain name in there - its not your email or you zone id for that domain.. So with how pfsense updates it no it would never work.
-
@johnpoz Ok, well thank you anyway John
Tas -
I'm having this same issue after updating to 2.8.0. My DDNS providers all show red (all 3 of them) and none are updating. They all give the same error:
/services_dyndns_edit.php: Dynamic DNS (<redacted>) There was an error trying to determine the public IP for interface - wan (vtnet1 ).Seems like there's no solution in this thread, unfortunately :(
-
I found a solution on Reddit, it's to disable gateway monitoring (or in my case, I changed the monitoring IP):
https://www.reddit.com/r/PFSENSE/comments/1l1x7wd/pfsense_280_ce_and_dynamic_dns_with_linode_api/ -
@ManiacDC So your gateway was offline.. Or the gateway/monitor you were pointing to was not answering so pfsense thought it was offline. But it wasn't and was working.
It showed it in the gateway widget as offline? That is a pretty significant piece of info to know.. That was never mentioned here.
-
@johnpoz the gateway ip address does not respond to pings, so it was showing as offline in the widget. If I change the IP to something I can ping, like 8.8.8.8, then everything starts working. I don't know what's new with 2.8.0 to change this behavior:
Did monitoring change in 2.8.0?
Did DDNS updates start checking the gateway status in 2.8.0?
I don't know if my gateway showed as offline in 2.7.X, I never checked. I doubt my gateway's ability to respond to pings has changed. -
Seems to be an xfinity thing (which is my provider):
https://www.reddit.com/r/opnsense/comments/1c9zpfq/gateway_monitoring_for_a_boring_comcast_service/
https://www.reddit.com/r/PFSENSE/comments/u9ogdh/comcast_gateway_became_unpingable/I can only presume 2.8.0 started checking the gateway status before updating ddns.
-
@ManiacDC You have a completely different issue. For me, it was only cloudflare that stopped working; other DDNS providers updated fine (I did not mention this though).
It seems you found a solution and @johnpoz pointed you in the right direction. It's indeed recent xfinity issue where you can no longer ping the gateway. I brought this up a couple of months ago here. Just ping something else, and if you receive a response it implies that the gateway is working.
-
@revengineer yeah my issue is different from yours than, but we actually don't know if @70tas 's is. They are using xfinity also so it could be the same issue as mine.
-
@ManiacDC Sorry, I missed the thread.
I do use Comcast, but I don't think it has anything to do with it. I think I may have inadvertently, somehow contaminated my DDNS configuration when I changed my WAN port.
I am using a script that I was given, and used Claude to help modify it so it would not update my DDNS at Cloudflare if my address has not changed, and it is working just fine.
I added the script in cron and I'm running it every fifteen minutes, but I haven't had my address change yet. Hopefully when the address changes, the script will do it's job and change Cloudflare.I've chased my tail around trying to figure out what happened, but since I have a work-around, I'm not that worried about it.
-
@70tas so to confirm, your gateway is not reporting offline?
-
@ManiacDC no. The pfSense uplink gateway is up and sees it's IP. Only the DDNS client with Cloudflare seems to have an issue, but I got around it y using a script.
