SQL Server Performance

Heartbeat comm has Loopback DNS Address

Discussion in 'SQL Server Clustering' started by mblake99, Mar 23, 2004.

  1. mblake99 New Member

    I noticed that the Heartbeat comm on SQLClusterB has a loopback address in the DNS location. is this supposed correct? I am not sure why one server would have it and one wouldn't but this doesn't seem correct. This server is the Active directory server also.
    Any ideas would be greeatly appreciated.
  2. satya Moderator

    Use the PING utility from the command prompt to check each network adapter for connectivity with the loopback address (127.0.0.1), the card's own IP address, and the IP address of another system.

    Because is important that the heartbeat packets be sent and received in a timely manner, only PCI-based network adapters should be used, because the PCI bus has the highest priority.


    Satya SKJ
    Moderator
    http://www.SQL-Server-Performance.Com/forum
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
  3. Argyle New Member

    It can be ignored if you host DNS on the servers as well (Which you sometimes do on an AD). Then 127.0.0.1 will be added as an entry here. You don't need an entry at all for DNS though on the heartbeat NIC.
  4. mblake99 New Member

    You are right Argyle, the system is hosting the DNS and AD which helps explain why the loopback is there. Thank you both for your information.

Share This Page