Well, I see a couple different ways of looking at this.
From a web site developer standpoint (making/modifying/deleting HTML pages) you could install FrontPage Server Extensions on each web site, set up the permissions there, and then give each admin the permissions to use the extensions to make changes to his/her web site. The admins would have to use FrontPage to modify the site's pages, so it depends on how you feel on that!
Now, for a physical file structure and logical web site administration standpoint, this is an entirely different situation. Yes, with FP extensions, you can make new folders under your web site, but if you need to modify the Web Site properties themselves, then the admins need to use the MMC snap-in for IIS (Internet Services Manager). Now, in order to do THAT, they need to be able to connect to your Win2K server over the WAN on the NetBIOS TCP ports, so you will have to ensure they are open (not blocked by firewalls).
Also, you would need to have the Win2Kserver as a domain member of a domain that has a trust with every other domain (all 110 domains), so each admin in his/her own domain can authenticate and connect. This is the part that is more difficult.
Do the remote NT domains trust your centraldomain? That would sure be a lot of trusting going on, but that is OK.
It should be possible, though, to do what you suggest. YOu "could" configure a central server with 110 IP addresses, and configure each site to use a different site. Then, setup the NTFS security permissions on each site to allow the remote Admin from his/her own trusted domain access to their web site' files/folders.
You could also set up the remote admin's account to be an operator in the web site Properties.
I don't think the setup, though, is gonna be done in an afternoon. You are gonna have to test this one out.
But from a purely physical nature, I "think" IIS can handle it.
