[SAC] [Hosting] Upcoming DNS & DHCP infrastructure changes

Committees SAC mailing list
1

All,

Over the last several months we’ve been working on replacing our aging DNS & DHCP system which uses a php frontend/backend called Maintain, tinydns for the DNS server and ISC DHCP. We’ve been using this system since our inception almost 15 years ago. This old system has many limitations including proper IPv6 support and DNSSEC.

The new architecture will be based entirely on Bind and ISC DHCP with no frontend software. We’ll be maintaining zones we manage inside of a git repository. If you’ve relied on the old Maintain frontend for access to zones, please let me know so we can work out methods for getting access to make changes.

We’re at a point where we are very close to cutting over to the new system. However, in the meantime I wouldn’t mind some feedback and testing. We have one public server using the new architecture which we plan to switch over to production first. It’s only getting updates manually from the current system on an as-needed basis, but any zones we pull from you should be getting updated automatically now.

Temporary IP’s you can test are:

DNS caching: 216.165.191.55, 2600:3402:600:24::154
Authoritative: 216.165.191.58, 2600:3402:600:24::153

If you can, please test this server and let me know if you run into any issues. I’m hoping to deploy the new system within the next few weeks.

Thank you!

···

Lance Albertson

Director
Oregon State University | Open Source Lab

2

Hi Lance - thanks for the email .. speaking only personally, I think part of the decades-late adoption of IPv6 is that fundemetnally, IPv6 numbers are not human firendly, and IPv4 are.. so if youre new systems require human operators to configure with IPv6 with any regularity, there will be inevitable stress.. The solution is to always have some semi-automated way of connecting parts that are IPv6 only.. I know, its easier to say than to do.. but thats my feedback .. thanks for the great 15 years there ! here is to 15 more reliable years
best regards from Berkeley
--Brian M Hamlin

On Thu, 8 Jun 2017 16:56:44 -0700, Lance Albertson <lance@osuosl.org> wrote:

All,

Over the last several months we've been working on replacing our aging DNS & DHCP system which uses a php frontend/backend called Maintain, tinydns for the DNS server and ISC DHCP. We've been using this system since our inception almost 15 years ago. This old system has many limitations including proper IPv6 support and DNSSEC.
The new architecture will be based entirely on Bind and ISC DHCP with no frontend software. We'll be maintaining zones we manage inside of a git repository. If you've relied on the old Maintain frontend for access to zones, please let me know so we can work out methods for getting access to make changes.
We're at a point where we are very close to cutting over to the new system. However, in the meantime I wouldn't mind some feedback and testing. We have one public server using the new architecture which we plan to switch over to production first. It's only getting updates manually from the current system on an as-needed basis, but any zones we pull from you should be getting updated automatically now.
**Temporary IP's** you can test are:

DNS caching: 216.165.191.55, 2600:3402:600:24::154
Authoritative: 216.165.191.58, 2600:3402:600:24::153

If you can, please test this server and let me know if you run into any issues. I'm hoping to deploy the new system within the next few weeks.
Thank you!

--
Lance AlbertsonDirector
Oregon State University | Open Source Lab

-------------------------

_______________________________________________
Hosting mailing list
Hosting@osuosl.org
https://lists.osuosl.org/mailman/listinfo/hosting

-------------------------

_______________________________________________
Sac mailing list
Sac@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/sac

--
Brian M Hamlin
OSGeo California Chapter
blog.light42.com