DNS on 2 Servers

[tvanduzee]

Hello

I have 2 replicated DNS servers in 2 cities. (Both are local DC's/File servers).
City A also has app server for a program called Job Boss
City B replicates to A and back again so that both servers are the same.

The Job boss server is accessed via both cites (Through Sonicwall VPN).
I have the Primary DNS (on the Job Boss server) set to City A's DC.
I have the Secondary DNS set to City B's DC (which is replicated).

Job Boss is accessed via TS (RDP Connection)

Both cities are part of the same LAN (different subnet) 192.168.0.x and 10.10.2.x

My dilema is this: If I set Primary DNS to City A's DC then accessing the server via RDP is sped up drastically and City B's access to the Job Boss server is slowed down. And visa versa if I switch Primay/Secondary DNS.

Is there a solution to this or is this just the way it has to be?

Thank You
Terry

 

[dawks]

Not sure what your asking, but I'd set all the systems in City A to use City A's DNS server as Primary, and all the systems in City B to use City B's DNS server as Primary.

 

[AFurryReptile]

Not sure what your asking, but I'd set all the systems in City A to use City A's DNS server as Primary, and all the systems in City B to use City B's DNS server as Primary.

That's pretty much what I got out of this too.

DNS should have no effect on the speed of a TS application. Location and bandwidth is what matters. If it is the INITIAL CONNECTION that's slower for you... well, that makes sense. If the primary DNS is looking at a remote site - not finding the TS - then searching the secondary DNS - only then finding the TS - this makes complete sense.

 

[Comblues]

Umm...

DNS Replication - Let both DNS Servers update each other and perform local lookups accordingly.

Easy enough.

I've worked with DNS Servers with 10,000 entries or so each - with a primary and backup on 3 sites (in a similar scenario as the one you have described) with no service degradation.

If the servers are in sync - your world will be golden.

Comblues

 

[tvanduzee]

The users use RDP to access this application; which resides only on one server. To one location it is local, to the other it is remote.
The application is launched on the app server, not on the client side.

So, the application server (IP: 192.168.0.3) I have set its dns to be local (192.168.0.30) and the secondary to be remote (10.10.2.30).

When users from the remote site do their RDP session and run the app, their connection takes forever to establish (through our Sonicwall VPN). Locally all is fine. When working in the App, it is Ok at best. I cannot make 2 copies of the app database because it must be "real time data".

Is there a better way to set this up?

 

[seepy83]

It sounds like you're just not happy with the performance of RDP over your WAN links/VPN.

Am I missing something here, or is that really the problem? If that's the problem, then I would look at getting a faster connection between the two sites.

 

[dawks]

Yea, this doesnt sound like a DNS issue. More so the connection between the sites. Try a higher bandwidth link at City A (higher upload being key). And make sure City B has adequate download speeds to match.

 

[Exterous]

What model Sonicwalls do you have? You could consider setting up BWM on it to prioritize your VPN connections if thats an option on your firewalls