• Completes feature request #1005. To change record types, you can either start typing in one of the other fields to open the record for editing, or you can click on the record type to open the record for editing. Record types are editable as a dropdown list based on accepted record types in the config file.
• Completes feature request #974.
• Includes bug fix for item #1003.
• Includes bug fix for item #999.
• Fixed quick zone search on Zones page so that either mouse or keyboard can be used.
• Added config options for the PTR lookup pop-up when hovering over A records and for changing record types. Either can be set to true or false.
• Added Delegate PTR module which allows you to give subnets smaller than /24 to users of WebDNS so they can control the PTRs.
• Added larger list of TLDs to the config file. TLDs can be uncommented for use.

• Bug #924 fixed.
• Includes the prefs-patch, so no need to download that patch.
• Fixes issue with the IP Blocks module. The issue was that if you selected to create the PTR records and the reverse zone did not exist, the system failed to create the reverse zone. This release fixes that and the reverse zones will automatically be created if they did not exist.
• WebDNS will now allow you to create a new zone and NOT put it into a group if you wish.

• Re-work of the log search form. Allow users to enter the zone name they would like to search on. Automatically do a search upon loading the logs page. Any new installations will not have their zones in groups, so searching by group is pointless.

• Added addInBulk module, allowing users to add multiple records to a single zone from a tab delimited file.
• Removed auto-complete feature from Search Zones text input field so that the browser history dropdown doesn't overlap the list of zones found from the search.

• Completed merge/consolidation of javascript code.
• Removal of unused functions.

• Addition of the modules system, which will allow users to expand the functionality of WebDNS.
• Moved the IP blocks code into a module, as it won't be needed by all users.
• Moved the mass records update into a module, as it won't be needed by all users.

• Overhaul of the AJAX code, now allowing it more easily run multiple requests at the same time. Also, better utilization of the functionality in the javascript class in use.
• Re-write of the records edit code. Any user having the edit permission can now simply type their changes and click a button a save the changes. You no longer have to click each line individually to "open" it for editing.
• Added ability for mass record updates to be reverted (super users). This functionality will be rolled out further in the near future.

• New feature added. A fourth user type was added to the groups/users section. The user types and their permissions are as follows:
  1. Super user: Full control over the WebDNS system.
  2. Admin user: Full control over a group. This includes modification of group preferences and creation and deletion of zones within the group.
  3. Full group user: Full control over all zones and users within a group. This user cannot modify group preferences, create zones or delete zones. They can add, modify and delete users and records within the group.
  4. Restricted group user: May have up to 5 different permissions on specific zones within the group. Permissions for these users are handed out on a zone by zone basis. The permissions they can have include creating, modifying and deleting records and creating and modifying users.
  The newest user type is the Full group user. Previously, group users would be categorized as Restricted group users. They can have permissions on multiple zones, but those permissions have to be delegated out zone by zone. The Full group user overcomes that limitation, allowing these users to instantly have "admin-like" permissions over the group.

• New feature added. The deletion and modification of records can now be reverted back to their original form from the logs page. After any deletion or modification of records, the user will be presented with a message stating that the changes can be reverted along with a link to the log page. The log page will show the most recent changes for the zone and there will be a life preserver icon next to any record changes. Clicking on that icon will revert the changes mentioned in that log statement. The icon will then be changed to a check mark to denote that the changes were reverted and a new log statement will be created.
• Exporting a zone is now a forced-download. The user will receive a text file of the zone. This file is in the same format used to upload new zones into the system.

• Bug fix in the IP blocks script, specifically for removing blocks. It was reporting that it removed certain blocks (when multiple blocks were chosen for removal) and that it hadn't removed any PTR records when just the opposite was true. It didn't remove the forward records and did remove the PTR records. This has been fixed.

• Added "Load" link on the main search results page for users to load the zone of any record found in a search.
• Added a hover on the Type column of record display (both on Zones page and Search page) that will display a corresponding PTR record for any A record in the result set. Supers will also see a "Load" link to load the reverse zone of the PTR.

