AFP548 Changing the world one server at a time.

binding to specific interfaces rather than 0.0.0.0

Home › Forums › OS X Server and Client Discussion › Open Directory › binding to specific interfaces rather than 0.0.0.0

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • June 23, 2011 at 9:24 pm #380855
    macpup
    Participant

    Hi

    I have a Kerberos issue with a server which basically boils down to it having multiple IP’s, this is intentional so that services can have their own DNS names e.g. ldap.nowhere.com, afp.nowhere.com etc….

    Can anyone explain how I may bind an existing Open Directory config to specific interfaces rather than the default 0.0.0.0

    I’m open to suggestions if this sounds a bit ginger beer.

    cheers macpup

    July 1, 2011 at 11:14 am #380888
    macpup
    Participant

    matters have improved somewhat by removing the irrelevant interfaces from /Config/ldapreplicas, leaving just 192.168.1.253(ldap.nowhere.com)

    but I still have Open Directory binding to the primary interface 192.168.1.254(pri.nowhere.com) rather than the preferred ldap.nowhere.com

    $ ldapsearch -LLL -x -h ldap.nowhere.com -b “” -s base “(objectclass=*)” dnsHostName krbName
    dn:
    dNSHostName: pri.nowhere.com
    krbName: ldap/pri.nowhere.com@LDAP.NOWHERE.COM

    changip is inappropriate in this case as it renames just about everything on the server rather than only dNSHostName & krbName, is there a way to safely edit these records?

  • Author
    Posts
Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.