Hi John, I'm not exactly sure what your asking here, but i'll take a stab and you let me know where i can add detail or embellsih further.
DNS is a network service usually running on one or more Domain Controllers (in a windows environment). DNS maps an "IP address" to a "friendly name". for example, when you try to connect to your sql server from your local machine, and you use the name of the server instead of the IP addres. Under the covers there is a query to the DNS network service to find the IP address for a computer with that "name". There are 2 "lookups" you can perform in DNS. One is a "forward lookup" (called an "A" record), the other is a "reverse lookup" called a "PTR" record. "A" records and "PTR" records can be linked so if one changes, the other one changes too. But this is not forced, they can be independant (which can lead to some odd netowrk behaviors, but can also be needed for some configurations). IIRC a "forward lookup" takes a "name" and returns an IP address. a "reverse lookup" takes an IP address and returns a name. so...to set this up. Assume Client/Server application. You need to run the "server software" on a physical server, but don't want to have to "bake in" the name of that physical server computer. Think up a "name" that represents your server software. For Example "MyAppServer". Now you can "bake in" the "MyAppServer" into your client software, or at least use that as a default in the config file. To set this up within the DNS system.... Go to your domain controller that has the DNS service running. (this might be running on a firewall appliance instead...check with your network admin, however the principles and concepts reamin valid). Open up the "DNS Manager" tool. Start >Control Panel > Administrative Tools > DNS You need to create an "A Record" in the "forward lookup zone", WITHOUT "an associated PTR record". the record name will be "MyAppServer" and the IP address will be the IP of the physical server where your "server software" is installed. This way anytime a computer on the network requests "MyAppServer", they will be directed to the appropriate IP address as referenced in the DNS record you just created. This allows you to move the "server software" to a different physical machine, and you can redirect all "clients" by editing the DNS record to point to the new IP address. Saves a reconfigure at end user desktops...and lots of legwork. -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] Behalf Of John Warner Sent: Friday, May 23, 2008 8:28 AM To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: Re: [ADVANCED-DOTNET] Network Search Importance: Low Phil have you got a link to how you would implement that don't worry about the PHServer stuff, just normal IP? Thanks John Warner > -----Original Message----- > From: Discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of Phil Sayers > Sent: Friday, May 23, 2008 8:23 AM > To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM > Subject: Re: [ADVANCED-DOTNET] Network Search > > > If you can guaruntee DNS will be running on your software's > destination network, you could create a "host" A-record in > DNS (ex: PHSERVER, and client software can use that, or be > configured on what hostname to attempt to connect with. > > It a bit of hack, and adds an additional > dependency/requirement (DNS) to your product, but it is a > possible solution. > > -----Original Message----- > From: Discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] Behalf Of Peter Osucha > Sent: Friday, May 23, 2008 7:57 AM > To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM > Subject: Re: [ADVANCED-DOTNET] Network Search > > > Thanks Peter (and others who've responded). This gives me > some good info to work with. > > Peter > > -----Original Message----- > From: Discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of > Peter Ritchie > Sent: Thursday, May 22, 2008 2:53 PM > To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM > Subject: Re: [ADVANCED-DOTNET] Network Search > > Yes, if PHost isn't running or isn't listening continuously, > the you'll have to pick an arbitrary length of time to listen. > > You might want to have a look at the DHCP protocol [1]. > Parts of it's protocol sound much the same as you've described. > > [1] http://support.microsoft.com/kb/169289 > > On Thu, 22 May 2008 14:28:52 -0400, Peter Osucha > <[EMAIL PROTECTED]> wrote: > > >Then I guess I need to choose some length of time to 'listen' for > >replies? PHost should send a specific reply to the originating node > >providing, for example, the name of its machine? > > > >Peter > > =================================== > This list is hosted by DevelopMentor. http://www.develop.com > > View archives and manage your subscription(s) at > http://discuss.develop.com > > =================================== > This list is hosted by DevelopMentorR http://www.develop.com > > View archives and manage your subscription(s) at > http://discuss.develop.com > =================================== This list is hosted by DevelopMentor. http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
