Install/data/WiFi1.cab/dualserver.zip/README.txt Driver File Contents (WiFi_Intel_Win81_64_VER17025.zip)
Driver Package File Name: WiFi_Intel_Win81_64_VER17025.zip
This release 5.2 is a Stable Release
DHCP Server alots the IP addresses to local computers, while DNS server resolves
You need DHCP Server if you do not want to manually maintain IP Addresses or
you have less IP Addresses than number of machines you have, as dynamic DHCP Server will
recycle IP Addresses on machines.
DNS Server is needed for resolving hostnames to their IP addresses. Normally your
ISP will provide you with DNS Service. You may have your own DNS Server, which will
resolve hostnames by forwarding them to ISP's DNS Server and cache the addresses also.
If you have home/small office network with Unix/Linux machines, these machines will
not be resolved from each other, as Unix/Linux machines do not support NBNS protocol
and you need your own DNS Server.
But how about resolving your local machines ?. Your ISP's DNS Server will not have
this list and your own DNS Server wont have them either. Most DNS Servers cannot do this.
(unless you configure dynamic updates, or use static IP addresses and manually enter them).
THIS SERVER RESOLVES DHCP ALLOTED LOCAL MACHINES AUTOMATICALLY, IN ADDITION TO EXTERNAL
HOSTS, WITH THE ADDED ADVANTAGE BEING, BOTH DHCP AND DNS SERVER ARE ALLWAYS IN SYNC.
You may also like to use this DNS Server as caching proxy for your IPS's server for fast
response. You can disable DHCP Server, if you use static addresses or there is another
DHCP Server being used. Even if you have only one machine you can try it. Enable only
DNS Service, specify remote DNS Servers in ini file and set DNS Server of your machine
to itself. If you only have dialup, create loopback adaptor for testing.
ENHANCEMENTS in 5.2
1) DHCP Options can be specified on DHCP Range Basis also.
2) ClientID, if sent by Client, is returned with DHCP messages.
Bugs Fixed in 5.1
1) Zone Replication Bugs.
ENHANCEMENTS in 5.0
1) This release supports Zone Transfer and Replicaiton.
BUGS Fixed in 4.1
1) BootP Support fixed.
ENHANCEMENTS in version 4.0
1) Multiple Ranges can be specified.
2) Different physical network can be servered by this server using DCHP Relay Agent.
3) Single host can have multiple IPs and single IP can have multiple hosts.
4) Zone based DNS Query routing [CHILD-ZONES] is introduced. This permits splitting
main domain to child zones, using Dual Server.
5) Logging added.
6) Multiple listening interfaces can be specified for multihome servers.
1) Requires little configuration and no need to create zone files.
2) Provides both DHCP and DNS Service, can also use one of them only.
3) Automatic built-in dynamic updates. DNS Server includes DHCP alotted names.
4) Unlimited no. of hosts and aliases can be specified.
5) No limit to cached external hosts.
6) Both global and client specific DHCP Options.
7) Network PXE Boot and BOOTP support.
8) Zone based DNS Query routing (DNS Proxing) to different DNS Servers.
This program if installed on a machine, which is manually configured for IP Address,
DNS & router, it detects these settings from server machine (If you want diffrent
setting for clients, edit ini file) and uses them for configuring other machines on local
1) Installer automatically installs the Program
2) For Windows NT/2000/XP/Vista you should let installer install it as NT Service.
Although program's default installation directory is C:\Program Files\DualServer
but in Windows Vista Home, you should change it to C:\DualServer or some
other directory, not under C:\Program Files, as you may not have access to
C:\Program Files\* for editing config files.
1) Start Menu -> Dual Server -> Run Standalone.
2) If you have installed as NT Service, goto Services Applet and may start/stop
the service "Dual DHCP DNS Service".
Now try getting IP Address for another machine, it should work.
1) Configuration of Server
The program automatically picks up settings of Server computer and
no configuration is required if:-
a) Server machine is configured for DNS Servers and Gateway servers.
b) You use IP range 192.168.0.1 - 192.168.0.255 (Server is automatically excluded).
c) Lease Time is 360000 secs/100 hours.
You can change any of these settings in DualServer.ini file. You need to restart
if any changes are made in configuration file.
2) Configuration of Clients
1. You can use windows/linux/unix mix of clients.
2. The clients should be set to get IP Address automatically.
3. Do not configure the clients for Dynamic DNS Update, as this server automatically
1) This document is for guidance and is covered under GNU public license.
If program is not assigning addresses or resolve them check:-
1) Check network hardware and ensure that client machines has different host names from server and
2) No other service should be running on Server on ports 53 and 67.
3) If you get error like port 67 already in use means some other DHCP program or proxy server with DHCP
service is running. If you get error port 53 already in use means some other DNS Server or proxy server
with DNS Service is already running. Use any port scanner program like Active Ports to detect which program is
listening on these ports. It is also possible that another copy of dualserver itself is running.
or Microsoft connection sharing program is running, which uses these ports.
4) If you get error Static Interfaces/Listening Ports not available, it may be because of 1) Another
DHCP/DNS Server is running or Interfaces specified on [LISTEN-ON] section are not available.
If your interface may not be ready when your computer/Service starts and due to this service
fails to start, use Window's recovery option in Services applet to try starting service at later time.
5) Look at DualServer.log (if running as service) or Run in standalone mode, it will provide all debug
information as it verbatim the activities.
6) If you use Braodband router, which also has DHCP Server, this program may still run, but some hosts
configured by other DHCP Server may not use this DNS or DHCP Service.
7) Often you will find that other machines can resolve each other and server, but server resolves
nothing. This is because server's DNS Server may be different. To resolve machines from server,
specify (forwarding) DNS Servers in ini file and set server's DNS Server to itself.
8) Zone Transfer and Replication, if used on multihomed servers,make sure the IPs for Primary and Secondary
server can be pinged from Each Other.
9) Dualserver.state file backs up current leases and is read back when server restarts. If you want to
clean previous leases, you may delete this file and restart the server.
10)If you are not able to receive DHCP Discover messages from clients, make sure that Dual DHCP DNS Server
and client are on same physical network (not separated by routers). If it is separated by routers and it
is same subnet, please allow routers to pass broadcast messages to Server on Port 67. If these are
different subnets, use the BOOTP relay agents.
Goto control panel's add/remove programs and remove the program.
REPLICATION (for advance users only)
Release 5.0 onwards support zone replication. Please read the ZONE REPLICATION file.
Domain Name Server and Child Zones. (for advance users only)
If you have a domain with multiple child zones, each zone having its own DNS/DHCP or DNS server, You
can use a multizone DNS Server like bind as Main Domain Name Server, which would transfer diffrent
zones from child servers. Dual Server can be very well used as Child Zone Servers with DHCP/DNS for
zone and Domain Name Server would have all the zones transfered from Child Servers.
Dual Server, being single zone server, still provides a way to work as main Domain Name Server for
whole domain. It works differntly but with same results, without even the need to trnasfer child zones.
You can confure 1 or more Dual Servers as Master DNS Server (Domain DNS Server) for whole domain
and these will forward queries to specific zone servers based on zone match. Queries not matching to zones
specified in [CHILD-ZONES] section will be forwarded to default forwading DNS Servers. One query will
be forwaded only once to Child server and then cache is used to resolve unless it has expired.
Please see the [CHILD-ZONES] section of ini file.
Entries in [CHILD-ZONES] behave differently than forwarding server entries in [DNS-SERVERS] secion.
Child Servers are basically meant for child zones queries. For correct behavior you should specify
child zone servers in [CHILD-ZONES] like:-
The child zone can have just one DNS Server or can have primary and secondary with zone replication between
them. Domain Server would contact primary or secondary child zone server, whichever is availabe. You can
specify one server also, if child zone has only 1 server.
Main Domain Name servers should be specified as forwarding servers in child zone dns servers, so that
each zone can also resolve entries in sibling child zones through main Domain Name Server. ISP or Public
DNS Servers should only be specified in main Domain Name Servers.
If you need full backup, minimum 2 DualServers should be used as main Domain Name Server for main domain
with identical configuration and each child zone should have 2 DualServers, with zone replication between
If you find any problem with this program or need more features, please send mail to firstname.lastname@example.org.
You may also send thanks email if it works fine for you.