Re: Network Load Balancing adds cluster IP to DNS

Tech-Archive recommends: Fix windows errors by optimizing your registry

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" <gaspar@xxxxxxxxxxxx> wrote in message news:OY2433RfHHA.3508@xxxxxxxxxxxxxxxxxxxxxxx

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



.

Relevant Pages

  • Re: Cannot Add Second Node to Cluster: Multiple DNS records were found for "MyServer.MyNet.local"
    ... So now I think I only have one problem: the multiple DNS thing ... (not withstanding, the nightmare configuration). ... You should never cluster domain controllers. ... Server1 failed to register its IP info on the DNS in ...
    (microsoft.public.windows.server.clustering)
  • Why does NLB add these DNS entries?
    ... AD DNS for "SERVER1" to this effect. ... Cluster IP address is 172.16.3.8. ... "MYCLUSTER" to this effect. ...
    (microsoft.public.windows.server.clustering)
  • ACE/STEVE
    ... frssysvol ... DC Server1 is advertising itself as a DC and has DNS ... Failed cannot test for Host SPN ...
    (microsoft.public.win2000.dns)
  • Unable to failover when public network cables are removed
    ... The cluster was setup using the standard guide from Microsoft. ... We are testing the failover by removing the server1 network connection on ... We also noticed that when the 2 public network cables were pulled out, ...
    (microsoft.public.windows.server.clustering)
  • Disabling DNS Registration of 2nd NIC?
    ... Our PDC and primay DNS is a Windows 2003 server. ... NICs - 1 for our internal network, and the 2nd for a different, ... PDC Machine name: Server1 ...
    (microsoft.public.windows.server.dns)