OS X Server 10.9 vhost and alias is very slow?

Question

Hi.
I'm using OS X Server with Mavericks.
I have configured vhosts at my provider to point to my IP, and I would like to use those to serve webpages and be able to access them remotely to show my work to customers.
What I have discovered is that requests to vhosts on my OS X Server other than the default site are extreemely slow. (30 seconds+)
So I figured I would use aliases instead under the default site and point them to my development directory. No success, i'm still looking at 30s+
To sum it up.
Example.
sandbox.somedomain.com (Server Website) serves content properly.
Creating host1.somedomain.com is extreemely slow.
Creating sandbox.somedomain.com/alias on (Server Website) is extreemely slow.
I have tried to disable ipv6, created local DNS, edited /etc/hosts and so on.
If I do the same thing on my Windows PC, everything works and it's serving pages normally.
Any ideas?

Answer 1

Many Open Directory problems can be resolved by taking the following steps. Test after each one, and back up all data before making any changes.
1. The OD master must have a static IP address on the local network, not a dynamic address.
2. You must have a working DNS service, and the master's hostname must match its fully-qualified domain name. To confirm, select the server by name in the sidebar of the Server application window, then select the Overview tab. Click the Edit button on the Host Name line. On the Accessing your Server sheet, Domain Name should be selected. On the Accessing your Server sheet, change the Host Name, if necessary. The server must have at least a three-level name (e.g. "server.yourdomain.com"), and the name must not be in the ".local" top-level domain, which is reserved for Bonjour.
3. The primary DNS server used by the master must be 127.0.0.1 (that is, itself) unless you're using another server for internal DNS. The only DNS server set on the clients should be the internal one, which they should get from DHCP if applicable.
4. Follow these instructions to rebuild the Kerberos configuration on the master.
5. If you use authenticated binding, check the validity of the master's certificate. The common name must match the hostname and domain name. Deselecting and then reselecting the certificate in Server.app has been reported to have an effect in some cases.
6. Unbind and then rebind the clients in the Users & Groups preference pane. Use the fully-qualified domain name of the master.
7. Reboot the master and the clients.
8. Don't log in to the server with a network user's account.
9. Export all OD users, delete them, turn off OD, turn it back on, and import. Ensure that the UID's are in the 1001+ range.