Announcement

Collapse
No announcement yet.

DNS issues with clustering

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • DNS issues with clustering

    im having some issues and need someone to see where I am going wrong here.

    I have a DC and 2 Nodes (as clusters).

    Everytime I create a new service/application to cluster, I get this warning for an application that has a CAP (Client Access Point) created:

    Cluster network name resource 'WCFServiceApp' failed to update the DNS record for name 'WCFServiceApp.test.me.com' over adapter 'Local Area Connection'. The error code was 'DNS bad key. (9017)'. Ensure that a DNS server is accessible from this cluster node and contact your DNS server administrator to verify the cluster identity can update the DNS record 'WCFServiceApp.test.me.com'.
    All the machines can ping to each other.
    the DNC and DHCP are on the DC but all of the machines have static IP Addresses.

    DC
    LAN connection
    IP Address: 192.168.1.2
    Subnet: 255.255.255.0
    DNS: 127.0.0.1


    Cluster Node 1
    LAN connection
    Auto configured (I think its VMWare that does this for the public network)

    LAN connection 2
    IP Address: 192.168.1.3
    Subnet: 255.255.255.0
    Default Gateway: 192.168.106.1
    DNS: 192.168.1.2



    Cluster Node 2
    LAN connection
    Auto configured (I think its VMWare that does this for the public network)

    LAN connection 2
    IP Address: 192.168.1.4
    Subnet: 255.255.255.0
    Default Gateway: 192.168.106.1
    DNS: 192.168.1.2


    any ideas whats going on and how to fix it?

  • #2
    Re: DNS issues with clustering

    First off try changing the DNS IP to the actual IP address of the server.

    I personally feel it is bad practice to use that over the real IP address.

    http://technet.microsoft.com/en-us/l...62(WS.10).aspx

    Try running the Best Practices Analyser on the server and see what that comes up with.

    http://technet.microsoft.com/en-us/l...(v=ws.10).aspx

    Comment


    • #3
      Re: DNS issues with clustering

      Thanks.
      When you say try changing the DNS IP to the actual IP Address of the server - for which LAN and to which server? LAN (public)?

      Comment


      • #4
        Re: DNS issues with clustering

        On your DC. Change the IP of the DNS server on that to the 192.168.1.2, which i'm presuming has DNS installed on it.

        Comment


        • #5
          Re: DNS issues with clustering

          What's the FQDN of your AD Domain? Is it Test.me.com?

          Comment


          • #6
            Re: DNS issues with clustering

            yes that is correct

            Comment

            Working...
            X