Expiration time
One of the most important of our many features is the
"expiration time".
In contrast to other dynamic-DNS services, we neutralise accounts for which
the regular account updates have ceased. With DynAccess, account updates
take place at fixed (but tariff-dependent) intervals several times per
day.
Why account neutralisation?
Your account is not deactivated, but neutralised, i.e. it is
configured with a neutral IP.
Depending on the chosen tariff, you update your account completely
automatically (!) at various intervals, even when there has been no IP
change. The higher the chosen tariff, the more often these updates are
planned.
| | update-
interval |
updates
per day |
|
| Private A |
6 hours |
4 |
| Private B | 3 hours | 8 |
| Business A | 90 minutes | 16 |
| Business B | 60 minutes | 24 |
| Business C | 30 minutes | 48 |
| HeartBeat A | 15 minutes | 96 |
| HeartBeat B | 10 minuten | 144 |
| HeartBeat C | 5 minutes | 288 |
| HeartBeat A | 45 seconds | 1920 |
| HeartBeat B | 15 seconds | 5760 |
| HeartBeat C | 5 seconds | 17280 |
| our competitors | 24 hours | 1 |
|
| |
| |
| |
| |
| |
| (Advanced SetIP) |
| (Advanced SetIP) |
| (Advanced SetIP) |
| (HeartBeat mode) |
| (HeartBeat mode) |
| (HeartBeat mode) |
| |
|
The goal is to use DynAccess to realise a
quasi-permanent connection and thus a quasi-static IP. Note, however, that
we cannot make a static IP out of a dynamic IP!
If a planned update does not occur, then there is a problem at your end!
The cause can be a disrupted internet connection due to problems with the
telecommunication provider. However, it is also possible that a new
connection isn't possible after a new IP has been assigned due to problems
with the RADIUS servers used by the telecommunication provider. Also,
internal LAN problems can never be ruled out.
If our monitoring system detects this, we configure your account with a
neutral IP. This is to prevent access to someone else's server - for your
old dynamic IP is no longer valid for you. Every other dynamic-DNS
service updates your IP only then when you explicitly register a new IP
with an account update, except perhaps if you configure an offline IP
before a planned disruption, which is not comparable to our
concept.
An example:
You operate an in-house email server on a dynamic IP from a standard
internet-access provider (e.g. T-Online, T-Business Online, ...).
You allow emails to be sent to this email via direct routing, as opposed
to accessing them via POP3 at your hosting provider (e.g.
Ambos InterNet-Solutions)
or via a unified messaging service.
If your internet connection is disrupted due to a problem, then the relation
between the IP and your account as well as the DNS configuration for direct
MX routing still exists. Emails are still sent to the dynamic IP
via which you used to be connected to the internet.
What can happen?
| a) |
Emails cannot be delivered and are returned to
the sender with an error message, unless you make use of our
backup mail exchanger service. |
| b) |
Your "former" dynamic IP was assigned to another
customer of your internet-access provider (e.g. T-Online).
Your emails can then reach his email server (if he is running one, otherwise
see a)). He rejects your emails with the error message "User unknown".
This certainly does not leave a positive impression on your customers. |
| c) |
As described under b), your emails reach someone
else's email server which, however, is configured so that it can
receive them (default in the case of Tobit David)!
Critical emails meant for you land in someone else's hands! |
In order to prevent the scenario described above, we
have perfected the idea of dynamic DNS.
Since we can detect problems at your end, we neutralise your account. When
using a HeartBeat C account, this takes place after just 15-20 seconds!
If you use our backup mail exchanger service, then you are sure not to
lose any email.
Summary:
In order to choose the tariff appropriate for you, you must first
determine the job DynAccess is to perform for you and how important it is
that problems at your end are quickly noticed by our monitoring systems.
When using an in-house email server, we recommend at least the HeartBeat A
tariff. If your are using DynAccess for implementing a VPN tunnel, then
the business A tariff might be enough. Stability and security are increased
by increasing the tariff.
Since we can recognise problems very quickly, the HeartBeat tariffs are
often used for server monitoring (including SMS notification).
Resumé:
It's not a bug - it's a feature!
With DynAccess, you update your account several times per day, even when
your dynamic IP has not changed. This allows regular contact between
you and our DynAccess servers. If a planned update does not occur, then
our monitoring servers notice the disruption of your internet connection.
In this case, we neutralise your account. Access to the wrong servers
is prevented by a meaningful DNS configuration.
When using DynAccess in a business environment, you should consider
a HeartBeat tariff.
|
