Setup instructions for DDNSServ 10.6

Please note this feature limited demo will not allow IP address updates. When you are ready to make your purchase please visit
http://www.dyndnsservices.com/purchase.htm If you need any help with setup and configuration please do not hesitate to email support at sam@dyndnsservices.com

 

System Requirements
The following System requirements must be met before the Server application will operate correctly.

1. Windows Server 2000-2003 Family Operating system
2. Latest Security updates available from http://windowsupdate.microsoft.com
3. IIS, Domain Name System (DNS), SMTP service installed and operating correctly. "All available from Control Panel-add remove programs-Windows components"
4. Fully Qualified Static IP address or Persistent IP address, and a Connection to the Internet.. Blocked ports, Proxies and firewalls may hinder your ability to run the server application.
5. At least one Fully Qualified Domain Name with your server listed as its primary or first listed name server.

(Optional)

1. SQL Server 2000 or later or MySQL 4.0 or later.

 

Installing DDNSServ
Below you will find a basic break down of the steps needed to install DDNSServ.. These instructions assume you are familiar with IIS, SMTP and DNS on Windows Servers. Support services are offered free of charge, and unlike most support system you will generally receive near immediate attention. Please email dyndns@seznam.cz for support.

1. Install the file ServerSetup.exe located in the (ServerSetup) directory.

2. Open the (Copy to Web Root Directory). If you are using SQL Server 2000, open the (Copy to Web Root) directory found under the (SQL Server 2000 support) directory. If you are using MySQL open (Copy to Web Root) directory found under the (MySQL Support) directory

3. Open the file Specs.inc in your favorite text editor. Change email fields and SMTP options. Save shanges and exit the file Specs.inc. (If you are using SQL Server 2000 edit the file global.asa as well, entering your SQL Server name, User-ID and Password. Save changes and exit the file global.asa.). "Note this file is often marked as hidden, and you may need to set your folder view settings to edit the file specs.inc"

4. Copy all files found in the (Copy to Web Root Directory) to the websites web root that will host DDNSServs's .ASP files. Generally file:///C:/inetpub/wwwroot.You must copy these files to the root of your web directory, and not a virtual directory. The files must reachable by http://www.yourdomain.com/dnsman.asp and not http://www.dyndnsservices.com/virtualdir/dnsman.asp.

5. If you are not using SQL Server or MySQL ensure the file DDNSDATA.mdb is allowing read-write access. In your web root/database directory right click on the file DDNSDATA.mdb and choose properties, then security. Ensure the everyone group, or the IIS anonymous user account has Read, Write and execute permissions to the file DDNSDATA.MDB. If you are using MySQL or SQL Server skip this step.

6. If you are using MySQL or SQL Server complete this step otherwise skip this step. If you are using MSSQL restore the DDNSDATA backup into SQL Server. MSSQL or if you are using MySQL see this document.

7.  DDNSServ needs an administrative account to make DNS updates. There are two options available.

    1. Set access levels via IIS anonymous access. more information can be found here. (Simplest)
2..2003 Server can use Application pools to set security. Or you can also use COM+ to set security levels.
8.Browse to http://www.yourdomain.com/adminlogin.asp with your favorite web browser.

9. Logon to the Web-Admin. the Default User Name is Admin and the Password is Password The UserID and password are case sensitive.

10.You need to enter all the domains you want to use with your service and change appropriate fields "Each field Within the Web-Admin contains Instructions and a Description" All domains must be setup as primary on the server DDNSServ will connect to prior to there addition within the Web-Admin.
 Please Note: If you are unable to make changes, or add new items via the Web-Admin. Check access rights to the Your-Web-Root\Database\DDNSDATA.MDB database. ensure the everyone group has at least read and write access to this file.

Client Application Configuration
In order to create your client install package you will need to download and install the NSIS installer system. you can download this application here http://prdownloads.sourceforge.net/nsis/nsis20b3.exe?download

Once you have downloaded and installed NSIS you must configure the Client application to use your domain. This is done by running the file Edithost.exe and entering the domain that hosts DDNSServ's asp scripts
(EditHost.exe can be found in the Client Config and Compile directory)

