OS X Server DNS service

Discussion in 'Mac OS X Server, Xserve, and Networking' started by soinro, Jan 13, 2011.

  1. soinro, Jan 13, 2011
    Last edited: Jan 13, 2011

    soinro macrumors newbie

    Jan 13, 2011
    Hello all,

    I have a Mac Mini (1.83GHz, 1.5 RAM) with a fresh install of OS X Snow Leopard Server and I want to use it for DNS and web hosting.

    What I have done so far is to go to the domain registrar and configure a new nameserver (ns.domain.tld) to point to my static IP. This Mac Mini is behind a DI-524 router and I have forwarded ports 53 and 80 to the Mini.

    I have also added the domain name to the DNS configuration pannel (as in the attachment), but intodns.com gives the following error (among others, and obviously the site is not working): "Mismatched NS records WARNING: One or more of your nameservers did not return any of your NS records."

    I don't know where to go from here ..

    Thank you to anyone willing to take the time to give me a hint!

    Best regards!

    Attached Files:

  2. sim667 macrumors 65816

    Dec 7, 2010
    That sounds more like a problem with the DNS service rather than your setup, i could be wrong, hopefully someone with a more specific knowledge will help you shortly.
  3. talmy macrumors 601


    Oct 26, 2009
    I'm no expert, but this seems all wrong to me. You are running a DNS on your LAN. You can see from the configuration that it is only concerned with your LAN addresses (192.168...) so it is only by your local systems. You should be port forwarding only 80 to your server for web hosting.
  4. sim667 macrumors 65816

    Dec 7, 2010
    You need to use the dns to redirect to your routers public ip address then port forward the correct protocols to the local address of your server on your network.

    However if your server attains its ip from the router via DHCP then you may want to assign the server a static IP address to stop the port forwards borking.

    Also if you have a dynamic ip address from your ISP then you want to look at ways you can automatically update your DNS with an IP when the lease runs out.
  5. Danuska macrumors newbie

    Jan 22, 2011
  6. jg900ss macrumors newbie


    Nov 28, 2009
    Europe, and Florida
    Some ideas....

    I have a Mini with Server, at home, behind router(s). I signed up for DynDNS to get the location of my server tied to the dynamic IP I get from the phone company (lease is only guaranteed for 24 hours). I open ports on the routers to shove traffic to the server, and as long as the server is up, and announces itself to DynDNS through the DynDNS updater software that runs on bootup, its visible externally. I had MacWorks consultant help me get that and more running and it works fine. In fact, we got a directory sync'ed between similar servers on the web so it is clear the servers can find each other even when one has the temp address from the phone company. I believe the key is the port forwarding and doing it correctly on the router of choice, and using DynDNS, or something similar, for the "pinging".
  7. sim667 macrumors 65816

    Dec 7, 2010
    This is what i do to share my AFP fileshares across the web to friends houses, except instead of the DNS updater being an application on my mac, its on my router instead. I use dnydns too.
  8. Winni macrumors 68030


    Oct 15, 2008

    Just a few quick points:

    1. Does your ISP even allow you to forward DNS requests to your local DNS server? If not, then public DNS requests will never be forwarded to your private DNS server. I doubt that your ISP delegates the DNS authority to your local machine - only few ISPs would, and if so, they charge good money for that.

    2. You CANNOT use private IP addresses on the Internet. The ranges 10.x.x.x/8, 172.16.x..x-172.31.x.x/16 and 192.168.x.x/24 are DROPPED by every ISP and never routed. (That's why they are private.) In other words, if you want the Internet to be able to resolve your host names and actually reach the hosts, you must use public IP addresses. (In your case, the one assigned to your Internet router.) Do you even have a STATIC public IP address? If not, DynDNS might become your best friend.

    3. DNS requires UDP AND TCP. Make sure that both UDP and TCP port 53 are open and properly forwarded.

    4. I don't know how Apple's implementation of BIND/their DNS server works, but BIND in Linux, for example, requires entries in this notation:

    In the Forward lookup zone:

    machine IN A

    In the Reverse lookup zone:

    242 PTR machine.domain.com. (The dot "." behind the FQDN is important and MUST be there.)

    The important part here is that BIND requires the full host and domain name and the full network address, not just host names like "www.". But as I've said, I've never used OS X Server and don't know how its DNS GUI works and if they've dumbed the thing down in the name of user friendliness.

Share This Page