Mac OS X 10.5 Server: Preventing DDNS registration for multiple interfaces


 
Thread Tools Search this Thread
Operating Systems OS X (Apple) OS X Support RSS Mac OS X 10.5 Server: Preventing DDNS registration for multiple interfaces
# 1  
Old 10-08-2008
Mac OS X 10.5 Server: Preventing DDNS registration for multiple interfaces

When connecting Mac OS X Server version 10.5 to networks that implement dynamic DNS (DDNS), including Microsoft Active Directory networks, Mac OS X Server may register each configured network interface address in DNS. For multi-homed servers, this may cause confusion and prevent clients from connecting to the server.

More from Apple OS X Support ...
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. IP Networking

MAC Address - Four Interfaces with the same MAC Address

four interfaces with ifconfig all interfaces have the same mac. If is not set for unique. but it still works. what difference does it make to have all macs the same or different? (4 Replies)
Discussion started by: rrodgers
4 Replies

2. AIX

Problem with multiple network interfaces

Hi .. we have two AIX 5.3 systems with a small client server app communicating over a TCP socket. Box A has a single network interface where the server app (in Java) opens a well known port and waits for connections from Box B. Box B has two network interfaces, X and Y. Interface X has the... (4 Replies)
Discussion started by: RonBowater
4 Replies

3. Shell Programming and Scripting

No lock file: Preventing multiple instance of a script

I've been bitten by using a lock or pid file to prevent multiple instances of a script. A user typed kill -9, and the pid file didn't go away. You can't trap -9. So when he tried to restart, it said "already running", and I got trouble report. Argh. So here's what we came up with: # Stop if... (1 Reply)
Discussion started by: McFadden586
1 Replies

4. Programming

Client/Server Socket Application - Preventing Client from quitting on server crash

Problem - Linux Client/Server Socket Application: Preventing Client from quitting on server crash Hi, I am writing a Linux socket Server and Client using TCP protocol on Ubuntu 9.04 x64. I am having problem trying to implement a scenario where the client should keep running even when the... (2 Replies)
Discussion started by: varun.nagpaal
2 Replies

5. AIX

Multiple LAN Interfaces

Is there a way to add routes using the add route command in AIX to add different routes and bind them to different NICS installed in the box? (2 Replies)
Discussion started by: Docboyeee
2 Replies

6. IP Networking

DHCPD, Multiple interfaces, Single Subnet

I have an OpenBSD 3.7 firewall with five network interfaces on it, one of which is connected to the Internet. I'd like to use the remaining four interfaces as a network switch for a single internal subnet. The main problem I have is that the DHCP daemon doesn't like multiple interfaces matching... (0 Replies)
Discussion started by: vertigo23
0 Replies

7. UNIX for Dummies Questions & Answers

multiple interfaces with apache?

I'm having some problems here, and was wondering whether it was an Apache problem. We have two firewalls where I'm at, Apache is installed on the second one. The first firewall is setup to forward all outside requests to port 80 on the second firewall. Apache is only working on the lan, not the... (2 Replies)
Discussion started by: cerberusofhnsg
2 Replies

8. IP Networking

Multiple Interfaces and Routes

I have a Unix box with 2 network interfaces on the same IP subnet and would like to add a host route via a specific interface. Any assistance would be greatly appreciated. (3 Replies)
Discussion started by: diemos
3 Replies
Login or Register to Ask a Question
opendirectoryd(8)					    BSD System Manager's Manual 					 opendirectoryd(8)

NAME
opendirectoryd -- is a launchd(8) job for client access to local or remote directory systems SYNOPSIS
opendirectoryd [--version] DESCRIPTION
opendirectoryd is a launchd(8) job which replaces "DirectoryService" as a core part of the Open Directory technology. Several modules are provided that allow access to existing directory systems: o Active Directory o LDAP o Local Database o NIS Modules opendirectoryd modules have specific capabilities: Authentication password verification, password changes, etc. Connection general connections used for queries, record modifications, etc. Discovery location and prioritization of servers to contact (a.k.a., service discovery) Unspecified a generic module used for unspecified purpose (usually to extend capabilities) Third party plugins developed for "DirectoryService" are supported via dspluginhelperd(8). Open Directory Open Directory is a technology which includes a client API abstraction layer, a directory server, and the opendirectoryd daemon. This allows clients to utilize a single API to access a variety of directory servers simultaneously or configure their own directory server. Open Directory forms the foundation of how Mac OS X accesses all authoritative configuration information (users, groups, mounts, managed desktop data, etc.). This allows use of virtually any directory system via Apple and third party modules. Configuration of opendirectoryd is done via "System Preferences" under the "Users & Groups" preference pane. Advanced settings are available by using "Open Directory Utility..." within "Users & Groups" preference pane. More information is available from the Open Directory website: http://developer.apple.com/darwin/projects/opendirectory/ Open Directory Server Open Directory Server utilizes OpenLDAP which is included as part of Mac OS X Client, Mac OS X Server, and Darwin. OpenLDAP provides a robust and scalable platform for serving directory-based information for both standalone and networked systems. NFSv4 Domain name The following will set the default domain name used to map user and group identities in NFSv4 client/server operations. dscl . -create Config/NFSv4Domain RealName <Example.com> This command requires root privileges. FILES
Files are stored in various locations for opendirectoryd depending on use. A list of folders and files are shown below. System files provided by Apple and should only change with operating system updates: /System/Library/OpenDirectory/Configurations/ node configuration files /System/Library/OpenDirectory/DynamicNodeTemplates/ dynamic node definitions /System/Library/OpenDirectory/Mappings/ record/attribute mapping tables /System/Library/OpenDirectory/Modules/ modules to be loaded on demand /System/Library/OpenDirectory/Templates/ templates used for node styles (module layout and mappings) /System/Library/OpenDirectory/record-schema.plist OpenDirectory record/attribute schema /System/Library/OpenDirectory/permissions.plist OpenDirectory global record/attribute permissions User defined files: /Library/OpenDirectory/Templates/ templates used for node styles (module layout and mappings) /Library/OpenDirectory/Mappings/ record/attribute mapping tables Files that change periodically are located in: /Library/Preferences/OpenDirectory/Configurations/ node configuration files /Library/Preferences/OpenDirectory/DynamicData/ dynamic data stored by nodes /Library/Preferences/OpenDirectory/.LogDebugAtStartOnce enables debug logging until process exits or system is rebooted (reboot required) /var/log/opendirectoryd.log* log file(s) for opendirectoryd Legacy locations: /Library/DirectoryServices/PlugIns/ third party DirectoryService plugins loaded by dspluginhelperd SEE ALSO
odutil(1), dspluginhelperd(8), slapd(8) BSD
March 3, 2011 BSD