Archived from groups: microsoft.public.win2000.dns (
More info?)
In news:10e8c12fv2gme9d@corp.supernews.com,
John Coutts in <administrator@spam.yellowhead.com> posted their thoughts,
then I offered mine
> In article <engd#txXEHA.2812@TK2MSFTNGP11.phx.gbl>,
> PleaseSubstituteMyActualFirstName&LastNameHere@hotmail.com says...
>>
>>
>> I tried it but I got an "Error 10014 Encountered when sending data".
>> --
>> Regards,
>> Ace
> ***************** REPLY SEPARATER *****************
> Error 10014 is a general Winsock error that can occur for a number of
> different reasons, but most often because of a bad socket address.
> The program uses the Microsoft Winsock Control 6.0. The remote port
> is bound to port 53 UDP, and the local port uses the first available
> port on the first interface that supports TCP/IP (I have not tested
> the program on machines with more than 1 supporting interface). The
> program attempts to discover the first default DNS server available
> on your machine, and by default uses it as the remote host. You may
> actually use any DNS server listed (or add your own) in either
> recursive or non-recursive mode.
>
> To narrow down the problem a bit, could you please supply a little
> more information? Does the error occur when the program is loaded, or
> does it occur when you attempt to send a query? Does it properly
> discover your default DNS, which should appear in the DNS Server box?
>
> If you don't care where the answer comes from, use it in the
> recursive mode (default). But if want the answer directly from an
> authoratative server, use it in the non-recursive mode. Click the
> "Root Servers" button and then choose one of the Root Servers. When
> you query the root server, it will supply the GTLD (or whatever)
> servers. Choosing one of these and re-applying the query will
> generally provide the authoratative servers, but you may have to dig
> deeper. Choosing one of these and re-applying the query will provide
> the authoratative answer. By default, it looks for the "A" record,
> but once the authoratative server is found, you can change the record
> type (say to MX) and requery.
>
> You may contact me directly if you so desire.
>
> J.A. Coutts
> Systems Engineer
> MantaNet/TravPro
> <administrator@yellowhead.com>
ClientDNS picks up my two DNS servers separated by a comma:
4.2.2.2,68.80.0.6
So the way I see that ClientDNS works, it selects the two DNS servers that
my machine is configured with, but they show up in the list as I showed you
above with a comma separating them with NO spaces between the two. Kind of
didn't make sense why it would do that, so I thought maybe its supposed to
do that.
So assuming its using one of them (so I thought it would do, or assume it
should do), then I entered microsoft.com and hit "Send Query", and that is
when I received the error.
So following your suggestion to use a Root, that gave me a response. Hmm...
Taking it a step further, I tried another step by adding 4.2.2.2
individually (instead of the way the app "found" my two servers and
separated them with a comma) and tried the same query and it worked. I tried
it again adding the other DNS individually, selected that, hit Send Query,
and it worked as well..
But when I tried to choose what ClientDNS found originally, the two
separated by a comma, it did NOT work. Is this a bug?
--
Regards,
Ace
Please direct all replies ONLY to the Microsoft public newsgroup so all
can benefit. This posting is provided "AS-IS" with no warranties and
confers no rights.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================