So BEFORE YOU EVEN THINK about starting a LION/SNOW SERVER..here is what you MUST do. (of course it's not part of ANY Basic Setup instructions on SNOW hard manual that comes with the Mac mini server..or LION server instruction pages......or neither in the Lion Server Manual that you get when you download it.
AND THIS - People - SHOULD BE IN BIG RED LETTERS on any document or instruction for SERVER SETUPS as THE FIRST STEP in SETTING UP MAC SNOW OR LION SERVER
1. HAVE A DOMAIN REGISTERED somewhere on the internet.
2. SET UP ALL DNS SERVICES and CONFIGs FOR THE DOMAIN BEFORE YOU EVEN THINK about doing anything else.
Before going to STEP 3....see step 1 and 2 again and double check you did it right.
3. Everything else with what you need the server to do.
Ok..so already I've gone over the Lynda.com setting up primary DNS zone video. Very descriptive and very helpful..
BUT ...still one problem after the other.
EVEN after setting up the primary dns server and adding CName and Machine record...guess what.
This Service has Encountered and Error.
Try to refresh the view (server.mcpserver.com/DNS). (kReceivedUnknownError)
God...someone shoot me now!
It's taken OVER two weeks after installing the LION server just to get a couple of network users to be able to login to your own local network mobile accounts.
****. Someone find a gun or let me borrow their car and garage!
And when you open the Server Admin app to alter DNS configs... does that mean that the SERVER is running or is it technically running when the Server App is? Do you have to have them BOTH open at the same time to not get these errors in saving?
This is all very confusing.
I think these questions and more will be answered on the next episode of...
S O A P !
Kimbakat, I read through this thread a few times to get a better grasp on your issue, but it seems that you are still a bit confused as to how to set up your DNS server properly, and why a properly working local DNS will help you in solving your problem. You mention earlier in the thread that you want your mobile accounts to work on your local network, nothing external, but then proceed to sign up for a domain on the internet. Why? What lead you to believe this was necessary?
Also, you say that none of the server manuals mention signing up for an internet domain. This is because it simply isn't required for a basic server setup. It all depends on what you want to use the server for. Further, you gave advice on the forum that likely is unecessary for many people, by leading them to believe they NEED an internet domain for mobile accounts. If they didn't know any better, this advice can lead people to wasting their money, purchasing something that probably isn't required.
And just for reference, I currently have mobile accounts running on my local network, with NO registered internet domain. Further, my server does not have DNS running, because the DNS service is provided by my internet gateway, and not any other computer on the network. Chances are, on a small business or home network, your gateway is already running DNS for you. Have you looked into this?
We have no problem helping you out with the issue, but you would do yourself a big favor by spending some time researching basic network fundamentals and planning out what you want to accomplish and what tools you will need to reach your goals. I know it doesn't sound fun, but it saves alot of headaches. On top of Jonathan's advice on checking out lynda.com, wegotserved.com has a nice tutorial on setting up OS X Lion Server on a home network, covering a wide range of topics. Also, it may be helpful to find your local friendly computer nerd (every family or company has one), and ask him/her to assist.
Yeah...sorry for the drama..but my drama is not really drama but more of my humor vented from frustration. You have to admit it's pretty godamn funny when you read the despair with drama.....but after following strict instructions on Lynda on how to set up DNS..the DNS had an error while saving and the pane would not reload.
The error read:
"The service has encountered an error. Try refresh the view (server.local/DNS). (kRecievedUnknownError)."
This article fixed it...from thread https://discussions.apple.com/thread/3303859 . I just went to the var folder without terminal....and I got the DNS pane back.
But still don't have my users/directory back.
I experienced exactly the same problem in Lion server (10.7.2, but also in 10.7.3).
For me it solved the problem by renaming some files in /var/named/.
open a shell
- stop DNS service (> sudo serveradmin stop dns) (you can stop DNS service in Server Admin too)
- change directory to /var/named (> cd /var/named)
- rename all "db.*" files to "db.*.backup" (> sudo mv db.xxxx.xxxx db.xxxx.xxxx.backup)
- rebuild your DNS settings in Server Admin
- start DNS service (> sudo serveradmin start dns) (you can start DNS service in Server Admin too)
NOW the next question I need cleared up before I move any further is. Is ADMIN TOOLS unstable with LION SERVER. I've read some problems with this that other people having the same problem I did....So is working with DNS setting in ADMIN TOOLS going to mess up my LION SERVER dns again. Admin Tools seem really unstable in conjunction with LION SERVER as mentioned in other forums..and as I just experienced all day yesterday!
Any comments on this?
After upgrade to Mountain Lion on clients and Mountain Lion + OSX server on my server manually syncing to the server failed with the "home at "(null)" does not allow writing" error.
Here is what worked for me.
1. Noticed that under the File Sharing settings of the Server app that "Share home directories with AFP" was not checked for the /Users directory. I checked this. This caused a double entry in the Home directory entry when viewed from the Workspace app. I ignored this.
2. My DNS entries had myserver.local and server.myserver.com. I removed the myserver.local entry and syncing started working.
Hi, J.W. Martin. I had the same problem on OSX 10.7 server as kimbakat and there (to my knowledge) seemed to be two ways to solve it. 1) Run the built in DNS server of OSX server. Or 2) point the home folder reference of the mobile accounts to the servers 'static IP-address' instead of server's xxxx.local name.
You write your internet gateway is running the DNS service? Could you elaborate on that? As far as I know my Airport Extreme could only a) forward to the ISP's DNS servers (by default), in which case mobile accounts could not synchronise. (the so-called green dot in the client's system preferences would turn on for some reason) or b) forward to OSX servers DNS server, after setting it up.
If there is a c) "run the DNS server on the interent gateway" I would be highly interested in that. Especially if it is possible with the Airport Extreme.