Archives of the TeradataForum

Message Posted: Wed, 02 Aug 2006 @ 17:02:51 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

I'd try all the suggestions that have been previously mentioned and it that doesn't improve things you could do the following:

As a test, I would create entries in my host file and see if that improves you connection time. If it does, by a noticeable amount, then you know it's a DNS issue. I've been to sites where the DNS servers just didn't respond quick enough. Because you are asking the DNS for entries multiple times a delay in a DNS response can be multiplied by the number of nodes you have. If it turns out to be a DNS issue you can check the order of the DNS server entries. It's possible that it's always going to a server that doesn't have the entries, or is timing out first, before it goes to the DNS that actually knows about your Teradata nodes.

There's also a "switch" in most OS's that dictates where to look first, in the host file or in the DNS. It's possible to change this "switch" to point to the one you want to do first and that might speed up you response. I've found this to mostly be true when you have the other situation though. Where you don't want to ask the DNS, because the DNS won't know about it. Instead you want it to look in your host file.

You can also do a tracert command to see how many hops you are taking to get to your DNS. The more hops would typically indicate a longer latency. I'd also check this against your Teradata nodes.

Robert Meunier

	<Prev	Next>		<<First	<Prev	Next>	Last>>