[DDNS]Zoneedit update URL changed?

wallabybob · Aug 15, 2011, 11:13 AM

DNS-O-Matic will update dynamic DNS entries on a number of different providers. I'm not sure if zoneedit is supported. See http://www.dnsomatic.com

DNS-O-Matic is supported in pfSense.

jimp · Aug 15, 2011, 6:27 PM

From /etc/inc/dyndns.class:

				case 'zoneedit':
[...]
					$server = "https://dynamic.zoneedit.com/auth/dynamic.html";

jimp · Aug 15, 2011, 6:29 PM

For the fun of it…

From git blame:

9b8dc821 (Scott Ullrich   2006-05-04 00:37:01 +0000 279)                                        $server = "https://dynamic.zoneedit.

If it changed, it sure wasn't recently… though that URL matches. It's been active on that URL for at least 5 years. :-)

breese · Aug 15, 2011, 11:06 PM

The change started back in april of this year…

So far the pppoe in pfSense is working for me.
Right from Zoneedit's Blog

This specifically applies to ZoneEdit users who use Dynamic DNS updates (most often to serve websites from their own home servers).

Please update your dynamic clients to point to dynamic.zoneedit.com if they are not already pointed at that location. There are still some clients pointed at legacydns.zoneedit.com, and when an account migrates, this configuration will no longer work. However, regardless of whether you are on the legacy system or the new system, pointing your client at dynamic.zoneedit.com will work properly.

If you have any other questions regarding where to point your dynamic update clients, please let us know in the comments.

jimp · Aug 15, 2011, 11:09 PM

So the new site has been up for years, and people were still using the old one. pfSense has been using the "new" one for years already, so that notice doesn't impact us at all.

EddieA · Aug 16, 2011, 10:22 PM

@breese:

Please update your dynamic clients to point to dynamic.zoneedit.com if they are not already pointed at that location. There are still some clients pointed at legacydns.zoneedit.com, and when an account migrates, this configuration will no longer work. However, regardless of whether you are on the legacy system or the new system, pointing your client at dynamic.zoneedit.com will work properly.

From memory, as I use ZoneEdit, when they announced the migration, they told all users to change the registration address to legacydns.zoneedit.com, because at that point they hadn't migrated people to the new servers.

As they migrated people, they were told to go back to the "old" address of dynamic.zoneedit.com.

So, what happened, is that for a period, between the start of the migration, and the point that your account was migrated, the updates failed, because pfSense still, as it always had, pointed to dynamic.zoneedit.com.

Cheers.

zlyzwy · Aug 17, 2011, 2:02 AM

I am now moving to the Freedns and it works fine to me.

For Zoneedit, I still can't update the IP.
Even it shows no problem(green) in PF, I didn't see any change in Zoneedit.

