11 Replies Latest reply: Aug 27, 2012 10:51 PM by William Kucharski
Remy S. Level 1 Level 1 (0 points)

Setting up a primary dns zone in server.app results in a faulty SOA record:

 

file /var/named/db.example.com reads:

 

example.com.                              10800 IN SOA      example.com. admin.example.com. (

                                                        2012082105 ; serial

                                                        3600       ; refresh (1 hour)

                                                        900        ; retry (15 minutes)

                                                        1209600    ; expire (2 weeks)

                                                        86400      ; minimum (1 day)

                                                        )

                                      10800 IN NS       ns2.some.org.

                                      10800 IN NS       ns3.some.org.

 

imo, the "primary nameserver" field of the record is wrong; shouldn't it read "my-macmini.mydomain.com.", if this is the name of my server?

Due to this error, it is not possible to update the zone via nsupdate.

Any ideas, work arounds?

 

Ciao

Remy


OS X Server
  • 1. Re: Wrong DNS SOA record in serverapp
    William Kucharski Level 6 Level 6 (14,695 points)

    Try asking your question over in the OS X Server forum, but according to RFC 1033, the nameserver field should reflect the FQDN of the nameserver the record came from.

  • 2. Re: Wrong DNS SOA record in serverapp
    Barney-15E Level 8 Level 8 (35,275 points)

    As with William, I don't know anything about it for sure, but the default apache server has the same entries. You must change them to your FQDN in the Config files.

    Given that the file is db.example.com, I would imagine you must create a config for your server. Not having the Server, I can only guess. The Server forums would likely be the best place to ask.

  • 3. Re: Wrong DNS SOA record in serverapp
    Remy S. Level 1 Level 1 (0 points)

    William,

    Looks like you agree with me: When I create the primary zone on my mac server (with hostname my-macmini.mydomain.com) then this is definitely "the nameserver the record came from" and should be recorded as such by server.app.

    Looks like Apple needs fixing this?

  • 4. Re: Wrong DNS SOA record in serverapp
    gracoat Level 3 Level 3 (660 points)

    What does terminal report if you run sudo changeip -checkhostname

  • 5. Re: Wrong DNS SOA record in serverapp
    William Kucharski Level 6 Level 6 (14,695 points)

    It depends on what you mean by "create."

     

    If the SOA entry looks like this after using some OS X Server configuration tool to generate DNS records, then yes, it's a bug.

     

    If you are supposed to edit the file yourself, then you must replace the "example.com" placeholder text with the FQDN of your internet-facing nameserver.

  • 6. Re: Wrong DNS SOA record in serverapp
    Remy S. Level 1 Level 1 (0 points)

    When I say "create", I actually mean something along the line:

     

    1) open server.app

    2) click on "DNS" to access the dns settings of the server

    3) click on "+" icon and select "new primary zone"

     

    After this, we have "created" a new primary zone on this server. Hence the primary master of the zone should be set to this server....

    I am now convinced it is a bug. Looking forward to see this fixed...

  • 7. Re: Wrong DNS SOA record in serverapp
    William Kucharski Level 6 Level 6 (14,695 points)

    Have you filled in the appropriate fields first?

     

    /___sbsstatic___/migration-images/migration-img-not-avail.png

  • 8. Re: Wrong DNS SOA record in serverapp
    shcaerp Level 1 Level 1 (55 points)

    Don't know what you guys are trying to accomplish, but DNS works great on Mountain Lion Server!

     

    First of all the primary zone name is the top level domain - example.com - nothing more.  Mountain Lion adds the host to the name at setup if there is not a proper upstream dns to query.  Then you create a machine record and enter the host name - mymac - and an IP address.  Next you add a nameserver record and possibly an mx record.  The reverse should be setup automatically.  Then delete the primary zone mymac.example.com and it's reverse or you will have issues.

     

    Now, there are a thousand caveats to dns but since you obfuscated your domain records, it would be difficult to help you further.

  • 9. Re: Wrong DNS SOA record in serverapp
    Remy S. Level 1 Level 1 (0 points)

    William,

    In 10.8 Server app there is no way to set the "primary name server"; Looks like this has been "simplified away"

    Serverapp-Dns-PrimaryZone.png

  • 10. Re: Wrong DNS SOA record in serverapp
    Mark23 Level 3 Level 3 (975 points)

    William is working on a pre-ML server. William, this forum is for OS X Server, which is the newest model of, uhm... OS X Server. It's older brother is called Lion Server....

  • 11. Re: Wrong DNS SOA record in serverapp
    William Kucharski Level 6 Level 6 (14,695 points)

    Just grabbed a screen shot for OS X Server, which apparently is an older version - my apologies.

     

    If in the example above the "example.org" entries remain after a different name is entered in the "Name:" field, then yes, it appears it may be a bug.