Antcas DynDNS

The DynDNS service from Antcas can be used for free. The address is assigned randomly in the free mode from 16 characters. If a Premium license is used, it is possible to register the following domain: *.my.antcas.com. The * can be replaced by any name. The following characters can be used:

  • a-z, 0-9 and -
  • At least 4 characters
  • Maximum 63 characters

The name must not start or end with a -.

IPv4 and IPv6

If the DynDNS service has been deactivated or the IPv4 mode activated, then the connection to the portal is established only with IPv4. This affects only the initial communication. The VPN and other connections can also communicate via IPv6. In addition to IPv4, an IPv6 assignment can also take place. The service then checks every 5 minutes for a change in the IPv6 address. A connection via IPv6 is fundamentally faster as NAT translation is omitted. If the poll to the IPv6 backend fails, the IPv6 address is immediately removed again.

Note: IPv6 must be allowed in the local network so that the server can establish the connection.

Configuration

To begin configuring the service, the Server must first be registered in the Antcas Hub. The DynDNS service must have been activated in the Remote Access Options. In the Portal, the entry DynDNS is then displayed under the selected Server.

When using DynDNS Premium, a name can be added in the Explorer DynDNS Premium. Enter the complete name (FQDN) or only the prefix for this purpose. If it is valid and available, it will be added. After registration, the name can no longer be used by anyone else. It is possible at any time to assign a name to another server. If no name is used, the random address is used as an alternative.

Note: Only as many names can be reserved as there are servers with Premium DynDNS licenses in the portal.

To check the configuration, the displayed IP address can be checked using nslookup. It may take some time until this is available. In addition, the domain and the IP address are displayed under Remote Access.

If an error occurs on the Server under the domain, then the service has been deactivated under Remote Access, the license has been removed or the IP address of the server has not yet been transmitted.