During a recent server migration project I encountered something I hadn't seen before. It was two different IIS site definitions with independant bindings, yet each site point to the same physical folder containing DNN and therefore pointing to the same database.  Both sites seemed to work just fine, but is this a reasonable practice?  Or was it just luck that it didn't experience problems to that point.?  I'm guessing problems weren't encountered because it was the same person maintaining each site.

When migrated, they were setup in a single IIS site definition with the combined site bindings corresponding to all portal aliases.  It accomplished the same thing, and I assume it consumed fewer system resources.

Am I wrong to assume that multiple site definitions against a single folder isn't consider best practice?

...rick...