I have bit of a situation here, and I don't know the best way to tackle it..
I have a DSL Line that is 1.5Meg, in the remote office, and it goes through to T1 back to the main office. The DC is also at the main office. I plan to get a secondary domain here.. The issue is, the internet is horribly slow and needs to be fixed. I can upgrade our DSL line to 10 or 25meg, however I don't think we see a difference because we would be bottlenecked by the T1. The T1 also handles our backups and some of the fileshares.. Ideally, we would just break away from that office network wise all together and do all of the backups and drive shares locally. That is my plan for the future, however right now, that isn't an option..
So, is there a way for the internet not to be routed back through their T1 but leave it be for the local resources? I think it is a Cisco 2600 router. I will try to get as much details as possible if needed..
Best Answer +BudMan , 04 February 2014 - 13:56
Sure its quite possible to route internet out your own local connection vs back to home office over the T1. Just need to created the more specific routes of the networks at the home office or that are available through that connection. And then point your default route at your remote location down your new faster internet pipe.
As to DNS queries and dhcp.. Well I would assume he is serving local dhcp - but that has nothing to do with internet access. As to dns queries - his AD queries are not related to internet queries.. But sure on his local dns, I would point it to internet dns so it uses his new local internet vs forwarding to say his home AD to have it forward or query roots, etc.
So reread you have no onsite DC? Where do you query dns? I have to assume your AD dns if your local devices are members of your AD. That you don't want to mess up.. You could run local DNS, that has NS records for your AD dns to solve that problem.. So all AD related goes to AD, while other public dns would go out your local internet connection to a public/ISP dns server, etc.Go to the full post