Currently Being ModeratedAug 21, 2012 4:44 AM (in response to Remy S.)
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.
Currently Being ModeratedAug 21, 2012 5:46 AM (in response to William Kucharski)
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?
Currently Being ModeratedAug 21, 2012 1:55 PM (in response to Remy S.)
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.
Currently Being ModeratedAug 22, 2012 7:32 AM (in response to William Kucharski)
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...
Currently Being ModeratedAug 22, 2012 6:10 PM (in response to gracoat)
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.
Currently Being ModeratedAug 27, 2012 10:51 PM (in response to Mark23)
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.