• Major overhaul of layout and styles. Virtually all styles have been brought under CSS control. Tables have been removed from the layout in favor of CSS layout.
• Revamped quick zone search for supers. The search is now performed as you type, with results popping up below. The result is an ability to find what you want faster.
• Brought together all the IP block items into 1 page. Super users can now add and remove entire blocks of IP address records (forward A records and reverse PTR records) by just entering in a block in CIDR format.

• Fixed bug created by 1.2.3 which gave regular users a PHP error on the zones page. This was the result of attempting to verify the zone being loaded was apart of the user's group without first loading the user's group.
• Updated logging statements to include more (better) information about what changes took place. Basically, what changed FROM this TO that.

• Added a "Zones in this Group" box for super users, allowing them to switch between zones within the currently loaded group quickly.
• Changed how the pagination works for zone listing boxes on the Zones page for both super users and regular users. Instead of clicking links to view the zones page by page, you can use a scrollbar to quickly skim all available zones. This also allows a user to use the Ctrl-f keys on the keyboard to quickly find the zone they want.

• Better handling of PEAR errors recieved by AJAX calls. Non-ajax requests use a redirect when they encounter a PEAR error, but the ajax calls cannot do that. Now when an ajax calls comes across a PEAR error, we send the ajax call a HTTP/1.1 500 error, using the PEAR message as the text of the error. The ajax call then takes the message and puts it in our error block at the top of the page, just as Horde does.
• Condensed the functions that handle the ajax repsonseText. Instead of having seperate handlers to handle each type of request, we have 1 that handles any ajax call that simply spits our innerHTML.

• Overhaul of the users page.
• Added AJAX pagination widget for super users to find and load groups more efficiently.
• Added PHP page to handle AJAX calls for various user page templates, such as adding a group, adding a user, etc.

• Complete re-work of the main search page.
• Searches from main search now use the same code as searches for records on the zones page, except it is on a global scale (spanning multiple zones).
• This added full editing and deletion capabilities to the main search page. Again, this is on a global scale now, so users can modify records across multiple zones from a single page. From the zones page, this requires loading each zone seperately.
• Completely removed the concept of users having a default zone. This fixes a bug where users could no longer use the system if their default zone was removed.
• Regular users who have no permissions on any zone or Admin users who have no zones listed in their group, can still log into the system and navigate. These users will not have the Zones icon at the top. Users are able to see and use the Users section. From there, Admin users can add permissions for specific zones to users who didn't previously have any zones. Before this change, users without any permissions on any zone would not even be listed on the users page.
• Added ability to remove permissions from users from the Users page.

• Added an Options tab.
• Added the following user preferences for personalization of WebDNS: Zone and Record Change Notification, Preferred Start Page, Records Per Page.
• Added the following group preferences which are only modifiable by the group admin. Changes get propogated to all users within the group. Group Preferences: Password Timeout, Password Length.
• Added ability for all users to delete multiple records at one time.
• Fixed bug which allowed users to modify NS records after clicking on the "Open All For Edit" button. NS records never had an edit icon next to them.

Since this changelog was created well after WebDNS was put into production, we're starting the version numbering after many changes and feature enhancements have already taken place. Below is where we are at today (a brief overview).

• Initial deployment, July 2005.
• Global search of zones and records from main search page. Searches are based on user permissions meaning you can only get info on zones you have permissions for.
• Zones pages displays records using an AJAX call to the server.
• Searches from zones page are "local" to the currently loaded zone and are executed through an AJAX call to the server, the page does not refresh.
• All users can add records to zones, add zones to the system and add users to the system with the correct permissions. Users belong to groups and each group has 1 group admin who has complete control over all users and zones within that group.
• The zones page offers the ability to "export" a zone, essentially creating a BIND-like zone file.
• From the zones page, super users can modify a zone (change it's group, type and assign a master server to it), delete a zone from the system, perform a mass record update (like 1000's of records at once) and delete multiple records at one time.
• Super users have access to all zones in the system through a quick search input field on the zones page. This also performs an AJAX call to the server to get a list of zones that meet your search criteria.
• The users page gives users the ability to edit user information, add new users or change their passwords with the correct permissions.
• Super users can add new groups (customers) to the system from the users page.
• The logs page allows users to search for changes pertaining to zones in which they have permissions.