Tornevall Maintenance and DNS updates

As our hosting conditions is about to radically change, the decision has been made to push away some of our DNS services. The services moved to Linode can not be used as recursive services. We’ve also completely removed the “microweb”-services, since they are practically empty and no longer necessary.

This is what’s happened during this weekend:

NS3.TORNEVALL.NET

  • Relocated to Linode DNS.
  • Removed service in JP

Removed

139.162.124.220
2400:8902::f03c:91ff:fe87:3989

Linode replacement

162.159.27.72
2400:cb00:2049:1::a29f:1a63

NS4.TORNEVALL.NET

  • Relocated to Linode DNS
  • Removed service in NL

Removed

141.138.204.6
2a02:348:83:cc06::1

Linode replacement

162.159.27.72
2400:cb00:2049:1::a29f:1a63

Deprecating APIv3 for APIv4 – Rebooting the API

Tornevall Networks has plans to deprecate v3.x of the current TorneAPI-package. One of many reasons is that many functions are still bound to the netcurl 6.0-series – one other reason is an upcoming RSS-interface. There are also efficiency issues within the API that has been a problem. Not publicly but for internal perfomance. The first plan was to go APIv4, but instead there could be a major change – a reboot. Version 3 will remain in place, to handle DNS requests until there’s a new stable.

With this deprecation change, the DNSBL will got itself a major issue: Removals are now forced. This also means that a full removal procedure will be sent to the DNS even if the requested IP address is not confirmed listed.