DNSExit DynDNS Cached IP Problem

Gertjan · Feb 28, 2017, 6:33 PM

:)

Great !

kevindd992002 · Jun 6, 2017, 12:10 AM

I got the same problem now and here's the result:

[2.3.4-RELEASE][root@pfSense.condo.local]/root: host checkip.dyndns.org
checkip.dyndns.org is an alias for checkip.dyndns.com.
checkip.dyndns.com has address 216.146.43.71
checkip.dyndns.com has address 91.198.22.70
checkip.dyndns.com has address 216.146.43.70
checkip.dyndns.com has address 216.146.38.70
[2.3.4-RELEASE][root@pfSense.condo.local]/root: curl checkip.dyndns.org
<title>Current IP Check</title>Current IP Address: {public IP}
[2.3.4-RELEASE][root@pfSense.condo.local]/root:

Gertjan · Jun 6, 2017, 3:16 PM

@kevindd992002:

I got the same problem now and here's the result:

[2.3.4-RELEASE][root@pfSense.condo.local]/root: host checkip.dyndns.org
checkip.dyndns.org is an alias for checkip.dyndns.com.
checkip.dyndns.com has address 216.146.43.71
checkip.dyndns.com has address 91.198.22.70
checkip.dyndns.com has address 216.146.43.70
checkip.dyndns.com has address 216.146.38.70

That ok.
checkip.dyndns.org uses multiple hosts.
One will be picked automatically.

@kevindd992002:

[2.3.4-RELEASE][root@pfSense.condo.local]/root: curl checkip.dyndns.org
<title>Current IP Check</title>Current IP Address: {public IP}
[2.3.4-RELEASE][root@pfSense.condo.local]/root:

That's NOT good.
It shouldn't be {public IP} but your WAN IPv4 ….
IF this was the case (we can't know) then all is well : the check works for you : checkip.dyndns.org returns the correct IPv4. So : no problem.

kevindd992002 · Jun 6, 2017, 9:16 AM

Yes, I understand that checkip.dyndns.org uses multiple A records for rudimentary load balancing purposes.

What do you mean by your second statement? I understand that the IP can be queried properly when you use "curl". So what is "not good" about this?

Gertjan · Jun 6, 2017, 3:15 PM

@kevindd992002:

Yes, I understand that checkip.dyndns.org uses multiple A records for rudimentary load balancing purposes.

So no problem there….

@kevindd992002:

What do you mean by your second statement? I understand that the IP can be queried properly when you use "curl". So what is "not good" about this?

So, no problem neither ….

Still :
@kevindd992002:

I got the same problem now and here's the result:

[2.3.4-RELEASE][root@pfSense.condo.local]/root: host checkip.dyndns.org
checkip.dyndns.org is an alias for checkip.dyndns.com.
checkip.dyndns.com has address 216.146.43.71
checkip.dyndns.com has address 91.198.22.70
checkip.dyndns.com has address 216.146.43.70
checkip.dyndns.com has address 216.146.38.70
[2.3.4-RELEASE][root@pfSense.condo.local]/root: curl checkip.dyndns.org
<title>Current IP Check</title>Current IP Address: {public IP}
[2.3.4-RELEASE][root@pfSense.condo.local]/root:

What is the problem ?

kevindd992002 · Jun 6, 2017, 3:46 PM

The problem is the same as in my OP. Here are the system logs that show the same:

Jun 6 08:18:05 php-fpm 40642 /services_dyndns_edit.php: phpDynDNS (condo1.linkpc.net): (Unknown Response)
Jun 6 08:18:05 php-fpm 40642 /services_dyndns_edit.php: phpDynDNS (condo1.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.
Jun 6 01:01:10 php-cgi rc.dyndns.update: phpDynDNS (58947837): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
Jun 6 01:01:04 php-cgi rc.dyndns.update: phpDynDNS (condo1.linkpc.net): (Unknown Response)
Jun 6 01:01:04 php-cgi rc.dyndns.update: phpDynDNS (condo1.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.
Jun 6 00:11:50 php-fpm 20683 /rc.dyndns.update: phpDynDNS (58947837): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
Jun 6 00:11:44 php-fpm 20683 /rc.dyndns.update: Dynamic DNS (condo1.linkpc.net) There was an error trying to determine the public IP for interface - wan (igb0 ).
Jun 6 00:11:44 php-fpm 20683 /rc.dyndns.update: Dynamic DNS dnsexit (condo1.linkpc.net): IP address could not be extracted from checkip.dyndns.org
Jun 6 00:11:12 check_reload_status Updating all dyndns

And I get a 0.0.0.0 again in the dashboard for DNSExit DynDNS.

Gertjan · Jun 6, 2017, 5:58 PM

It's not the same problem.
Read again : https://forum.pfsense.org/index.php?topic=126000.msg695869#msg695869
Some major details are :
…..
Feb 22 19:02:26 php-fpm 1088 /rc.dyndns.update: Dynamic DNS: updatedns() starting
Feb 22 19:02:30 php-fpm 1088 /rc.dyndns.update: Dynamic DNS dnsexit (public FQDN): <public ip="">extracted from checkip.dyndns.org
.....

the Cached IP is not equal to the Public IP extracted from checkip.dyndns.org. It does update it successfully but the Cached IP still remains 0.0.0.0. Please help.

and:
@kevindd992002:

I managed to solve the problem already! You know what the causes is? It was a freaking defective RJ11 cable from the phone socket to the VDSL splitter! Who could've thought RJ11 cables break.

So, I advise you to change your "RJ11" cable :)

Your issue (new thread maybe ?) : "checkip.dyndns.org" used by the GUI isn't retrieving any information.

Tell us about your setup - images about settings how you setup the "DNSExit" DynDNS.

Btw : "https://condo1.linkpc.net/" == 112.203.118.128 and point to your ( ? ) pfSense Gui access page. That's nice, and considered as bad, very very bad ;)

Look at this :
https://github.com/pfsense/pfsense/blob/master/src/etc/inc/dyndns.class#L1382
Text return from your DynDNS host should contain :
"No Change In IP Address"
or
"IP Address Changed Successfully!"
If not, it will return "Unknown Response" as it did, because it returns :
(from your log) :
"OK 4=IP not changed. To save our system resources, please don't post updates unless the IP got changed."

and true, neither the first text (string), neither the second exists in the reply (also called the PAYLOAD).

It is very possible that DNSExit changed this text that it returns (btw : you undrtood the reply ?) tries to update the IP (that was already in place !!). Do so more often and they might blacklist you ….
In that case pfSense (the code - file /etc/inc/dyndns.class - lines 1382++) should be modified.

To check why "checkip.dyndns.org" shows you "IP address could not be extracted from "checkip.dyndns.org" :
The option :
Verbose logging - Enable verbose logging
on the page where you setup your DNSExit is set ?</public>

kevindd992002 · Jun 7, 2017, 6:35 AM

I don't think it's the RJ11 cable again. The only thing that prompted me to change the RJ11 previously was because I was getting obvious drop in speeds everywhere. But this time my speed is getting the advertised 100Mbps down.

Please see attachment for my DNSExit configuration. I just enabled verbose logging and got this:

Jun 7 14:24:35 php-fpm 18023 /services_dyndns_edit.php: phpDynDNS (condo1.linkpc.net): (Unknown Response)
Jun 7 14:24:35 php-fpm 18023 /services_dyndns_edit.php: phpDynDNS (condo1.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.
Jun 7 14:24:35 php-fpm 18023 /services_dyndns_edit.php: Dynamic DNS dnsexit (condo1.linkpc.net): _checkStatus() starting.
Jun 7 14:24:33 php-fpm 18023 /services_dyndns_edit.php: Dynamic DNS dnsexit (condo1.linkpc.net): _update() starting.
Jun 7 14:24:33 php-fpm 18023 /services_dyndns_edit.php: Dynamic DNS (condo1.linkpc.net): running get_failover_interface for wan. found igb0
Jun 7 14:24:33 php-fpm 18023 /services_dyndns_edit.php: Dynamic DNS dnsexit (condo1.linkpc.net): {public IP} extracted from checkip.dyndns.org
Jun 7 14:24:26 php-fpm 18023 /services_dyndns_edit.php: Dynamic DNS: updatedns() starting

1.) Yes, I know that security is very bad on my part. But how do you publish the pfsense website with security in mind? Do you have to build a web proxy for it?

2.) Yes, I understand about the Payload and it's not like I'm doing this very often to be blacklisted. I've done it just a couple of times while testing (twice so far since this started again). So no worries here.

3.) So if the pfsense code should be modified to fix this, what do I need to do to confirm that it is really the cause of the problem? DNSExit's support sucks and they don't know a thing about their infra.

