Project

General

Profile

Actions

Feature #9063

open

Allow dynamic DNS client entry to specify which Check IP service to use

Added by Mitch Claborn over 5 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Dynamic DNS
Target version:
-
Start date:
10/24/2018
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:

Description

Please update the dynamic DNS client feature to allow specification of the Check IP service to use at the individual client level.

My use case:
I have a 4G/LTE router that I use as a backup WAN that gets a dynamic IP address. Web traffic through that router goes through some kind of web proxy at AT&T, so the public IP for web traffic is different than that for other ports. I've defined a custom Check IP service to handle the other ports, but it is used for all of the dynamic DNS clients. I need to be able to have one DDNS client for the web traffic that uses a normal (port 80/443) check IP service and one for the other traffic that uses my custom Check IP. This will allow me to get DDNS host names for both uses that I can put in my cloud server firewalls.


Related issues

Related to Feature #14067: Force Dynamic DNS to fetch public IP instead of using WAN IPNew

Actions
Related to Feature #14610: Add source address option to Check IP ServicesNewMarcos M

Actions
Actions #1

Updated by Jim Pingle about 1 year ago

  • Related to Feature #14067: Force Dynamic DNS to fetch public IP instead of using WAN IP added
Actions #2

Updated by Marcos M 9 months ago

  • Related to Feature #14610: Add source address option to Check IP Services added
Actions

Also available in: Atom PDF