DNS issue

[stuarta99]

Hi guys,

I'm not sure if I have a DNS issue or misconfiguration but a new install of Yosemite server doesn't seem to be able to resolve itself. I've attached a screenshot if someone can please advise if it's set correctly.

There is a reverse zone which I think is incorrect because it was originally setup on 192.168.1.77 but the new IP is 192.168.5.2

Some clients have issues of being disconnected and I'm not sure if this is causing a problem. I'd be grateful if someone could advise

 

[DJLC]

Looks to me like you have two incorrect reverse lookup zones that would resolve GM-MINI-01.private to 192.168.72.74 and 192.168.1.77 respectively. You'll want to wipe out both of those and create a new one for the updated internal IP address.

 

[stuarta99]

Yep I've fixed them today I think and created from scratch from the host name option. The workstations can now resolve the server but the server not the workstations, not sure if that important. Also it seems to have broken the open directory and its showing no replica servers in the main window. Got issue where got several clients ranging from snow leopard to Yosemite are having a mixture of issues ranging from slow connection and disconnections. I just need to find a happy os and protocol to use

 

[DJLC]

Haven't used Yosemite server yet; I'm on Mavericks on the Xserve at work.

But ideally you want to have DNS golden before enabling OD. Not sure what steps you need to take to make OD happy with your corrected DNS.

Clients should be able to resolve the server; I don't think the server typically needs to be able to resolve clients. I think that's more of an Active Directory thing over in Windows land/

 

[stuarta99]

Yep that's what I'm thinking as long as clients can see server. Hoping the DNS was why there was some disconnections and hopefully that resolved and not sure if OD is vital. You using SMB or AFP and connecting via network pane in browser or connect to server? Had some issues when I forced shares to SMB, connecting via finder page didn't work see them, but once I had initially connected using connect to server using smb://nameofserver the pane then worked

 

[Zjef]

Not claiming to be an expert, but what is odd to me:

1. Looking on top of the screenshot, the DNS settings to be used by your clients are not reflecting the IP of the DNS server
2. I also noticed that you've got differences in the reverse zones

When I look at my server settings, the IP is always the same.

Recalling my installation, I've got issues when I tried to set up DNS as a "local" server. Setting up the server as "private" resulted in correct DNS setting.
To be as complete as I can be, prior to install the server app I made sure that the server's IP was correct (the setting it must have when operational). Including a DNS lookup to itself in the Network DNS settings.

I'll hope it helps.

 

[stuarta99]

Sorry just an update to this I think I have resolved the DNS issues but in the process killed Open Directory. This morning users weren't able to access data with the Local Network User account so I had to create them Local User accounts.

I'm hoping to rebuild with this fix tonight and hopefully OD will be ok. Although they do seem to be working well today and not sure if I really need the OD

1. So, downloaded WorkGroup Admin and installed (Thankfully it still works in 10.10)
2. From Workgroup Admin I exported the users and then the groups.
3. Open Server.app and I turned off OpenDirectory, then quit Server.app
4. Open terminal and destroy the directory
sudo slapconfig -destroyldapserver
5. Open Server app and set up a NEW OpenDirectory server
6. Add a test user and try changing the password to verify it is all working
7. If it works then blow away that user
8. Select Manage import Accounts from File and import your users and verify they all come in
9. Do the same but this time select your groups file
10. unfortunately this does NOT preserve passwords so you can either set a temp password and have users change it at login or if you know them you can re-enter them

 

[stuarta99]

Ok the above fix seems to have worked and Open Directory is now reporting correctly. I've removed the user accounts and re-entered them as Network accounts. Not sure what the benefit however is though between the local and network as network seemed to be working fine.

What I have noticed however is that when I click on the user the 'change password' option is greyed out, not sure why

 

[chrfr]

What I have noticed however is that when I click on the user the 'change password' option is greyed out, not sure why

At the top of the Users pane in the Server window, select "local network users" and at the bottom, a padlock will appear. Click the padlock (if locked) and enter your Open Directory admin user credentials.

 

[stuarta99]

Ok thanks will give that a whirl Monday. So better to use network over local?