On Mon, Nov 16, 2009 at 1:29 PM, David W. McSpadden <[email protected]> wrote: > Using article http://www.amset.info/netadmin/split-dns.asp
<movie theater> "Don't go in there!" </movie theater> There should be no need to start mucking around with DNS here. Look at why you can't access your website by it's public DNS name and public IP address from within your network. That *should* work. Don't go create another problem while not solving the first problem. Claiming authority for a DNS zone for which you are not delegated *will* cause you grief in the future. At some point, something will change, and you won't be notified, or you'll just forget, and you'll end up posting to this list asking why it won't work, and when that happens, I'll link to this message and say "I told you so." So, if you persist in this ill-advised split DNS idea: Hi David in the future! -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
