Sponsored Content
Full Discussion: Mac OS X
Top Forums UNIX for Dummies Questions & Answers Mac OS X Post 8639 by loadc on Monday 15th of October 2001 05:20:19 PM
Old 10-15-2001
Named

It looks like named, but it's said as "name-dee", it's the daemon that runs the name server. The config file you want is in /etc, if memory serves, usually /etc/named.conf. There shoudl also be a man page on that one. The database for the zone is usually in the named.hostname file in /etc. This will contaitn all of the entries for your zone that you are setting up. There are a number of quirks to BIND and named, not the least of which is incrementing the serial number each time you edit the database file to get named to re-read the SOA.
In all honesty, setting up DNS is a real task, and I'd highly recommend the O'Rielly book "DNS and BIND", available at B&N, or anywhere that has ORA books (also ora.com). It's a good read, relatively short, and a relaly good reference to DNS and BIND.

Good luck, get the book, save yourself some seriously frustrating time, and have fun with it,


loadc
 

We Also Found This Discussion For You

1. OS X (Apple)

Let's get a .mac top level domain! As in www.xyz.mac

ICANN, the Internet Corporation for Assigned Names and Numbers, is inviting proposals for new sponsored top level domains. This may be wishful thinking, but isn't that a chance to push for a .mac top level domain (TLD)? I for one would VASTLY like the idea of having a domain of something.mac --... (0 Replies)
Discussion started by: ropers
0 Replies
MAC_PREPARE(3)						   BSD Library Functions Manual 					    MAC_PREPARE(3)

NAME
mac_prepare, mac_prepare_type, mac_prepare_file_label, mac_prepare_ifnet_label, mac_prepare_process_label -- allocate appropriate storage for mac_t SYNOPSIS
#include <sys/mac.h> int mac_prepare(mac_t *mac, const char *elements); int mac_prepare_type(mac_t *mac, const char *name); int mac_prepare_file_label(mac_t *mac); int mac_prepare_ifnet_label(mac_t *mac); int mac_prepare_process_label(mac_t *mac); DESCRIPTION
The mac_prepare family of functions allocates the appropriate amount of storage and initializes *mac for use by mac_get(3). When the result- ing label is passed into the mac_get(3) functions, the kernel will attempt to fill in the label elements specified when the label was pre- pared. Elements are specified in a nul-terminated string, using commas to delimit fields. Element names may be prefixed with the '?' char- acter to indicate that a failure by the kernel to retrieve that element should not be considered fatal. The mac_prepare() function accepts a list of policy names as a parameter, and allocates the storage to fit those label elements accordingly. The remaining functions in the family make use of system defaults defined in mac.conf(5) instead of an explicit elements argument, deriving the default from the specified object type. mac_prepare_type() allocates the storage to fit an object label of the type specified by the name argument. The mac_prepare_file_label(), mac_prepare_ifnet_label(), and mac_prepare_process_label() functions are equivalent to invocations of mac_prepare_type() with arguments of "file", "ifnet", and "process" respectively. RETURN VALUES
Upon successful completion, the value 0 is returned; otherwise the value -1 is returned and the global variable errno is set to indicate the error. SEE ALSO
mac(3), mac_free(3), mac_get(3), mac_is_present(3), mac_set(3), mac(4), mac.conf(5), maclabel(7) STANDARDS
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion of the draft continues on the cross-platform POSIX.1e implementation mailing list. To join this list, see the FreeBSD POSIX.1e implementation page for more information. HISTORY
Support for Mandatory Access Control was introduced in FreeBSD 5.0 as part of the TrustedBSD Project. Support for generic object types first appeared in FreeBSD 5.2. BSD
August 22, 2003 BSD
All times are GMT -4. The time now is 06:40 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy