DNS Made Easy DynDNS setup

[jeffc]

Hi Matthew,

That explains it! I don't have a business account, I have a small business account. And indeed, with a small business account, the API isn't available (the pricing clearly shows that).

I'm hesitant to update to a business account, as I just don't need to double the cost for a single dynamic address. I did note that pfSense now supports Hover, which is interesting. Hover is my domain registrar, and I moved DNS to DNS Made Easy solely because of a DHCP address on the WAN. If Hover is now supported directly, then I can completely eliminate DNS Made Easy from my network topology. I'll look at that before looking at upgrading to a business account on DNS Made Easy.

Thanks so much for your help and explanation here - I really appreciate it!

@johnpoz, I did understand what a DNS ID is. I didn't understand what you meant by "record" in the pfSense screens, as no field in pfSense (for DNS Made Easy) is marked as "record".

/Jeff

[johnpoz]

I have small business account as you can see.. You do not need anything more than that.

I showed you the screen in pfsense - what version are you running of pfsense?

Record = Hostname..

I posted a screenshot showing where you put the ID.. Not sure how it could not be any more clear..  Where you NOT seeing the attachments in my post?

[jeffc]

Hi John,

This is very odd. When I did what you said, I get an error. My version of pfSense is: 2.3.4-RELEASE-p1 (amd64).

I've attached pfSense configuration (I mangled my DNS ID for security purposes). When the update occurs, it fails:

Aug 29 08:33:48 php-fpm 55302 /services_dyndns_edit.php: Dynamic DNS: updatedns() starting
Aug 29 08:33:48 php-fpm 55302 /services_dyndns_edit.php: Dynamic DNS dnsmadeeasy (15…57): 50.35.71.245 extracted from local system.
Aug 29 08:33:48 php-fpm 55302 /services_dyndns_edit.php: Dynamic DNS (15025057): running get_failover_interface for wan. found igb0
Aug 29 08:33:48 php-fpm 55302 /services_dyndns_edit.php: Dynamic DNS dnsmadeeasy (15...57): _update() starting.
Aug 29 08:33:48 php-fpm 55302 /services_dyndns_edit.php: Dynamic DNS dnsmadeeasy (15...57): _checkStatus() starting.
Aug 29 08:33:48 php-fpm 55302 /services_dyndns_edit.php: phpDynDNS (15...57): (Error) Invalid username or password

Any suggestions would be appreciated, thanks so much.

/Jeff


[johnpoz]

You didn't really put … in there did you?

I would check your password, from the log looks like you didn't put in the correct password.

here I just did this again.. Took all of a 1 minute to setup. See Attached.

[jeffc]

Yes, I used the actual DNS ID.

I think the problem is that I used special characters in my password (it was a generated password), and that the protocol has problems with certain special characters. DNS Made Easy has a limit of 15 bytes for the password, so I generated a new password that was limited to alphanumeric characters, and that seemed to work fine.

Thus, I'm now all set. Thanks for your help! And just to verify, I have a small business account, and DNS Made Easy works fine with that.

/Jeff

[johnpoz]

Glad to here.. kjnew is was something stupid ;) I didn't notice any mention of any restrictions on the password on dnsmadeeasy site.. I will have to relook, if they do not mention it they should.. Might have to drop them a line.. Might really nice added feature for pfsense to mention the restrictions when you enter the password on the dyn form on pfsense.  But sure they are way busier with than for something some minor as that.

But good catch..

edit:  Ok something not right.. I did get a warning when I made the pass over 15 characters on their site.  But I couldn't find any restrictions on specials.  So I tried using pass!@#$

This gave me this error
Aug 29 12:33:42 php-fpm 73746 /services_dyndns_edit.php: phpDynDNS (56340608): (Error) Record does not exist in the system. Unable to update record

But then I just changed pass to newpass and worked just fine..

So not 100% sure if something on their end or the way pfsense is sending the info?

[jeffc]

There's definitely problems with "complex" passwords. But as long as that's known (and documented), people can work around it.

Thanks again for all your help. It would have taken a bunch of research to try and find some other provider and then switch over to it, taking care to retain all my current services.

/Jeff

[johnpoz]

I just updated the wiki with a note under dns made easy to reflect the complex password thing
https://doc.pfsense.org/index.php/Dynamic_DNS#DNS_Made_Easy

[jeffc]

I don't believe the complex password issue is not specific to DNS Made Easy.

In working with OpenDNS, I also ran into a complex password problem. I couldn't get OpenDNS to work properly with authentication for Dynamic DNS support, so I generated an alpha-numeric password and added a "." character (OpenDNS requires one or more "special characters"). Then it worked fine.

I suspect that the protocol requires some special characters to be quoted, and they're not. But that's just a guess without looking at the code.

I just wanted to point out that the complex password problem is not isolated to DNS Made Easy, it appears to be generic (or at least it extends to OpenDNS as well).

Thanks for your help, it's awesome that you could work with me to make everything work!

For DNS Made Easy users, the key points to take away:

1. Use a "simple" password (alphanumeric), using the 15-byte maximum (for DNS Made Easy) to make things as secure as possible,
2. You do not need a "business" account on DNS Made Easy; any account at all works fine,
3. Enter the DNS ID for both the hostname and the username in the pfSense software.

With those three things, getting DynDNS updates to DNS Made Easy was a snap.

[johnpoz]

I will add those to the wiki notes..