Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

lowload + result nslookup netcom, netcom1 = random?

0 views
Skip to first unread message

jan b. schipmolder

unread,
Mar 8, 1998, 3:00:00 AM3/8/98
to

I did several nslookups on netcom and netcom1 in a row.
Looks like I'm getting random answers from the pool ov
of available machines.
I removed netcom and netcom1 from consideration in
lowload till I understand what's going on.
Anybody have a semi-authoratative anser?
Thanks.
Jan.
--
--
Jan B. Schipmolder
sc...@netcom.com

Brett Frankenberger

unread,
Mar 8, 1998, 3:00:00 AM3/8/98
to

In article <schipEp...@netcom.com>,

jan b. schipmolder <sc...@netcom.com> wrote:
>I did several nslookups on netcom and netcom1 in a row.
>Looks like I'm getting random answers from the pool ov
>of available machines.

On what server? netcom12's named reports round-robin addresses for
netcom.com, but reports netcom1.netcom.com correctly (192.100.81.100)
no matter how many times I try.
--

- Brett (bre...@netcom.com)

------------------------------------------------------------------------------
... Coming soon to a | Brett Frankenberger
.sig near you ... a Humorous Quote ... | bre...@netcom.com

jan b. schipmolder

unread,
Mar 8, 1998, 3:00:00 AM3/8/98
to

Brett Frankenberger <bre...@netcom.com> wrote:
: In article <schipEp...@netcom.com>,

: jan b. schipmolder <sc...@netcom.com> wrote:
: >I did several nslookups on netcom and netcom1 in a row.
: >Looks like I'm getting random answers from the pool ov
: >of available machines.

: On what server? netcom12's named reports round-robin addresses for
: netcom.com, but reports netcom1.netcom.com correctly (192.100.81.100)
: no matter how many times I try.

I don't know what I did wrong.
Now I'm getting consistently the same number also.
And I tried it on all machines. I always get (192.100.81.100)
I think I'll go get some fresh air for a while before I do
anything else.

0 new messages