> So I verified this fails any time there is a DNS configuration that
> results in nslookup returning an error regarding "Non-existent
[quoted text clipped - 5 lines]
>
> It seems this is a .Net 2.0 bug.
I don't know what the problem is, but one person wrote a comment to this
documentation page:
http://msdn2.microsoft.com/en-us/library/ms143998.aspx
...that seems to confirm the problem you're having (though in a slightly
different example, the behavior seems basically the same problem).
I wonder if you or the other person has reported this problem as a bug
yet. I haven't run into it myself, but if you have a reproducible
example, you should probably report it so that it can be fixed.
Pete
Joe K - 04 Apr 2007 22:55 GMT
Yes, I think I have a reproducible case but it requires a specific DNS
setup. The link you pointed me to sounds exactly like my issue, but I think
the poster didn't realize there is a more specific setup required to
reproduce (e.g. I can run his test case without a problem).
I wasn't planning on reporting it as a bug due to the sheer effort to push
this through Microsoft (e.g. open a case, wait a week for callback, work
through 1st level engineer, wait for engineer to setup & reproduce, wait for
engineer to talk with development, wait for development to acknowledge as a
bug, etc.., etc...). Okay, okay, I am a bit jaded by my last two
experiences in which after all that effort, the product failures we actually
deemed documentation bugs!
If anyone has more details, I'd be interested. In the meantime, I will be
making a critical hotfix to our application that uses the deprecated method
instead of GetHostEntry.
Thanks for reply.
Joe