the ISP DNS should be the primary for the remote sites, and your AD/DNS as secondary.
The reason I have it like that is that my intranet site and my citrix servers run only on my network, and are hosted in the internal server's DNS. I actually tried reversing the order but then my intranet site wouldn't load and my workstations couldn't connect to my citrix farm, because my ISP's DNS server didn't know anything about my internal network (obviously) the more infrastructure redundancy you have, the better. Setting up will be more work, but the maintenance is almost nil, and the benefits would be you would have avoided this problem. I was concerned about the bandwidth that would be required with 4 servers now doing dynamic DNS updates across the WAN line. This has been what was preventing me from setting it up this way to begin with. Thanks Len, wasn't sure you were still around :) Sharyn To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
