Forum Replies Created
-
AuthorPosts
-
ToddJob
ParticipantThis works fines using the fred sub domain.
toddjob:~ todd$ nslookup fred.exampleco.com
Server: 10.32.32.32
Address: 10.32.32.32#53fred.exampleco.com canonical name = ns.exampleco.com.
Name: httpserver-02.exampleco.com
Address: 10.32.32.9However, when no sub domain is entered this is the results we have:
toddjob:~ todd$ nslookup exampleco.com
Server: 10.32.32.32
Address: 10.32.32.32#53Name: exampleco.com
Address: 10.32.32.32Any ideas?
*domains and ips have been changed per our security policies.
ToddJob
ParticipantI must correct myself. I am able to get wild cards working, only if I us the DNS server for the wildcard entry. however if use a wild card on any other server (machine) this does not work.
TK
ToddJob
ParticipantI try that and it did not work. It root domain points to the dns server only.
ToddJob
ParticipantHere’s process I use for exampleco.com
1) create a folder called exampleco.com in /Library/WebServer/Documents
2) set up the domain http Server Admin. ie http://www.exampleco.com
3) set up an account in WGM ‘exampleco’
4) set up ftp share point @ /Library/WebServer/Documents/exampleco.comThis is when the problem occurs. http service requires r/w permission to a folder in order to publish web pages. When you upload files via ftp the defaults 755 permissions with the users named ‘exampleco’ this is when the issues happen. http service needs to have user be ‘root’ or ‘www’ or group to be ‘www’ or ‘admin’.
Does this clarify what is happening?
ToddJob
ParticipantHere’s process I use for exampleco.com
1) create a folder called exampleco.com in /Library/WebServer/Documents
2) set up the domain http Server Admin. ie http://www.exampleco.com
3) set up an account in WGM ‘exampleco’
4) set up ftp share point @ /Library/WebServer/Documents/exampleco.comThis is when the problem occurs. http service requires r/w permission to a folder in order to publish web pages. When you upload files via ftp the defaults 755 permissions with the users named ‘exampleco’ this is when the issues happen. http service needs to have user be ‘root’ or ‘www’ or group to be ‘www’ or ‘admin’.
Does this clarify what is happening?
-
AuthorPosts
Recent Comments