DNS question

[Domino1]

Can someone help me out here? I was told to use a open dns. This would be a better option than the default dns. Using the tracert cmd I connect through the same ip addresses as using my default dns plus some. I time out occasionally using tracert with the open dns. If my understanding is correct the open dns is more secure with the cache. But my question is If I go through more connections to get there am I less secure? Maybe I am way off base and totally lost here. Any help would be appreciated.

[sagan]

How many hops away is it?

Is it really worth it over your ISP?

[Force Flow]

DNS simply translates IP to domain names and vice versa.

I started using openDNS for home and work (because of latiency issues when trying to resolve domain names) and I can't say I've had a problem since.

Sometimes tracert doesn't always work since some services/servers block the protocol for security reasons, so I wouldn't use that as a benchmark. tracert is intented to trace the path that your request takes between your computer and the destination computer. This trace can take varying amounts of time, if it actually does a full trace at all.

If you open up a cmd window and clear your DNS cache (this is what stores addresses that have already been resolved), then try to ping a domain name, the time it takes between hitting the enter key and seeing the first return ping is the time in which the DNS translation occurs. If it is longer than half a second or so, then you might have a problem.

command to flush the DNS cache:
ipconfig /flushdns

ping a domain name:
ping pcmech.com

[Domino1]

Originally Posted by Force Flow DNS simply translates IP to domain names and vice versa. I started using openDNS for home and work (because of latiency issues when trying to resolve domain names) and I can't say I've had a problem since. Sometimes tracert doesn't always work since some services/servers block the protocol for security reasons, so I wouldn't use that as a benchmark. tracert is intented to trace the path that your request takes between your computer and the destination computer. This trace can take varying amounts of time, if it actually does a full trace at all. If you open up a cmd window and clear your DNS cache (this is what stores addresses that have already been resolved), then try to ping a domain name, the time it takes between hitting the enter key and seeing the first return ping is the time in which the DNS translation occurs. If it is longer than half a second or so, then you might have a problem. command to flush the DNS cache: ipconfig /flushdns ping a domain name: ping pcmech.com

Thanks. Much appreciated!! I have the DNS service disabled on my machine but I did ping pcmechanic.com and it did respond within a second and I averaged 66ms with a maximum of
81ms TTL=238. Are those decent numbers?

[Force Flow]

Like I said, the actual ping reply doesn't have anything to do with the DNS request.

The DNS client service should be enabled and set to automatic, or domain names won't resolve properly.

http://www.blackviper.com/WinXP/Services/DNS_Client.htm



Side note...pcmech.com and pcmechanic.com are seperate websites.