Feature #52
Additional DNS resolver required
| Status: | Closed | Start: | 2011-01-02 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Votes: | 0 |
Description
It would be desirable to provision an additional Unbound DNS resolver to replace 212.13.194.71. Too much is running on that host; it all needs to be split off to separate VMs. Unfortunately it will not be possible to just move the IP to another host as 212.13.194.71 was provisioned back in the bad old days and a terrible decision was made to not dedicate a service IP to it.
Some time in the next 6 months people need to start migrating to the new IP allocation (85.119.80.0/21) and all infrastructure needs to move first, so it might be an idea to provision the resolver service IP as one of the first IPs from that allocation. When the migration is complete in at least 6 months 212.13.194.71 can be retired.
History
Updated by admin over 14 years ago
Four new resolver hosts have been provisioned, spread across the
infrastructure, along with two service IPs.
These hosts have been placed into a cluster and the two service IPs
will be automatically moved between them to try to ensure highest
availability.
The two service IPs are:
85.119.80.232
85.119.80.233
Documentation has been updated with these new IPs and all new
customers will have their VPSes configured with these IPs as the
resolvers.
The announce list needs to be notified, otherwise I believe the
issue is closed.
Updated by admin over 14 years ago
- Status changed from New to Closed