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.2

Overview

Version 2.1.2 is a maintenance release that addresses several security vulnerabilities and bug fixes identified in v2.1.1. This update focuses on enhancing the stability and security of Poweradmin without modifying the database structure.

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 cross-site scripting (XSS) vulnerabilities in zone and record management forms
  • Patched SQL injection vulnerabilities in search functionality
  • Enhanced input validation for all form submissions
  • Improved session handling and security
  • Better sanitization of user input throughout the application

Bug Fixes

  • Resolved issues with special characters in DNS record content
  • Fixed pagination in zone listing for large DNS installations
  • Corrected display issues with certain record types
  • Addressed browser compatibility problems
  • Fixed JavaScript errors affecting record editing functionality
  • Corrected sorting problems in zone and record listings
  • Improved error messages for better user guidance

Usability Improvements

  • Enhanced form validation with more informative error messages
  • Improved handling of internationalized domain names
  • Better compatibility with various PowerDNS versions
  • Optimized database queries for improved performance
  • Updated language translations

Notes

  • No database schema changes are required for this update
  • This release maintains full backward compatibility with v2.1.1
  • The update is recommended for all users due to security improvements
  • Users running versions earlier than v2.1.1 should first upgrade to v2.1.1 before proceeding to v2.1.2