https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162023-03-03T09:58:06ZpfSense bugtrackerpfSense - Feature #14067: Force Dynamic DNS to fetch public IP instead of using WAN IPhttps://redmine.pfsense.org/issues/14067?journal_id=659842023-03-03T09:58:06ZJim Pingle
<ul></ul><p>It would also be nice in some rare cases to force it the opposite way, to disable the check entirely so it will use the address it has no WAN no matter what.</p>
<p>So this could have three choices:</p>
<ul>
<li>Auto (current default, uses check IP service when WAN is "private")</li>
<li>Always use Check IP Service</li>
<li>Never use Check IP Service</li>
</ul>
<p>Might make sense to implement <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Allow dynamic DNS client entry to specify which Check IP service to use (New)" href="https://redmine.pfsense.org/issues/9063">#9063</a> alongside this (the ability to select a specific Check IP service for a DynDNS entry)</p> pfSense - Feature #14067: Force Dynamic DNS to fetch public IP instead of using WAN IPhttps://redmine.pfsense.org/issues/14067?journal_id=659862023-03-03T09:58:13ZJim Pingle
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-1 priority-4 priority-default" href="/issues/9063">Feature #9063</a>: Allow dynamic DNS client entry to specify which Check IP service to use</i> added</li></ul>