Setup instructions for DDNSServ 10
 

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

1. Windows Server 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.

 
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.

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.

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

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 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 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 SQL Server skip this step.

6. If you are using SQL Server complete this step otherwise skip this step. Restore the DDNSDATA backup into SQL Server. more information can be found here

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. on 2000 server you can also use COM+ to set security levels. for more information please contact support.
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.