Network Load Balancing adds cluster IP to DNS

Is there any way to avoid automatically adding of cluster's IP address
in DNS?

I have SERVER1 with IP 192.168.0.1 and SERVER2 with IP 192.168.0.2
NLB Cluster listens for port 80 in 192.168.0.10 (both servers are in the
cluster)

When I setup NLB, it adds 192.168.0.10 to DNS so, if someone pings
server1, it's possible that 192.168.0.10 will respond, and I don't want
that! I mean: when I someone use the "server1" host name I only want
that name to be resolved to 192.168.0.1.

Thanks a lot,
Gaspar

Would that not defeat the purpose of having them clustered? I though the
whole point of clustering was that the request went to the cluster address
and the clustering software decided which server handled it.

"Gaspar" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Is there any way to avoid automatically adding of cluster's IP address in
> DNS?
>
> I have SERVER1 with IP 192.168.0.1 and SERVER2 with IP 192.168.0.2
> NLB Cluster listens for port 80 in 192.168.0.10 (both servers are in the
> cluster)
>
> When I setup NLB, it adds 192.168.0.10 to DNS so, if someone pings
> server1, it's possible that 192.168.0.10 will respond, and I don't want
> that! I mean: when I someone use the "server1" host name I only want that
> name to be resolved to 192.168.0.1.
>
> Thanks a lot,
> Gaspar

Nope... the cluster is just for ONE PORT (80), all the other networking
services should behave as usual.

Also, I'm using a special host name for the cluster (eg:
mycluster.mydomain.com).

Thanks!

Bill Grant wrote:
> Would that not defeat the purpose of having them clustered? I though the
> whole point of clustering was that the request went to the cluster address
> and the clustering software decided which server handled it.
>
> "Gaspar" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Is there any way to avoid automatically adding of cluster's IP address in
>> DNS?
>>
>> I have SERVER1 with IP 192.168.0.1 and SERVER2 with IP 192.168.0.2
>> NLB Cluster listens for port 80 in 192.168.0.10 (both servers are in the
>> cluster)
>>
>> When I setup NLB, it adds 192.168.0.10 to DNS so, if someone pings
>> server1, it's possible that 192.168.0.10 will respond, and I don't want
>> that! I mean: when I someone use the "server1" host name I only want that
>> name to be resolved to 192.168.0.1.
>>
>> Thanks a lot,
>> Gaspar
>
>

Are you SURE it's picking up .10 when you ping server1? Are you sure
it's showing up in your DNS table?

grep

Gaspar wrote:
> Nope... the cluster is just for ONE PORT (80), all the other networking
> services should behave as usual.
>
> Also, I'm using a special host name for the cluster (eg:
> mycluster.mydomain.com).
>
> Thanks!
>
> Bill Grant wrote:
>
>> Would that not defeat the purpose of having them clustered? I
>> though the whole point of clustering was that the request went to the
>> cluster address and the clustering software decided which server
>> handled it.
>>
>> "Gaspar" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>
>>> Is there any way to avoid automatically adding of cluster's IP
>>> address in DNS?
>>>
>>> I have SERVER1 with IP 192.168.0.1 and SERVER2 with IP 192.168.0.2
>>> NLB Cluster listens for port 80 in 192.168.0.10 (both servers are in
>>> the cluster)
>>>
>>> When I setup NLB, it adds 192.168.0.10 to DNS so, if someone pings
>>> server1, it's possible that 192.168.0.10 will respond, and I don't
>>> want that! I mean: when I someone use the "server1" host name I only
>>> want that name to be resolved to 192.168.0.1.
>>>
>>> Thanks a lot,
>>> Gaspar
>>
>>
>>