DNSKong Version 1.0.6
Copyright 2000, Pyrenean
email Pyrenean

DNSKong is free for individuals for personal non-commercial use.
Commercial users contact Pyrenean for license details.

After installing DNSKong you must configure your system to use 127.0.0.1 as the first Domain Server. The file, tcpipreg.reg contains the registry entries needed; however, manual configuration is the best method to use. For help on how to perform manual configuration consult:

• Controlling DNS Lookup Sequence
• Controlling DNS Lookup Sequence for Windows2000

You must keep the configuration files Named.txt and pass.txt in the same folder as DNSKong.exe

Notes:

1. We don't care what you filter. This distribution does not include a Named.txt nor a Pass.txt. You will need to create these in Notepad or download these from a DNSKong user support site.
   As a test entry you can add the keystring:
   www.pyrenean.com
   to your Named.txt. This keystring will only filter the pyrenean web site. We hope you will remove that entry, but you can filter anything and everything you want. Each entry must be on a separate line. Although comments and blank lines in Named.txt will improve overall readability future versions of DNSKong may dynamically resequence these files for improved performance.
   Inclusive set of rules for different purposes may be gathered from domain names in publically available hosts files. The rule file approach, Named.txt, is much smaller than a matching hosts file. The rule search resolves a domain name to 127.0.0.1 when it first finds a matching entry in Named.txt.
   
2. The rules are predictive. Use minimal names for Named.txt and specify exactly the names you want to pass DNSKong. This is the exact opposite of the approach you would take with hosts.
   
3. With DNSKong, you don't need hosts. You can use hosts with DNSKong. You machine checks Hosts first, then DNSKong, then your other Domain Name Servers.
   
4. DNSKong is compatible with web proxies or proxy servers. Your browser will route its request through your proxy server before your machine looks up an entry in Hosts or DNSKong. Your proxy configuration is processed first. You need to use a personal web server to avoid missing pictures or web pages that your proxy or web browser expects from 127.0.0.1.
   
5. DNSKong forces IE5.0+ to cache Domain names so once you've resolved a name the browser will not need to requery the DNS for some time. If you decide to remove an entry from Named.txt after a displaying a web page you will need to exit your browser prior to being able to see the matching web page.
   
6. Performance of DNSKong should be similar to performance using Hosts.  Performance is important and depends on many factors. For example, smaller filters will give DNSKong better overall performance, just as a small Hosts file speeds up Hosts lookups.
   
7. You will experience minor browser differences using DNSKong rather than hosts. In general, DNSKong filters more than hosts. Hosts only filters specific names, DNSKong filters names that contain any match from the Named.txt file.
   
8. DNSKong nows offers DNS proxy support. You can use this option to select 5 DNS servers that DNSKong will use to lookup domain names provided the names are not filtered. If you do not use this option you will not need to allow DNSKong access to the internet under ZoneAlarm. If you choose to use this option you will need to configure ZoneAlarm to allow DNSKong access to the Internet. This feature can be used to proxy to a DNSKong Enterprise server and may not offer any performance improvement over your current network configuration. If you use the feature you can determine that DNSKong has proxied a name request by the tray icon which will have the upper kong-block gray and the two lower kong blocks green when a name has been proxied. Some machines need to have a priming operation prior to proxying DNS lookups through DNSKong. The easiest way to prime the proxy is to use the command-line ping or tracert command to a known domain name.
   
9. If using the proxy fill the entries from top to bottom. This feature is included with this release in order to permit chaining DNSKong personal servers to DNSKong enterprise servers. You may also use genuine DNS servers if you would like to the extend the number of available Domain Name Servers for your machine.

DNSKong only is available to the local machine, so even without a firewall machines will not be able to access your DNSKong. Contact Pyrenean to get a server version of DNSKong that will allow a single machine to act as a DNSKong server. On personal machines, firewalls should be configured to allow local only access for DNSKong and block Internet access to DNSKong.

Configuration can be difficult. For reference on how to do this consult the tutorials "Controlling DNS Lookup Sequence" referenced by hyperlink above.

The idea is to set up your machine to use 127.0.0.1 as the first DNS Server.

On NT/9x and WinMe, use Network properties to examine TCP/IP protocol settings. Add 127.0.0.1 as your first DNS entry.

Win2K requires more effort. The network Internet TCP/IP properties dialog does not like 127.0.0.1 as a DNS Server address. The advanced properties button can be used to add 127.0.0.1 as the first DNS on the list. You most likely will need to disable the DNS Client. You will need to reboot your machine after making the DNS entry and disabling the DNS Client service. Your Win2K machine may act differently than our test computers. This procedure has worked on the few Win2K machines that we have available for testing.

If you run a firewall continue to do so. You may be able to configure your firewall to block DNSKong access from the Internet. If you use ZoneAlarm, you may need to first pass the block when ZA asks for the first time about DNSKong. Then immediately open ZA's configuration and disallow access.

Some users may need to add 127.0.0.1 as a machine on the local net for ZA. Use the security tab and look in the Advanced features button to add this address. The IP 127.0.0.1 is a Universal IP reserved for the local machine.