[reSIProcate] Windows Name Resolution in reSIP

[Scott Godin]

Thanks Cullen.

Using this stuff would mean linking in and requiring the .NET framework 1.1.
I'm no expert on the .NET framework - I'm not sure if there are issues with
Managed vs Unmanaged code and compatibility with older OSs.  We may be able
to build it in as a compile flag alternative to ares, as you suggested.

Scott

-----Original Message-----
From: Cullen Jennings [mailto:fluffy at cisco.com] 
Sent: Tuesday, November 16, 2004 11:07 AM
To: Scott Godin; resiprocate-devel at list.sipfoundry.org
Subject: Re: [reSIProcate] Windows Name Resolution in reSIP

On 11/13/04 11:33 AM, "Scott Godin" <slgodin at icescape.com> wrote:


> Does anyone know if .NET has async DNS?  I've looked around, but I can't
> seem to find any reference to it.  There is an asynchronous version of the
> GetHostByName API - but the MSDN article says that the application should
> not expect that the name will be resolved in parallel with other requests
-
> so I don't think this is ideal - also this function has been deprecated
> since it does not support IP V6.
> 

Look in the Dns class in the System.Net package. It has BeginResolve and
EndResolve.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/
frlrfSystemNetDnsMethodsTopic.asp