- Status Closed
- Percent Complete
- Task Type Upgrade
- Category Involved Service
FS#2483 - Upgrade DNS-Servers
We are going to upgrade all DNS-Servers to a new hardware and software version.
With this version upgrade we will introduce new features requested by customers and more stability, security and reduncancy.
With this version upgrade we will introduce new features requested by customers and more stability, security and reduncancy.
Closed by Admin
Friday, 27 September 2019, 12:06 GMT
Reason for closing: Finished
Friday, 27 September 2019, 12:06 GMT
Reason for closing: Finished
Tuesday, 17 September 2019, 06:54 GMT
2019-09-18 08:00 - 18:00
On this timeframe
- dns changes take no effect
- single dns servers not reachable for 30 minutes
Affected services
- Domain
- Webspace
- Server (Revers DNS)
- vServer (Revers DNS)
If an error occurs we will rollback to the old system.
Wednesday, 18 September 2019, 15:32 GMT
2019-09-18 08:00 - 22:00
Wednesday, 18 September 2019, 20:48 GMT
Thursday, 19 September 2019, 06:22 GMT
Known issues after this upgrade:
* Some DNS Zone Entries for Domains are not longer valid. Due to this fact, a domain becomes not resolved for the same level of the invalid entry until this invalid entry becomes deleted or corrected.
* Some DNS Zone Entries for a Domain and/or Subdomain are not longer valid due to malformatted Database timestamps. Customers can update the domain zone by "changing" all entries or make a restore. We will also create an additional fix of this issue during the sync of the values to all DNS-servers.
Saturday, 21 September 2019, 07:43 GMT
Here is the update for known issues after this upgrade:
* Some DNS Zone Entries for Domains are not longer valid. Due to this fact, a domain becomes not resolved for the same level of the invalid entry until this invalid entry becomes deleted or corrected.
->> UPDATE 21.9.2019: WE DO NOT CORRECT THESE INVALID DNS ENTRIES! Customers with invalid DNS-Entries have to correct it themselves.
* Some DNS Zone Entries for a Domain and/or Subdomain are not longer valid due to malformatted Database timestamps. Customers can update the domain zone by "changing" all entries or make a restore. We will also create an additional fix of this issue during the sync of the values to all DNS-servers.
->> UPDATE 21.9.2019: This issue is only informational for customers since it was already automatically fixed at 19.9.2019. Only about 0.01% of all records were affected and fixed.