Dynamic DNS
A DNS feature offered by NetDefendOS is the ability to explicitly inform DNS servers when the
external IP address of the D-Link Firewall has changed. This is sometimes referred to as Dynamic
DNS and is useful where the D-Link Firewall has an external IP address that can change.
Dynamic DNS can also be useful in VPN scenarios where both ends of the tunnel have dynamic IP
addresses. If only one side of the tunnel has a dynamic address then the NetDefendOS VPN keep
alive feature solves this problem.
Under System > Misc. Clients in the WebUI, several dynamic DNS services are defined. The
HTTP Poster client is a generic dynamic DNS client with which it is possible to define 3 different
DNS URLs plus an explicit value for Delay in seconds until all URLs are refetched (with a default
of 604800 seconds, equivalent to 7 days).
Everytime NetDefendOS reconfigures, HTTP Poster will send an HTTP GET request to the defined
URLs. It will also repeat this at an interval specified by the refetch delay.
The difference between HTTP Poster and the named DNS servers in the WebUI is that HTTP Poster
can be used to send any URL. The named services are a convenience that make it easy to correctly
format the URL needed for that service. For example, the http:// URL for the dyndns.org service
might be:
myuid:[email protected]/nic/update?hostname=mydns.dyndns.org
This could be sent as shown above by using HTTP Poster, or the URL could be automatically
formatted for the administrator by NetDefendOS through choosing the DynDNS menu option and
entering the information required for dyndns.org.
The CLI console command httpposter can be used to troubleshoot problems by seeing what
NetDefendOS is sending and what the servers are returning.
Note
Dynamic DNS services are often sensitive to repeated logon attempt over short periods
of time and may blacklist IP addresses that are sending excessive requests. It is
therefore not advisable to query these services too often otherwise they may cease to
respond.
HTTP Poster may be used for other purposes than dynamic DNS. Any need for NetDefendOS to
generate an HTTP GET request can be met by the feature.
3.9. DNS
Chapter 3. Fundamentals
120
Summary of Contents for 800 - DFL 800 - Security Appliance
Page 24: ...1 3 NetDefendOS State Engine Packet Flow Chapter 1 NetDefendOS Overview 24 ...
Page 69: ...2 6 4 Restore to Factory Defaults Chapter 2 Management and Maintenance 69 ...
Page 121: ...3 9 DNS Chapter 3 Fundamentals 121 ...
Page 181: ...4 7 5 Advanced Settings for Transparent Mode Chapter 4 Routing 181 ...
Page 192: ...5 5 IP Pools Chapter 5 DHCP Services 192 ...
Page 282: ...6 7 Blacklisting Hosts and Networks Chapter 6 Security Mechanisms 282 ...
Page 300: ...mechanism 7 3 7 SAT and FwdFast Rules Chapter 7 Address Translation 300 ...
Page 301: ...7 3 7 SAT and FwdFast Rules Chapter 7 Address Translation 301 ...
Page 318: ...8 3 Customizing HTML Pages Chapter 8 User Authentication 318 ...
Page 322: ...ALG 9 1 5 The TLS Alternative for VPN Chapter 9 VPN 322 ...
Page 377: ...Management Interface Failure with VPN Chapter 9 VPN 377 ...
Page 408: ...10 4 6 SLB_SAT Rules Chapter 10 Traffic Management 408 ...
Page 419: ...11 5 HA Advanced Settings Chapter 11 High Availability 419 ...
Page 426: ...12 3 5 Limitations Chapter 12 ZoneDefense 426 ...
Page 449: ...13 9 Miscellaneous Settings Chapter 13 Advanced Settings 449 ...