Hey thanks John. Let me start by stating that I appreciate your response and as always you have given solid advice. I do have an extensive plan that involves transactional data replication because both sites need to be able to manage content. My only real concern is that the DNN application uses the portal alias table, and the portal alias table will be overwritten during replication. Also, I am a little concerned that I will not be able to use the DNS server to redirect the users to the proper local instance regardless of which site they happen to be at. For example, if I live on the east coast, but I am visiting the west coast, I want to hit the west coast server; and visa versa. The other begging questions ask: How scalable is this DNS solution? How many web servers can I add as DNS entries? and so on...
My solution also involves clustering at every end-point. So each web server and database are in a high-availability environment.
Finally, I really have no need for load balancing. It is a fairly light application, with limited user access, and bandwidth to spare since all the users will be hitting their local instance.
I also agree with you that the web farm document does contain some of the info I need, but that said, I could not find any information about using transactional data replication with the DNN database device.
I think that I am going to have to set up a lab to test my possible issues and address my concerns. If I am able to address these concerns, I will likely have to create a document that outlines my findings. I will try and post it to the community if/when I finish.
Thanks again,
John