Os x server app 2.253/16/2024 Getting all of these right first is critical. Then I'd move on to DHCP and finally Open Directory. I've chased problem too often with bad DNS so now if I see a bad DNS config and the server isn't online yet, I typically nuke and pave and get that part right before anything else. DNS is primary and you have to have it rock solid before you do anything else. A secondary (192.168.1.101) IP turns into your go to for everything else webish. Leave the primary in place for Server so it can do what it needs to for Open Directory and its internal websites. I multihome my servers due to the aggressive way Server app has been holding onto web ports. Deploy the server and get your SSL certs in place. Forward the appropriate ports for the services you plan to host on your server as you open them up so I don't worry about them yet. Typically I would put the modem into bridge mode and then let the airport handle the routing and NAT. Is your modem in bridge mode? What devices are handling NAT, DHCP, DNS?
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |