This message was deleted.

To resolve a DNS name, user's PC sends the DNS query to the user's local DNS servers. The local DNS servers are configured for recursion where they walk the DNS tree to resolve DNS names on the user's behalf. While walking the tree, the local DNS server will be given a list of NetScaler ADNS services that can resolve the DNS name and the local DNS server will choose one at random (you have no control over this).

Thanks Carl, I've gone through your website geo location section already. Trust me, your site is the first thing I look at, in case of any technical doubts. 🙂 In my current environment, we have 4 GSLB netscalers. I was told that based on user's location, user's request is sent to the netscaler nearest to his physical location. How or where in netscaler can I check this? under GSLB/database and entries/static database, I dont see any database in my netscalers. This where I got the initial doubt whether or not we are using static proximity in netscaler. How can I check it in netscaler?

Least Response Time is not proximity.

In here, as soon as a database file is present and method is set to “static proximity”, it will use this file.

Yes, that is exactly where I checked. Under static databases, there is nothing. In GSLB virtual servers, method is set to least response time.

if you are using optimal gateway routing then least response time should be fine as you’ll end up on the correct gateway eventually.

yes we use ogr. But I want to know whether we use proximity db or dns - least response time on the initial connection.

You’ve answered that one yourself, there’s no DB and everything is set to least response so you aren’t using proximity

thanks.. 🙂