Technitium DNS Server

To reset your password, you need to contact the DNS server administrator.

If you are an administrator, follow these steps to reset the 'admin' user's password:

1. Stop the DNS server.
2. Find the DNS Server config folder and locate the auth.config file. The config folder will be found where the DNS Server is installed on Windows or /etc/dns/ folder on Linux.
3. Rename the auth.config file as resetadmin.config
4. Start the DNS Server to complete the password reset process.
5. Just refresh this web page in the web browser to auto login with default credentials and quickly change the password.

Note: To reset 'admin' password, you will need file system access on the server running this DNS Server. If the 'admin' user does not exists then it will be created automatically.

Enter the records to be imported below in standard zone file format:

Note: The $ORIGIN and $TTL values will be automatically set if not specified.

Warning! Overwrite SOA serial option when used to set a lower SOA serial value than the current SOA serial will cause secondary zones to fail to sync.

WARNING! Unsigning the zone without removing all DS records from its parent zone will cause DNSSEC validating recursive resolvers to mark the zone as bogus and fail to resolve it.

WARNING! Make sure that you have removed all of the DS records from the parent zone and sufficient time has passed before unsigning this zone. You MUST wait for at least the number of seconds specified by the DS record's TTL value to elapse before unsigning the zone to ensure that all recursive resolvers would have expired the DS records from its cache. For example, if you have DS records at the parent zone with TTL value set to 86400 then you must wait for 86400 seconds (24 hours) to pass after you delete the DS records from the parent zone. Once you have ensured that you have waited for the appropriate time then you can unsign the zone safely.

NOTE! You can find out the TTL value of DS records for your zone by querying for DS records using the DNS Client tab.

WARNING! Unsigning the zone will permanently delete all of the private keys associated with it. Consider taking a backup before proceeding.

Are you sure you want to proceed to unsign the zone now?

Enter domain names one below other to import into Allowed Zone:

Enter domain names one below other to import into blocked zone:

Edit the dnsApp.config config file below as required by the DNS application.

Note: The app will reload the config automatically after you save it.

The backup process will create a zip file for the items selected below:

Note! The Web Service or Optional Protocols TLS certificate (.pfx or .p12) files will be included in the backup only if they exist within the DNS server's config folder.

Note! It may take several minutes to generate the backup zip file if log files are selected to be backed up which will depend on the size of the log files on the disk.

Warning! The restore process will overwrite existing config files on disk for above selected items and reload new settings including user accounts from the backup. The current logged in user account and current session will be added automatically.

WARNING! Removing a DHCP lease from the server side will NOT remove the allocated IP address from the client side. Make sure that the client assigned this lease is not connected to the network before proceeding.

WARNING! Removing a DHCP lease may cause IP address conflict if the DHCP server assigns the same IP address to a new client while the old client is still connected to the network.

It is not recommended to remove a DHCP lease when the client is still connected or may connect back later to the network before the lease expires. Use this option only as a last resort.

Follow the recommendations below to avoid such a case that requires removing a DHCP lease:

• Use a shorter lease time such that a dynamically allocated lease expires quickly when the client exits the network.
• Use Exclusions to exclude IP address ranges from being dynamically allocated that you plan to assign manually to some of the devices on the network.
• Use Exclusions to make sure that you have unallocated addresses available in the DHCP scope to be assigned as reserved leases in future.
• Rely less on the assigned IP addresses by configuring a domain name for the DHCP scope and accessing all the devices using their domain names.

Are you sure you want to remove the DHCP lease now?