OPNsense Forum
Archive => 15.7 Legacy Series => Topic started by: Solaris17 on September 06, 2015, 03:27:53 am
-
cant seem to tell the difference.
I use freeDNS (thanks for supporting this!!) The services page seems to understand this.
WAN freeDNS
however the email system (COOL FEATURE) says this
DynDNS updated IP Address on WAN (re1) to
and the logs indicate this
opnsense: /usr/local/etc/rc.dyndns.update: phpDynDNS (www): (Success) No Change In IP Address
Not a big deal just not sure if anyone reported it. It seems teh script or implimentation was originally statically named for dyndns and as such it reports that dynDNS succeeded but the services page itself seems to know what you are using and what you have selected but the alert text for the logs and email systems do not replicate this change.
-
"DynDNS" being the service rather than the provider... I mean the category name as opposed to the actual thing.
-
I see sorry for the confusion I somehow thought it was the dynDNS provider not enough sleep I guess. /cheers
-
No worries. It gets even more confusing when RFC 2136 enters the picture:
https://www.ietf.org/rfc/rfc2136.txt
I think at some point everything got slushed together as "dynamic DNS", maybe that can be made clearer in the GUI a bit?
-
I actually think it might be a bit difficult since some refer to dynDNS as a service, but adding "service" and "provider" to the outputs seems incredibly tacky.
-
I wasn't clear enough. I meant renaming the instances of "DynDNS" that really mean "Dynamic DNS" to make it a bit less confusing?
-
Sounds like a great idea!
-
Cool, I'll correct the string you mentioned earlier along with a few other obvious candidates. Won't be all of the spots, but at least the most prominent will be named more accurately then. Thanks. :)
-
I lied. I think I got all of them... https://github.com/opnsense/core/commit/27e5ef1c33ca81a10d5e5542033f1794882245ef
-
Thank you! Easy readability is beneficial to everyone!