3 Replies Latest reply: Dec 3, 2012 12:24 PM by infinite vortex
dazza222 Level 1 Level 1 (0 points)

Can anyone help a real novice?

 

I've just upgraded from SL server and have to start from scratch.  I have very limited understanding of DNS.  Can anyone help me with a basic setup?

 

I have registered the following domain example.co.nz which points to my fixed IP address

 

OSX is running on a mac that is named "server" - internal IP address 192.168.0.4

 

Can someone give me the corrrect syntax for

IP forwarders - I think I've got this part sorted (entered 2 DN

hostname

machine record

etc....

 

IP forwarders - I think I've got this part sorted (entered 2 DNS servers for Xtra NZ)

After this I gather I set my airport extreme to refer all DNS lookups to the server i.e. 192.168.0.4

 

I used to be able to type server.local on my network and this would connect to my server.  This doesn't seem to be working currently so maybe I am doing something wrong.

 

Any help would be much appreciated


Mac Mini Server
  • 1. Re: DNS setup help for simple home server setup?
    infinite vortex Level 7 Level 7 (21,400 points)

    DNS is actually not that difficult once you know what you're looking at. However, Apple really don't make it simple.

     

    A typical home server DNS setup will have one Forwarder address, the IP address of your modem, plus a single primary zone master that looks something like this. [Note : I find it simplest to show you what the text representation in /var/named/ looks like rather than trying to describe something in the user interface]

     

    Clearly the server name is server.example.net within the domain example.net. The ns1 and ns2 are there so your own server can resolve itself correctly which is the requirement for Kerberos. MX (mail servers) are define for both example.net and server.example.net.

     

    Also, the loopback for 192.168.1.1 is set to server.example.net (as opposed to example.net) as it's simpler to handle Dynamic DNS from the outside by running things primarily from a sub-domain rather than the primary domain. From the outside you can define a CNAME for server.example.net that points to account.dynamicaddress.org for instance so you're accessible without a static IP address on your DSL/cable connection.

     

    root:/var/named > more db.example.net
    example.net.          10800 IN SOA      example.net. webmaster.example.net. (
    8566284857 ; serial
    3600       ; refresh (1 hour)
    900        ; retry (15 minutes)
    604800     ; expire (1 week)
    3600       ; minimum (1 hour)
    )
    10800 IN NS       ns1.example.net.
    10800 IN NS       ns2.example.net.
    10800 IN A        192.168.1.1
    10800 IN MX       0 example.net.
    10800 IN MX       10 server.example.net.
    server.example.net.   10800 IN A        192.168.1.1
    ns1.example.net.      10800 IN A        192.168.1.1
    ns2.example.net.      10800 IN A        192.168.1.1
    www.example.net.      10800 IN CNAME    server.example.net.

     

    root:/var/named > more db.1.168.192.in-addr.arpa
    1.168.192.in-addr.arpa.  10800 IN SOA      1.168.192.in-addr.arpa. admin.1.168.192.in-addr.arpa. (
    8566284857 ; serial
    86400      ; refresh (1 day)

    900        ; retry (15 minutes)

    604800     ; expire (1 week)
    345600     ; minimum (4 days)
    )
    10800 IN NS       ns1.example.net.
    10800 IN NS       ns2.example.net.
    1.1.168.192.in-addr.arpa.   10800 IN PTR      server.example.net.

  • 2. Re: DNS setup help for simple home server setup?
    dazza222 Level 1 Level 1 (0 points)

    Thanks.  This is helpful but the /var/named representation is a bit beyond me.  Is this something that I can edit directly without the GUI and therefore use your example and just substitute my own values?

  • 3. Re: DNS setup help for simple home server setup?
    infinite vortex Level 7 Level 7 (21,400 points)

    You actually could do that. What I suggest is for you though is to use it as a point of comparison to what's in your own files.

     

    One method is to manually edit it and then see how it's represented in the GUI. I suggest you do this with the DNS turned off. It's actually what I did when trying to figure out what the Mt Lion Server GUI was going on about when going from Server Admin in Snow Leopard/Lion Server