You will next need to edit the Client.nsi file found in the Client Config and Compile directory. You will then need to compile your setup package.
1. Open Client.nsi in your favorite text editor.
2. Near the top of the Client.nsi file you will see an entry which says Your Company Name. Change the value Your Company Name to the name you wish to use for your setup package.
3. Save changes and exit the file Client.nsi.
4. Using the right mouse button, right click on the file Client.nsi and choose the compile option. This will create a file named ClientSetup.exe in the Client Config and Compile directory.
5. Test the setup package by running the new ClientSetup.exe file. If everything is OK distribute the file ClientSetup.exe to your users.

YOU MAY NOT CHANGE OR EDIT THE FILE LICENSE.TXT AND YOU MAY NOT EXCLUDE IT FROM YOUR DISTRIBUTION PACKAGE. FAILURE TO COMPLY IS A VIOLATION OF YOUR LICENSE AGREEMENT.
 
Web Based User Interface.
The Web based user interface enables a friendly web based DNS management system, and also enables support for additional IP update clients.

Note: The web interface is a relatively new addition to DDNSServ and as such may contain yet undiscovered errors. Support issues relating to this interface will receive top priority. Please report any errors to dyndns@seznam.cz You will also likely want to edit these pages to change the layout or look of the interface. Please backup these files before making changes.

To install the Web Based User Interface. Please complete the following steps.
1. Open the Web Interface/Copy to Web Root directory.
2. Copy the contents of this directory to the base directory that is hosting the server ASP scripts choosing yes to overwrite Passlook.asp.
3. Open the following URL in a browser of your choice. http://www.yourdomain.com/signup.asp ensuring you replace yourdomain.com with domain hosting the server application.
4. Complete the signup process and ensure things are working correctly.

Additional clients are included with the web interface. A plug in file for DynSite http://www.noeld.com is provided, as is a LinkSys router client written in Python by a very competent programmer. Bobby W Griggs bgriggs@pobox.com Which can be used with any OS capable of running Python. Both of these clients require modification. The readme.htm file found in the Clients directory should be reviewed before making any changes. More clients will be added all the time so you should check back often for updates.

Below are the basic URL's used to access the Web Based User Interface.
http://yourdomain.com/signup.asp --User Signup Page
http://yourdomain.com/ulogon.asp --User Logon Screen
http://yourdomain.com/companel.asp --User Control Panel
http://yourdomain.com/zoneman.asp --User Domain Manager
http://yourdomain.com/IPUP.asp --IP Settings Screen
http://yourdomain.com/passlook.asp --User Password Lookup
http://yourdomain.com/payit.asp --Registration Screen

 

Common Error Resolution
If your problem is not listed below please contact dyndns@seznam.cz with error details. I will be more than happy to address your problems or answer any questions you may have.

COMMON PROBLEMS
******************************************************************************************
I have installed the server application and compiled my client application. When I run the client I receive the following error Could not connect to Server Ensure you are connecting to a ****
The first step you take when receiving this error is to validate the server installation. Open http://yourdomain.com/dnsman.asp in your web browser. If you are prompted for a password recheck the IIS anonymous access settings. If you receive an error 404 file not found your problem lies in the fact that your website is not configured correctly, you should always be able to reach the file dnsman.asp and its output should be similar to the dnsman.asp found at http://dyndns.dyndnsservices.com/dnsman.asp
******************************************************************************************
I make changes via the Web-Admin but my changes do not take effect, I can also add users via the client software but soon encounter an error stating Bad User-ID or Password.
Your database is not allowing write access. Browse to the location of DDNSDATA.MDB right click on the fie then choose properties from the dialog, when the properties window opens choose the Security tab and ensure the user Everyone has at least Read and Write access. It may be necessary to add the user Everyone.
******************************************************************************************
I am able to add users via the client software but am unable to add any records. Error states please try again.
There are several possible causes for this error. You should first check the servers Event Viewer-Application Log and look for any error titled vbruntime. If the error states Access Denied, you are using a user with insufficient rights to manage DNS. Check your IIS anonymous access settings and ensure you are using a user-Id with sufficient rights to manage DNS. If the error states Generic Failure,  check the DNS server settings via the Web admin and ensure you are connecting to the correct DNS server, it is also possible that you are attempting to connect to non Microsoft DNS server, or that the server you are connecing to does not have the DNS provider dnsprov.dll and dnsschema.mof installed on it.
******************************************************************************************