We’ve implemented a couple of fixes to the dynamic DNS as follows:

• SSL errors – we’ve swapped out the SSL cert (some clients were not recognizing the intermediate CA, examples: ddclient) and upgraded it to a geotrust cert.
• Some wildcard requests were not recognized as such: FIXED

Some of the effects of the latter were experienced as follows:

• Synology ddns update FIXED
• Invalid Hostname error FIXED
• wildcard DNS wasn’t being updated FIXED

UPDATE: We are now routing email destined for verizon via an alternate route.

Verizon has been blocking our email forwarders since shortly after the migration.

We have entered numerous requests to be unblocked and we have been attempting to establish contact with somebody clueful over there via backchannels, so far no luck.

Impacted customers are encouraged to open a ticket with Verizon and request whitelisting of the new ZoneEdit mail forwarders:

mailfwd1.zoneedit.com: 23.27.50.10
mailfwd2.zoneedit.com: 166.88.18.34


You can also use your mail forwarding abilities to simply forward your email to another destination.

Of interest: easyDNS offers email hosting with it’s domain packages,  see this for more info.

TXT records were truncated at 255 characters after migration which broke some SPF, DKIM and DomainKey records if they were longer than 255 chars.

• The interface now allows larger records to be entered (up to 1024 chars)
• Any records which were truncated but not already fixed by the users have been re-imported.