I use dynamic DNS hosted by Namecheap.com, which is one of the DDNS
vendors supported by the DDNS feature of pfSense.
For a long time, I have had problems where pfSense appears to have
updated the IP address on the DNS server, but in reality, nothing
changes. I've just resorted to manually updating my DNS entries manually
as needed.
I had seen similar problems described in the forums, but didn't see any
real resolution, as many were using the feature without problem.
I recently dug down to try to find out what was really going on, and it
seems to do with the fact that the domain (not counting the host part)
is a 3-part domain. I have the "regular" domain hosted elsewhere and
have delegated a portion to namecheap for managing the dynamic parts.
So namecheap knows my domain as "dyn.example.com", and I have a dozen
host entries within that domain.
I found this bug entry for pfSense:
https://redmine.pfsense.org/issues/2144
Which seems to address a closely related issue, whereby namecheap, of
all the vendors supported, is the only one to require that the hostname
and the domain be submitted as separate fields in the IP-update command.
The bug describes how some simple php string manipulation splits out the
hostname and domain portions by counting 2 (or 3, in the specific case
of .uk domains) segments from the end as the domain portion, and the
rest as the hostname portion.
I do understand, as noted in the bug discussion, the wish to not
complicate the GUI much to accommodate only one vendor out of the
several listed.
Could perhaps a special character be used as a sentinel for the break
between host and domain, and the dyndns.class file will split on that?
Then the only GUI update might be an added instruction sentence for
namecheap users.
For example, I might enter in the pfSense GUI the hostname
host1/dyn.example.com
to indicate which part is which.
-Lance
_______________________________________________
List mailing list
[email protected]
https://lists.pfsense.org/mailman/listinfo/list
