Home / server / Questions / 105271
In Process
Paul Nathan
Asked: 2010-01-22 19:48:59 +0800 CST

DNS on OS X 10.6 non-server

  • 772

I would like to have my OSX 10.6 (non-server) Mac serve domain names out to my small network(on the order of 5-10 computers).

There's a few things I need to know to do this:

  1. Use the supplied named software or find another one(with possibly a GUI and shell to simplify it). The disadvantage of named is that it's fairly complex. I'm comfortable dinking around in Linux, but OSX has some unique configuration aspects that can bite one in the butt.

  2. The Friendly Manual for domain name configurations (the FM part of RTFM).

  3. How I avoid trying to propagate myself out to the internet, when I simply want to do a local network configuration.

domain-name-system mac-osx osx-snow-leopard

3 Answers

  1. If you are fairly good with Linux, use MacPorts and use BIND9 and Webmin. This way you will get a clean, package managed BIND that is not messed around by Apple's update. BTW, Yes this assumes that you will read an manual or two on how to use BIND & DNS.

    It can be complicated mainly because DNS can become complicated if you make it out to be. If you want Apple simplicity, get MacOS X Server 10.6 and use their Standard mode and life will be easier; you still need to understand DNS...

    • 2

  2. Trust me, if you don't want to read books about DNS, I wouldn't get mixed up with OS X server, as DNS is pivotal to all of its services, and she gets way freaky if you don't know what you're doing and mess up DNS somehow. It has a nice BIND interface, but it's still NOT stupid-simple.

    By just setting the hostname on each computer, chances are you can just refer to each machine by hostname.local to resolve any services, no?

    You can also install Bonjour, aka mDNS/Avahi/ZeroCONF for no-stress local name resolution.

    If you want to be able to simply resolve some weird local domain hosts within your LAN, it's probably easier to just use the hosts file on each machine with an identical set of local addresses to resolve to... for example, machine/host annie on on your local domain wackylocaldomain with IP 10.0.1.4 you could...

    `localadmin@annie:~:sudo nano /etc/hosts

    127.0.0.1           annie.wackylocaldomain            annie          localhost
255.255.255.255     broadcasthost 
::1                 localhost
fe80::1%lo0         localhost
10.0.1.1            sandy.wackylocaldomain            sandy
10.0.1.2            daddy.warbucks.wackylocaldomain   daddy.warbucks
10.0.1.3            easierthandns.wackylocaldomain    easierthandns

    `

    and so forth...

    • 1

  3. Regarding point 3 - you won't have to "avoid" anything, propagation is not going to happen unless you explicitly set up NS records pointing to your name server (assuming it's even accessible from the Internet - and given that it's local - it shouldn't be).

    • 0