DNSEXIT
-
Dynamic DNS is not updated DNSExit addresses (other sites update OK it looks like a change in response from them. Log attached. The result is that the display stays red and shows 0.0.0.0
Only 1 entry in hostname field.
_[Sep 27 07:00:04 php: rc.dyndns.update: phpDynDNS (alyswork.linkpc.net): (Unknown Response)
Sep 27 07:00:04 php: rc.dyndns.update: phpDynDNS (alyswork.linkpc.net): PAYLOAD: HTTP/1.1 200 OK 4=IP not changed. To save our system resources, please don't post updates unless the IP got changed.
Sep 27 07:00:04 php: rc.dyndns.update: DynDNS (alyswork.linkpc.net): Current Service: dnsexit
Sep 27 07:00:04 php: rc.dyndns.update: DynDNS (alyswork.linkpc.net): DynDns _checkStatus() starting.
Sep 27 07:00:03 php: rc.dyndns.update: DynDNS (alyswork.linkpc.net): DynDns update() starting.
Sep 27 07:00:03 php: rc.dyndns.update: DynDns (alyswork.linkpc.net): DynDns: cacheIP != wan_ip. Updating. Cached IP: 0.0.0.0 WAN IP: 90.246.94.246
Sep 27 07:00:03 php: rc.dyndns.update: DynDns (alyswork.linkpc.net): Current WAN IP: 90.246.94.246 Cached IP: 0.0.0.0
Sep 27 07:00:03 php: rc.dyndns.update: DynDns (alyswork.linkpc.net): 90.246.94.246 extracted from checkip.dyndns.org
Sep 27 07:00:03 php: rc.dyndns.update: DynDNS (alyswork.linkpc.net): running get_failover_interface for wan. found em0
Sep 27 07:00:03 php: rc.dyndns.update: DynDns (alyswork.linkpc.net): 90.246.94.246 extracted from checkip.dyndns.org
Sep 27 07:00:03 php: rc.dyndns.update: DynDns: updatedns() starting[/i] -
I know that this is probably at the irritation level rather a serious problem, but is it likely to be reviewed in a future update?
Andrew
-
Sorry to bump an old topic, but on 2.2 I cant get DNSexit to work at all and it should be really straight forward. I'v done this a million times with other services.
The FQDN is entered and correct, username and password and thats all that should be required. It won't register or update.
Any trickery with their service I should be using?
Log:
php-fpm[92783]: /services_dyndns_edit.php: phpDynDNS (myling.linkpc.net): (Unknown Response)
php-fpm[92783]: /services_dyndns_edit.php: phpDynDNS (myling.linkpc.net): PAYLOAD: HTTP/1.1 200 OK 4=IP not changed. To save our system resources, please don't post updates unless the IP got changed.So, its not allowing an update because it thinks the IP hasn't changed, but it has. The IP that myling.linkpc.net is resolving to is different that whats on the wan of pfsense and definitely different than the red 0.0.0.0 in the gui for cached IP.
I suspect they are treating the attempted update as if its spam and I could understand that if it wasn't the very first attempt to up the IP!
-
For those looking for this, I ran into the same situation recently.
DNSexit's remote update service is kind of annoying, its algorithms are not so optimized apparently. It has some sort of cache and it will always tell you that your IP hasn't change if you have once before submitted that one IP. Even if the host has now a different IP in you account then the one you're passing for update.
But we still can make that work with pfSense (I'm using 2.2.4-RELEASE (amd64)):
Create or modify your Dynamic DNS client configuration and set the Service Type to "Custom". Choose the interface normally and then supply the "Update URL" using the following sintax:
http://update.dnsexit.com/RemoteUpdate.sv?login=YourLogin&password=YouPassword&host=YourHost&myip=%IP%&force=Y
The "force" switch is the most important here, it will bypass the "IP not changed" misunderstanding messages.
And pfSense will repace %IP% with your public IP (for the interface you choose).As per DNSexit's own instructions (for the URL):
"replace the values with your own account and domain data.
myip is optional. If not set, the IP address of your network will be detected and used as the IP for the host(subdomain).
host can have multiple hosts(subdomains) updated at the same time by seperating each host by ;. ie. host=host1.mydomain.com;host2.otherdomain.com.
password is the password for your web login. However, it is recommended that you setup a dynamic IP update password that is different from your web login password. You can login to your account, then go to "Account Profile" -> "IP Update Password" to setup dynamic IP update password. "
The IP Update Password is a good ideia, since this traffic is not encrypted and your password goes in plain text.
So, your configuration will look like the one attached, where the full Update URL example is something like http://update.dnsexit.com/RemoteUpdate.sv?login=mydnsexitaccount&password=Samp1ePassw0rd&host=web1.mydomain.com&myip=%IP%&force=Y
Then the Cached IP field will no longer show 0.0.0.0 (in red). Sometimes it will show a N/A, but eventually will show the current IP (in green). If not, edit the configuration and use the "Save & Force Update".
Cheers,
Victor.
