DNS Redirector will act as DNS server for network clients regardless of their operating system. DNS Redirector should always be the first DNS server that clients use and not installed behind other DNS servers.

Only when used as an initial redirector (typically in a wireless HotSpot environment to show a welcome or advertisement page) the machine running DNS Redirector and all network clients must be in the same IP address space and cannot be separated by a router or firewall.

This is necessary to ensure DNS Redirector can track clients joining and leaving the network.

Limitations:

· 2 concurrent clients allowed

What's New in This Release: [ read full changelog ]

· Corrected adverse behavior in any keywords list when lines or keywords had blank spaces
· Corrected an issue where a comment (starting with the ; character) before a regex would cause a crash
· Corrected spelling mistakes in some log items
· Logs now go in the \DailyLogs folder
· Added authonline.dnsredirctrl.com lookup, see FAQ 97
· Changed JoinType= valid options are Online/Auth/Both
· Added ResetClientFile= which when looked up sets client defaults (not authorized, not bypassing the block)
· Removed TimeRestriction options which were confusing and limited
· Requires .NET Framework 4 Client Profile