Very nice. I was always screaming for this -----Original Message----- From: Thomas W Shinder [mailto:tshinder@xxxxxxxxxxx] Sent: Tuesday, April 12, 2005 6:03 AM To: [ISAserver.org Discussion List] Subject: [isalist] HELP: Supporting Illegal Top-level Domains using a Split DNS Infrastructure http://www.ISAserver.org Hey folks, I'm working on this for future release on www.isaserver.org. If you get some time, could you let me know how I can make this easier and more understandable? Supporting Illegal Top-level Domains using a Split DNS Infrastructure: http://www.msfirewall.org/isa2004/splitdns/2004illegaltldsplitdns.htm Thanks! Tom ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Other Internet Software Marketing Sites: World of Windows Networking: http://www.windowsnetworking.com Leading Network Software Directory: http://www.serverfiles.com No.1 Exchange Server Resource Site: http://www.msexchange.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: ara@xxxxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist Report abuse to listadmin@xxxxxxxxxxxxx Attention: This message, including any attachment(s), is intended only for the use of the individual(s) to which it is addressed and may contain information that is privileged or confidential. Any other distribution, copying or disclosure is strictly prohibited. If you are not the intended recipient or have received this message in error, please notify us immediately by reply e-mail and permanently delete this message including any attachment(s), without reading it or making a copy. Any outgoing message has been scanned for possible harmful file(s) or script(s), but it is your sole responsibility to run detection tools as we won't guarantee the safety of message(s).