DNS resolution unreliable

Question

5.00/5 (2 votes)

See more:

I'm using GetHostEntry on tons of threads. The problem is that sometimes the DNS must get bogged down by requests and not respond to it. GetHostEntry doesn't tell you whether the DNS failed to respond or just didn't have an entry. How do I make this more reliable? I'm looking for 100% reliability. Any help?

Posted 31-May-11 6:40am

User 7379439

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Kim Togo · Answer 1 · 2011-06-05T00:36:00

Solution 1

I think you have to change timeout cache on one or more DNS servers that you are using. This way, the DNS server you are asking does not have to forward the query to the next and then the next and next DNS server, all the way up to the root server.

Posted 5-Jun-11 0:36am

Kim Togo