Namecheap dynamic dns Not Updating
-
I found a bug for this I believe for dyndns. Mine wasn't updating as well. The cache file name is being called incorrectly according to a bug report. I guess it supposed to be fixed in 2.1.
-
I found a bug for this I believe for dyndns. Mine wasn't updating as well. The cache file name is being called incorrectly according to a bug report. I guess it supposed to be fixed in 2.1.
It works fine in every stable version, any such bugs fixed in 2.1 were only in 2.1 to begin with.
-
My Namecheap DynDNS entry on my edge firewall is still working as far as I can tell.
It's also possible that at the time the OP started the thread, Namecheap had a temporary server-side problem.
-
the dyndns always up .but the namecheap one is my problem.this is my log
php: /services_dyndns_edit.php: DynDns: updatedns() starting
Apr 7 17:46:29 check_reload_status: Syncing firewall
Apr 7 17:46:29 php: /services_dyndns_edit.php: DynDns debug information: 197.251.163.186 extracted from checkip.dyndns.org
Apr 7 17:46:29 php: /services_dyndns_edit.php: DynDns: Current WAN IP: 197.251.163.186 Cached IP: 0.0.0.0
Apr 7 17:46:29 php: /services_dyndns_edit.php: DynDns debug information: DynDns: cacheIP != wan_ip. Updating. Cached IP: 0.0.0.0 WAN IP: 197.251.163.186
Apr 7 17:46:29 php: /services_dyndns_edit.php: DynDns: DynDns _update() starting.
Apr 7 17:46:29 php: /services_dyndns_edit.php: Namecheap: DNS update() starting.
Apr 7 17:46:30 php: /services_dyndns_edit.php: DynDns: DynDns _checkStatus() starting.
Apr 7 17:46:30 php: /services_dyndns_edit.php: DynDns: Current Service: namecheap
Apr 7 17:46:30 php: /services_dyndns_edit.php: phpDynDNS: PAYLOAD: ^M <title>Bad Request</title>^M ^MBad Request
^M
HTTP Error 400. The request is badly formed.
-
the dyndns always up .but the namecheap one is my problem.this is my log
php: /services_dyndns_edit.php: DynDns: updatedns() starting
Apr 7 17:46:29 check_reload_status: Syncing firewall
Apr 7 17:46:29 php: /services_dyndns_edit.php: DynDns debug information: 197.251.163.186 extracted from checkip.dyndns.org
Apr 7 17:46:29 php: /services_dyndns_edit.php: DynDns: Current WAN IP: 197.251.163.186 Cached IP: 0.0.0.0
Apr 7 17:46:29 php: /services_dyndns_edit.php: DynDns debug information: DynDns: cacheIP != wan_ip. Updating. Cached IP: 0.0.0.0 WAN IP: 197.251.163.186
Apr 7 17:46:29 php: /services_dyndns_edit.php: DynDns: DynDns _update() starting.
Apr 7 17:46:29 php: /services_dyndns_edit.php: Namecheap: DNS update() starting.
Apr 7 17:46:30 php: /services_dyndns_edit.php: DynDns: DynDns _checkStatus() starting.
Apr 7 17:46:30 php: /services_dyndns_edit.php: DynDns: Current Service: namecheap
Apr 7 17:46:30 php: /services_dyndns_edit.php: phpDynDNS: PAYLOAD: ^M <title>Bad Request</title>^M ^MBad Request
^M
HTTP Error 400. The request is badly formed.
I'm getting this same error (though with my IP of course) with hostname "@.sub.domain.com" (but actually mine), and 2.0.3-RELEASE.
-
How exactly do you have the Namecheap host setup in the DynDNS settings?
-
How exactly do you have the Namecheap host setup in the DynDNS settings?
Disable: unchecked
Service: Namecheap
Hostname: @.my.domain.co
MX: <blank>Wildcard: unchecked
Username: <blank>Password:</blank></blank> -
How exactly do you have the Namecheap host setup in the DynDNS settings?
(I'm not seeing an edit button to add this to my last post)
I tried on Sunday to change it to having the "wildcard" box checked.
There doesn't seem to be any change. -
(I'm not seeing an edit button to add this to my last post)
If your post is not "too old" there should be a "Modify" link on it.
-
(I'm not seeing an edit button to add this to my last post)
If your post is not "too old" there should be a "Modify" link on it.
It was too old then. I see a modify link on my newer one. I hate double posting >.>
-
I also have this issue. So what I did as a workaround is SCP ddclient (http://sourceforge.net/apps/trac/ddclient/) onto my pfsense box. It is a perl script, so no need to have a specific version compiled for freebsd/x86. I then updated the config for namecheap, and it works great :)
Its a hack, but it works.
-
I cannot do that sadly. I need to use the built in function for this.
-
It may be due to how the update URL gets formed when using the "@" record.
Can you try this with an actual hostname under the domain rather than the @ record?
-
It may be due to how the update URL gets formed when using the "@" record.
Can you try this with an actual hostname under the domain rather than the @ record?
That's not possible with the domain in question. I could try adding one, but I can't until tonight.
(and ultimately it IS the @ record that needs to be updated, so even if this is the issue, I need it to work for the @ records.) -
Yes, I understand that, I'm just trying to make sure it's not a problem with your account in general, but one specific to the @ record handling.
I don't have a free @ record handy that I can tinker with at the moment, but I can try to free one up. All my Namecheap dyndns entries are traditional host.domain.tld format, no @ records.
-
Yes, I understand that, I'm just trying to make sure it's not a problem with your account in general, but one specific to the @ record handling.
I don't have a free @ record handy that I can tinker with at the moment, but I can try to free one up. All my Namecheap dyndns entries are traditional host.domain.tld format, no @ records.
I'll see if I can make an additional one during my lunch.
-
I was able to free up an @ on one of my domains for testing, and it worked for me. No errors, and the @ record updated as expected.
I used the @.domain.tld format and it updated as expected using the dyndns access key for the domain.
Maybe try to re-enable DynDNS for your domain and then use the new auth token they generate when it resets.
-
Oh, and that was on a 2.1 snapshot from Thursday.
-
Oh, and that was on a 2.1 snapshot from Thursday.
I'm not on a snapshot. I'm using the latest stable.
-
I pulled up a 2.0.3 VM and tried it there, worked the same, no problems. I even edited the IP in Namecheap's control panel to something bogus, then removed the cached IP from the pfSense VM and made it update again, worked fine.
