Dynamic DNS & Namecheap
-
@mgodinez said in Dynamic DNS & Namecheap:
but since I have a dynamic ip address
Just a point of discussion - nothing wrong with having a ddns setup. But does your IP really change? I have had the same dynamic IP for going on 3 years now.. And with my previous ISP same IP for like 5 I believe without it changing. They had redone their IP space there once - if not would of been more like 10 years on the same IP.
Unless your turning off your router for extended periods, or change its mac normally you would just continue to renew your IP. Unless your isp is forcing a change to the IP for some crazy reason, or they redo their IP space for a region, etc.
If you have your router on 24/7 and it doesn't go offline for an extended amount of time you should just keep the same IP be it dynamic assigned or not.
-
@johnpoz said in Dynamic DNS & Namecheap:
Just a point of discussion - nothing wrong with having a ddns setup. But does your IP really change?
Here almost all ISPs give you a different public IP on every modem reboot. So DDNS services are really required for all inbound traffic.
Just my .02... -
@psp curious how they know your device rebooted? The dhcp client on even reboot of the device should at first still request is old IP before it sends out a discover.
Not saying it doesn't happen, just hasn't been my experience here in the US on any of the many ISPs have had over the years, nor any of isp have even dealt with for other users..
With many countries that require logging of IPs to users, etc. and traffic they go to - would seem odd that they would make their lives more difficult by changing the IP they give them at the drop of hat is all.
-
@johnpoz said in Dynamic DNS & Namecheap:
With many countries that require logging of IPs to users, etc. and traffic they go to - would seem odd that they would make their lives more difficult by changing the IP they give them at the drop of hat is all.
You are absolutely right. Even here (IT) we are required to keep those logs but they simply choose the hard way (i.e. logs every UserAuth/MAC -- IP association event).
-
@hossimo said in Dynamic DNS & Namecheap:
/services_dyndns_edit.php: phpDynDNS (example): (Unknown Response)
There was a recent thread about this and Namecheap...seems they are returning UTF-16 encoded text which is not being parsed by PHP correctly and hence failing to read the response. In the linked Reddit thread they acknowledge it's their issue.
-
@johnpoz For the most part my IP at home does not change between reboots, however it does sometimes (randomly), and given a travel a fair amount I use the dynamic DNS entry to access my VPN when I'm traveling so I don't get locked out.
-
@hossimo said in Dynamic DNS & Namecheap:
however it does sometimes (randomly)
Agreed - never hurts to have a fallback if this happens.. But generally speaking and I only bring it up as a point of discussion related to the topic.. Quite often users think they "have to have" ddns when their IP might be the same for years at a time, etc..
Just because its handed to you via dhcp, doesn't mean it changes as the wind blows ;)
you need a static IP
From OP comment was my point of discussion.
-
Can confirm the same issue here using Namecheap with pfsense. The config will update the IP fine, but it doesn't reflect this in the pfsense GUI, and the logs show the "/services_dyndns_edit.php: phpDynDNS (XXX): (Unknown Response)" error.
-
@zoltrix said in Dynamic DNS & Namecheap:
Can confirm
The issue left is : the DDNS text is showing a red 'failed' message, but the IP was updated. So your host name does point yo your actual WAN IP. It's just a 'visual' thing in the pfSense right now.
As cheapname confirmed that they changed something on their side, the solution is 'waiting'. -
Thanks Jangert
-
@gertjan Also experiencing this. If you use the namecheap http update method, then you do get a green tick in the gui. As its been said above, the ip address still updates.
-
we should enter a bug report I guess
-
@zoltrix said in Dynamic DNS & Namecheap:
we should enter a bug report I guess
Some one - here on this forum, or on reddit, wrote that the namecheap support has confirmed the issue, as 'something' on their side was changed (not pfSense, we use all the same version / scripts ) and that they, namecheap, will correct it.
For the record, as the brand of the company implies, they do not have a huge budget, so this will take some time.
In the future, they will correct he issue on their side, and everything will be fine again.
For the time being, a work around exists.If pfSense get patched now, and namecheap correct the issue afterwards, the problem will re start all over again, and the patch has to be removed by updating pfSense again.
edit : Btw : if a bug report has to be opened : go head : good idea. But use the namecheap bug reporter @namecheap - if they have one ....
-
@gertjan said in Dynamic DNS & Namecheap:
For the record, as the brand of the company implies, they do not have a huge budget, so this will take some time.
Maybe done some homework first.
Namecheap had over $200 million in revenue in 2020, which was up 35%, or $51.6 million, over the $149 million it posted in 2019.
It has 11 million registered users and 10 million domains.
-
@zoltrix I think that was meant as joke ;)
But they could have 1 Billion in revenue, doesn't mean they spend any of that on development ;)
The issue comes down to, if pfsense didn't change anything, and it stopped working because namecheap did change something. Do you also change pfsense to accommodate whatever changed (can you even?), or is namecheap going to change/fix what they did or forget to add or whatever.
-
@johnpoz said in Dynamic DNS & Namecheap:
I think that was meant as joke
Yeah, hope so.
@zoltrix said in Dynamic DNS & Namecheap:
Namecheap had over $200 million in revenue in 2020, which was up 35%, or $51.6 million, over the $149 million it posted in 2019.
I didn't fact-check that, but I tend to believe the numbers. I 'know' who namecheap is.
They have probably also an 'owner' or share holders, or whatever. And now we reached the point : Who comes first :
The 'clients' ?
The the share holders ?I'm pretty sure, if some one at namecheap sits down for one hour or so, the issue will be solved. One hour !
But noooop - xx thousand of clients will have to wait for weeks - now months.Btw : I say up front : I have nothing against namecheap - neither against the concept as companies and how they work and their goals. I'm working for a company - and the idea is mainly : making € (no $ here).
And making fun, of course.And also : again :
They have confirmed : they introduce the issue.
They fix it.
Or they shall feel the power of Free DynDNS service.
Although that won't touch them financially, as the service is free - and is this might be the actual reason why all this takes so long ;) -
D dma_pf referenced this topic on
-
D dma_pf referenced this topic on
-
@zoltrix said in Dynamic DNS & Namecheap:
logs show the "/services_dyndns_edit.php: phpDynDNS (XXX): (Unknown Response)" error.
https://redmine.pfsense.org/issues/12816
There is a patch in the new System Patches 2.0 package. (recommended patches are now listed in it)
I do not get the unknown response error when clicking Save and Force Update. I get "(Success) IP Address Updated Successfully!" but 2-3 minutes later the page times out and it logs a " *406 upstream timed out (60: Operation timed out) while reading response header from upstream" error.
-
This post is deleted! -
@steveits said in Dynamic DNS & Namecheap:
@zoltrix said in Dynamic DNS & Namecheap:
logs show the "/services_dyndns_edit.php: phpDynDNS (XXX): (Unknown Response)" error.
https://redmine.pfsense.org/issues/12816
There is a patch in the new System Patches 2.0 package. (recommended patches are now listed in it)
I do not get the unknown response error when clicking Save and Force Update. I get "(Success) IP Address Updated Successfully!" but 2-3 minutes later the page times out and it logs a " *406 upstream timed out (60: Operation timed out) while reading response header from upstream" error.
This patch doesn't work anymore, but there's an updated one that works here:
https://github.com/pfsense/pfsense/commit/70db168b7f7eb4d4e702f965aa4956e93340575f?diff=unified
-
@thearamadon thanks, worked perfect!