Yes, I was using legacy zonedit(http://legacy.zoneedit.com/) and it was no problem for me..

wallabybob · Aug 17, 2011, 5:25 AM

@zlyzwy:

Even it shows no problem(green) in PF, I didn't see any change in Zoneedit.

What does the pfSense dynamic DNS log say? (Use pfSense shell command # clog /var/log/system.log | grep -i dyndns ).

zlyzwy · Aug 17, 2011, 5:37 AM

clog /var/log/system.log | grep -i dyndns

Aug 17 13:27:52 pfsense php: : DynDns: updatedns() starting
Aug 17 13:27:52 pfsense php: : DynDns debug information: 116.230.179.118 extract ed from local system.
Aug 17 13:27:52 pfsense php: : DynDns: Current WAN IP: 116.230.179.118 Cached IP : 124.77.18.120
Aug 17 13:27:52 pfsense php: : DynDns debug information: DynDns: cacheIP != wan_ ip. Updating. Cached IP: 124.77.18.120 WAN IP: 116.230.179.118
Aug 17 13:27:52 pfsense php: : DynDns: DynDns _update() starting.
Aug 17 13:27:58 pfsense check_reload_status: Updating all dyndns
Aug 17 13:27:58 pfsense php: : DynDns: DynDns checkStatus() starting.
Aug 17 13:27:58 pfsense php: : DynDns: Current Service: freedns
Aug 17 13:27:58 pfsense php: : DynDns debug information: 116.230.179.118 extract ed from local system.
Aug 17 13:27:58 pfsense php: : phpDynDNS: updating cache file /conf/dyndns_wanfr eedns'zlyzwy.cn'.cache: 116.230.179.118
Aug 17 13:27:58 pfsense php: : phpDynDNS: (Success) IP Address Changed Successfu lly!
Aug 17 13:28:00 pfsense php: : DynDns: updatedns() starting
Aug 17 13:28:01 pfsense php: : DynDns debug information: 116.230.179.118 extract ed from local system.
Aug 17 13:28:01 pfsense php: : DynDns: Current WAN IP: 116.230.179.118 Cached IP : 124.77.18.120
Aug 17 13:28:01 pfsense php: : DynDns debug information: DynDns: cacheIP != wan ip. Updating. Cached IP: 124.77.18.120 WAN IP: 116.230.179.118
Aug 17 13:28:01 pfsense php: : DynDns: DynDns _update() starting.
Aug 17 13:28:02 pfsense php: : DynDns: updatedns() starting
Aug 17 13:28:04 pfsense php: : DynDns: DynDns _checkStatus() starting.
Aug 17 13:28:04 pfsense php: : DynDns: Current Service: zoneedit
Aug 17 13:28:04 pfsense php: : DynDns debug information: 116.230.179.118 extract ed from local system.
Aug 17 13:28:04 pfsense php: : phpDynDNS: updating cache file /conf/dyndns_wanzo needit'zlyzwy.cn'.cache: 116.230.179.118
Aug 17 13:28:04 pfsense php: : phpDynDNS: (Success) IP Address Updated Successfu lly!
Aug 17 13:28:04 pfsense php: : DynDns debug information: 116.230.179.118 extract ed from local system.
Aug 17 13:28:04 pfsense php: : DynDns: Current WAN IP: 116.230.179.118 Cached IP : 116.230.179.118
Aug 17 13:28:04 pfsense php: : phpDynDNS: No change in my IP address and/or 25 d ays has not passed. Not updating dynamic DNS entry.
Aug 17 13:28:06 pfsense php: : DynDns: updatedns() starting
Aug 17 13:28:06 pfsense php: : DynDns debug information: 116.230.179.118 extract ed from local system.
Aug 17 13:28:06 pfsense php: : DynDns: Current WAN IP: 116.230.179.118 Cached IP : 116.230.179.118
Aug 17 13:28:06 pfsense php: : phpDynDNS: No change in my IP address and/or 25 d ays has not passed. Not updating dynamic DNS entry.
Aug 17 13:30:01 pfsense php: : DynDns: updatedns() starting
Aug 17 13:30:01 pfsense php: : DynDns debug information: 116.230.179.118 extract ed from local system.
Aug 17 13:30:01 pfsense php: : DynDns: Current WAN IP: 116.230.179.118 Cached IP : 116.230.179.118
Aug 17 13:30:01 pfsense php: : phpDynDNS: No change in my IP address and/or 25 d ays has not passed. Not updating dynamic DNS entry.
Aug 17 13:30:03 pfsense php: : DynDns: updatedns() starting
Aug 17 13:30:03 pfsense php: : DynDns debug information: 116.230.179.118 extract ed from local system.
Aug 17 13:30:03 pfsense php: : DynDns: Current WAN IP: 116.230.179.118 Cached IP : 116.230.179.118
Aug 17 13:30:03 pfsense php: : phpDynDNS: No change in my IP address and/or 25 d ays has not passed. Not updating dynamic DNS entry.

breese · Aug 17, 2011, 9:56 AM

On the 11th I contacted customercare@zoneedit.com
They told me there were no ddns issues known.

On the 12th I sent another message to them and behold… on the 15th they sent me
There was an issue last week with dynamic DNS not updating the zone. This should be working now.

You might want to have them check your account / ddns logs.