Gertjan · Jun 7, 2017, 8:20 AM

Make a copy of this file on your pfSense : /etc/inc/dyndns.class
Now, edit it : https://github.com/pfsense/pfsense/blob/master/src/etc/inc/dyndns.class#L1384
Change
"No Change In IP Address"
into
"IP not changed"
and see what happens.

Normally, the "(Unknown Response)" will be gone because the "IP not changed" situation will now be recognized.

When ok, check also if what the reply will be from DNSExit when de IP did change. Can you force an IP change ?
pfSense thinks it is "IP Address Changed Successfully!" but this could have been changed to …

If you just want to make accessible from the outside == WAN the pfSense GUI then a VPN would be more appropriate.

Btw : no one forces you the stay with DNSExit - many others exists, and they do all the same for you.

kevindd992002 · Jun 7, 2017, 1:13 PM

Thanks. I'll try that.

Yeah, I really want to go away from DNSExit but I'm looking for a free service. DynDNS was good until they put a price to it.

kevindd992002 · Jun 7, 2017, 1:56 PM

I just went with NO-IP and that immediately solved the problem, lol. I'm not sure why I didn't think of that in the first place.

commandoathens · Aug 27, 2017, 8:51 PM

Hi i have same problem after the latest update the DNSexit IP is 0.0.0.0 even after force update.Ofcourse I tried everything of course
Any ideas?

Gertjan · Aug 27, 2017, 11:22 PM

I proposed a solution. Repair the error (the return string isn't recognized) and Bob's your uncle.
Or even better : use another DynDNS supplier.

Are you sure you tried all that ?

kevindd992002 · Aug 28, 2017, 4:06 AM

The solution for me was to change dynamic DNS provider. I can conlude that DNSExit sucks big time. I use NO-IP this time around and it has been working flawlessly eversince.