Non Dynamic DNS Entry
We have 4 locations in different cities. They are all connected with a Frame Relay T1. Each has it's own internet connection independant of the Frame. We use a WEB app that is housed on a server in a co-location which is connected to the main office by a direct T1. Each office has a windows 2000 server running DHCP for different subnets and DNS. The primary DNS is on the main DC in the home office and the others replicate from it. Here is the situation. We want the outlying offices to connect to the web app through their independant internet access, instead of coming into the main office through the frame and then to the CO-lo through our dedicated T1. But, we still want the main office to connect through the dedicated T1. What I need to know is how can I set up a DNS entry on the remote servers to this which will direct them over the net while not replicating so that the main office will still use the dedicated T1? Any Ideas?
Software/Hardware used:
Software/Hardware used:
ASKED:
July 13, 2005 8:50 AM
UPDATED:
July 13, 2005 1:16 PM
Answer Wiki:
You might consider setting up a static route on whichever device you have routing your traffic, i.e. send packets addressed to this IP out via this interface. Depending on where you have the internet and FR connected. Assuming your webapp is hosted somewhere off your head office IP range.
To see all answers submitted to the Answer Wiki: View Answer History.
This isn’t a DNS issue. It is a routing issue. What routing protocol are you using? You need to adjust the costs of the routes so traffic from the remote offices will preferentially use the internet but will fail over to your T1 if internet access is lost. The main office should have costs set to prefer the T1.
rt