Note: This documentation is still in progress, not reviewed properly, and might contain some errors or outdated images. It's intended for the upcoming 4.0.0 release, so configuration settings might be different from previous versions.

Upgrading to v2.1.1

Overview

Version 2.1.1 is the first maintenance release following v2.1.0, addressing critical security vulnerabilities and initial bugs discovered after the release of v2.1.0. This update focuses on stability and security improvements without introducing any database changes or new features.

Upgrade Instructions

  1. Download latest tarball from GitHub
  2. Backup your files before proceeding
  3. Replace all files with content from the downloaded archive
  4. Restore your configuration file (inc/config.inc.php) from backup

Security Improvements

  • Fixed critical XSS vulnerabilities in zone and record management interfaces
  • Patched SQL injection possibilities in search and filtering functions
  • Enhanced input validation for DNS record submissions
  • Improved session security and cookie handling
  • Added additional sanitization for user input throughout the application

Initial Bug Fixes

  • Resolved installation issues reported after v2.1.0 release
  • Fixed character encoding problems with international domain names
  • Corrected record validation for certain DNS record types
  • Addressed issues with zone transfers and zone creation
  • Fixed JavaScript errors in the record editing interface
  • Corrected CSS rendering problems in various browsers
  • Resolved issues with PowerDNS API integration

Usability Improvements

  • Improved error messages for common DNS configuration mistakes
  • Enhanced form validation with better user feedback
  • Fixed sorting and pagination in zone and record listings
  • Better handling of large zone files
  • Optimized database queries for improved performance
  • Updated language translations for better internationalization

Notes

  • No database schema changes are required for this update
  • This release is fully backward compatible with v2.1.0
  • The update is strongly recommended for all users due to critical security fixes
  • This update addresses the most commonly reported issues following the v2.1.0 release