Securepoint Dynamic DNS log messages
Last adaption: 08.2023
New:
- Layout adjustment
notempty
This article refers to a Resellerpreview
-
Log messages on the website
Invalid host name
Invalid hostname: $HOSTNAME- Category
Error
- Cause
The account credentials were correct, but the specified host does not exist or the user does not have permission to update this host.
- Solution
The correct host name must be entered in the DynDNS client.
No change
OK, no change: $IP- Category
Warning
- Cause
The host name was updated, but the same IP as before was used again.
- Solution
No user action is necessary as long as this message does not appear too often. The guideline here is that there should be no more than one update per 30 minutes. If this message is generated too often, further update attempts of this host are prevented for a certain time.
Update-Server
Please use as update server in your client "update.spdyn.de" (current setting: $SOME_OTHER_HOST)- Category
Error
- Cause
The DynDNS client has successfully updated the host, but failed to connect to the correct update server.
- Solution
In the DynDNS client, "update.spdyn.de" must be specified as the update server.
- Hint
- update.spdyn.de (IPv4/IPv6) [preferred server]
- update4.spdyn.de (IPv4)
- update6.spdyn.de (IPv6)
Updating hosts is possible through one of the following servers:
Log messages of the DynDNS client in the UTM
SSL Peer Certificate
SSL peer certificate or SSH remote key was not OK- Cause
- the server certificate was not issued for the host entered in the "Update server" field
- the server certificate has expired
- the certificate chain of the server certificate is incomplete
The DynDNS client in the Securepoint UTM validates the certificate of the entered update server before the update is performed. This error message is generated when this validation fails because: