In article < XXXX@XXXXX.COM >,
If you name it anything that is already used, you best not install DNS
A LONG TIME AGO, one of my first mistakes was setting up DNS, before SBS
was even around, and I called my network Stormy.com, figuring it fit as
it was a development network. Well, I started watching my firewall logs
and found some 600 connections an hour, to what I misread as inbound, of
someone trying to hammer my DNS service (which I didn't expose).
As it turns out, my DNS service was trying to replicate with the real
stormy.com and was hammering their DNS server....
That was a long time ago....
It's best to NEVER name your internal DNS anything that could be public
in name - use microsoft.lan or microsoft.local, but never any TLD name.
If you want microsoft.com to resolve to your internal network, from your
internal network, then create a DNS entry for it.
- Igitur qui desiderat pacem, praeparet bellum.
- Calling an illegal alien an "undocumented worker" is like calling a
drug dealer an "unlicensed pharmacist"
XXXX@XXXXX.COM (remove 999 for proper email address)