OSX Server Website DNS problems

I wanted to have a server  so I decided to get the mac mini server. We want to set up a small website with simple web services running on python and ruby.
Now I'm trying to set it up to have a website connected to our domain (olm.io), but the domain name doesn't forward to the mac mini server.
I believe the server is set up correctly. The router is set up to port forward incoming connections on port 80 to the server. To test that, connections to the ip 190.160.227.68 retrieves the server and shows up the test website.
I entered our ISP dns servers and also set up a dns server on the osx server.
From outside this shows from outside:
$ dig www.olm.io
; <<>> DiG 9.9.2-P1 <<>> www.olm.io
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 20417
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;www.olm.io.                    IN      A
;; Query time: 2431 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Thu Jan  9 14:54:03 2014
;; MSG SIZE  rcvd: 39
From inside the network this shows up:
$ dig www.olm.io
; <<>> DiG 9.8.3-P1 <<>> www.olm.io
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27239
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;www.olm.io.            IN    A
;; ANSWER SECTION:
www.olm.io.        10800    IN    A    192.168.0.10
;; AUTHORITY SECTION:
www.olm.io.        10800    IN    NS    www.olm.io.
;; Query time: 3 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Jan  9 11:54:25 2014
;; MSG SIZE  rcvd: 58
Also checking the hostname says its ok:
$ sudo changeip -checkhostname
Primary address     = 192.168.0.10
Current HostName    = www.olm.io
DNS HostName        = www.olm.io
Ok so from the inside of our network the website shows up, and from outside when looking at the public ip of the network the website also shows up.
What I'm missing is that when anybody types www.olm.io our website appears.
At one time I tried setting up Google public dns service, just to try it, but now it seems to be stuck referring to google 8.8.8.8 server,
$ nslookup 190.160.227.68                                                                                                                                                                                                                                               
Server:         8.8.8.8
Address:        8.8.8.8#53
Non-authoritative answer:
68.227.160.190.in-addr.arpa     name = pc-68-227-160-190.cm.vtr.net.
Authoritative answers can be found from:
$ nslookup www.olm.io                                                                                                                                
Server:         8.8.8.8
Address:        8.8.8.8#53
** server can't find www.olm.io: NXDOMAIN
I believe the problem is on the domain set up, which is as follows:
Registrar
Organization Name :
NIC.io
Primary Nameserver
Name Server:
ns00.olm.io
IPv4 Address:
190.160.227.68
Secondary Nameserver
Name Server:
ns00.vtr.net
Extra Nameservers (Optional)
Name Server:
ns01.vtr.net
screen of the dns setup
Thanks for the help

You will have two sets of DNS servers, your public DNS and the DNS running on your local network.  If your external DNS is getting to your servers, then that's probably working.  If you are getting the public IP address from your local network, then your gateway-router needs to "reflect" that address, or you'll need to configure local DNS services (OS X Server needs that in any case) to provide the local IP address for the public DNS name.
Put another way, read the article cited earlier and make sure your local DNS is correct.  You can test for most of the common network and DNS configuration errors with the following harmless, diagnostic Terminal.app command:
sudo changeip -checkhostname
...and this will tell you about the configuration, and whether no changes are required, or about the various errors that might be detected.
You can see what IP address you're getting with the following Terminal.app command:
dig +short oc.example.com
...or whatever DNS host name you're using.  You'll get either the public IP address (which if you use on the local network, your gateway-router needs to be able to detect that and run the connections back into your network) or your internal local network address.
Your local network clients will want to reference your local DNS server.
Do read the article cited earlier, too.

Similar Messages

  • Osx server website for virtualized application

    I hope someone can help me.
    On my OSX Mavericks server, I have a virtualized tomcat application. There is a Virtualbox instance, running Ubuntu, with bridged network. This means I have a unique IP number for this virtual machine. For tomcat I need to go to port :8080
    I do want to set a "subdomain.domain.com" to open this 123.1.1.1:8080.
    How do we set this in the webserver part of OSX server? Is this possible?

    You will have two sets of DNS servers, your public DNS and the DNS running on your local network.  If your external DNS is getting to your servers, then that's probably working.  If you are getting the public IP address from your local network, then your gateway-router needs to "reflect" that address, or you'll need to configure local DNS services (OS X Server needs that in any case) to provide the local IP address for the public DNS name.
    Put another way, read the article cited earlier and make sure your local DNS is correct.  You can test for most of the common network and DNS configuration errors with the following harmless, diagnostic Terminal.app command:
    sudo changeip -checkhostname
    ...and this will tell you about the configuration, and whether no changes are required, or about the various errors that might be detected.
    You can see what IP address you're getting with the following Terminal.app command:
    dig +short oc.example.com
    ...or whatever DNS host name you're using.  You'll get either the public IP address (which if you use on the local network, your gateway-router needs to be able to detect that and run the connections back into your network) or your internal local network address.
    Your local network clients will want to reference your local DNS server.
    Do read the article cited earlier, too.

  • Server Setup - DNS Problem

    I am trying to set up a Standard Server behind a router with Leopard Server. I have entered the following manual configuration during setup:
    Local Fixed IP: 192.168.77.15
    Subnet: 255.255.255.0
    DNS Servers: 65.106.1.196, 65.106.7.196
    Domain: server.XXXX.com (where XXXX is my domain name vonyz dot com)
    Name: XXXXserver
    I have a fixed IP address from my ISP and my domain A record points to that IP address and I have a PTR record that points back to my domain.
    The problem is that when the server goes through setup, it creates a server hostname of XXXXserver.local When I try to access the server from the outside, nothing happens. I have set up NAT on my router to forward all ports to the local 192.168.77.15 address.
    Any thougths on what my problem here is?
    Thanks, FVW

    If you are going to use this for server for mail you have to get the DNS set up right for that.
    Local Fixed IP: 192.168.77.15 -------- fine
    Subnet: 255.255.255.0 -------------- really the subnet mask, fine
    DNS Servers: 65.106.1.196, 65.106.7.196 -------- you can't use public DNS for private IP lookups but you can maybe use these as forwarders
    Domain: server.XXXX.com --------- domain is "vonyz dot com" not "server dot vonyz dot com"
    Name: XXXXserver ------ the the whole FQDN is "vonyzserver dot vonyz dot com"
    There should only be one A record for one public IP so either server, www or vonyzserver should be an A record and the others CNAME records to the A record name.
    And the reverse doesn't match as it is only "vonyz dot com" for the public IP.
    Pick one (the one A record name and it should be the one used for the mail server name if any).
    So if you have only these couple of IPs/names it would be easiest to reuse the domain name internally with only private IPs setup in the server DNS server for the services running in that server and public IPs and corresponding names setup for any public services hosted elsewhere (like mail currenty is).
    Or you could use another "private only" domainname internally like vonyz dot private but you still need the server to be able to resolve internal IPs for the public domain name if running your own public mail server (a correct reverse name is important when/if running your own mail server).

  • OSX Server Website

    I have my DNS for my subdomain forward to my home ip address. When I am not on my local network and type oc.example.com everything works. When I try to browse oc.example.com in my browser when I am on the same LAN as my server, nothing works. If I type the ip address of my server I get the default server app. Anyone know why I can't connect to my domain when I am on my local network, but works perfectly when I am remote?

    You will have two sets of DNS servers, your public DNS and the DNS running on your local network.  If your external DNS is getting to your servers, then that's probably working.  If you are getting the public IP address from your local network, then your gateway-router needs to "reflect" that address, or you'll need to configure local DNS services (OS X Server needs that in any case) to provide the local IP address for the public DNS name.
    Put another way, read the article cited earlier and make sure your local DNS is correct.  You can test for most of the common network and DNS configuration errors with the following harmless, diagnostic Terminal.app command:
    sudo changeip -checkhostname
    ...and this will tell you about the configuration, and whether no changes are required, or about the various errors that might be detected.
    You can see what IP address you're getting with the following Terminal.app command:
    dig +short oc.example.com
    ...or whatever DNS host name you're using.  You'll get either the public IP address (which if you use on the local network, your gateway-router needs to be able to detect that and run the connections back into your network) or your internal local network address.
    Your local network clients will want to reference your local DNS server.
    Do read the article cited earlier, too.

  • OSX Server 2.2.2 update broke my websites

    I updated to server 2.2.2 yesterday and my owncloud website on my server stopped working. It was so frustrating I restored via time machine. Is there something I should check so I can update again?
    Information of my setup.
    owncloud 5.0
    using osx server website feature pointing to folder.
    using ssl 443 port for my website.
    I have port 80 open as well but I have own cloud redirect to ssl.
    if you browse diectly to my server ip it brings up the osx server webpage.
    i have my computers point to my server ip for dns
    my dns server routes my local website dns to my local ip of server (had to do this because I was getting NAT loopback issues)
    all other dns should forward to opendns
    Please help, thanks!

    I have the same problem. Even trying http://127.0.0.1 from the server itself still the server cannot be found. My system log however is now generating what looks like an error from the server:
    Sep 20 20:09:34 home com.apple.launchd[1] (org.apache.httpd[69048]): Exited with code: 1
    Sep 20 20:09:34 home com.apple.launchd[1] (org.apache.httpd): Throttling respawn: Will start in 10 seconds
    This repeats constantly until the server is stopped.
    I'm guessing there is a permissions issue somewhere that 2.2.2 has now broken. No idea where to start to resolve.

  • OSX Server 10.6.3 - (Multiple) Website hosting via Server Admin

    Has anyone else experienced/had this problem? I am posting this hear in hopes that someone else has experienced this as well and may know how to correct/resolve this problem.
    We currently have purchased a collaboration software I have installed and I am running via OSX. The files are stored in /Library/WebServer/Documents/collab. OSX comes with a default website built in at /Library/WebServer/Documents. I intend to install the collab website in anticipation of adding more sites in the future and possibly utilizing the default OSX web services as well. I have set up our internal DNS server to route collab.company.com to the internal ip address of our OSX server. The default OSX webpage is currently hosted on port 80, I am running our collab site on port 8x (we are already hosting websites on a different server on port 80, and the router can only forward port requests to a single ip address).
    With this configuration, if I enter the address of collab.company.com, I get the default OSX server running on port 80. If I enter collab.company.com/collab, I then get our collab website (on port 8x). Essentially I want collab.company.com to open the collab website, not the OSX website. What is odd is, it seems that if I uncheck the default OSX webpage in server admin and disable it, change the collab site to port 80 as a test and go to collab.company.com I get a failed connection that the site is down or doesn't exist, like it is offline. It seems almost as if OSX is completely shutting down the entire directory of /Library/WebServer/Documents which is where the collab website exits inside of (Documents/collab). If I re-enable the default OSX website, then both websites become live again.
    So I guess my question is, is there a different structure/architecture that should be followed to prevent this behaviour? If so, how do I get multiple websites installed and configured properly in server admin to respond to their appropriate dns requests. I also forgot to mention for my collab site entry in server admin I have the host name in the general tab as collab.company.com, as well as the alias collab.company.com, but when I enter collab.company.com I am getting the default OSX site.

    I agree, this seems to make sense in theory, but here is the result I am getting.
    I have my internal (not my osx server) dns server containing a host entry of collab.company.com = 192.168.1.xx. I have a virtual host entry in OSX in the aliases area (correct?) of collab.company.com for my collab site. However, whenever I enter the url in my browser of collab.company.com, I keep getting the default Mac OSX Server website page. I even put an alias in the OSX server site of mainpage to try and differenciate it, but it doesn't seem to take or matter.
    So once again, in theory I think "oh, just uncheck the enable button next to the default OSX website", I uncheck it, and then both of my websites are offline, or appear to be? For my collab site, the link redirects, but I get the error page.
    Safari:
    Not Found
    The requested URL /collab/public/index.php was not found on this server.
    Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
    Apache/2.2.14 (Unix) PHP/5.3.1 Server at collab.company.com Port 80
    Google Chrome:
    Oops! This link appears to be broken.
    Thing is, I even changed my collab site to be running on port 80 as well as a test. I check enable for my osx default page, and they are both back online. If I change the default osx sites port to say 87 or something, and leave the collab at 80, I then get the same bad request messages etc. If I put the osx site back to port 80, they both work.

  • Help for first install of macpro with osx server

    Hello to all
    it's my first message on this forum, i'm seeking for help because i'm kind of new with Mac systems.
    I'm gonna explain the problem
    So we are going to buy a mac pro and put 4*2To inside with raid 5 and osx server.
    The problem is that the cost of installation of sotwre and deployement etc is really expensive.
    I need to create a vpn too, this mac pro is gonna be a storage and multiple users must have acces to it. In fact this mac will be connected on the router and users will acces to it on local network then later we're gonna move from our base so the mac will be at the home of one of us and other users will have to access it from outside.
    I was thinking avoyding cost of install by doing it myself.
    So i've thinked that the best way to do it is by asking help to the community.
    Is anyone can help me with this or tell me where i can find tutorials to do it?
    I have skills but this is hard form me. The thing is that i learn fast. But i need help.
    Maybe my post is not really clear i write as it comes to me, english is not my langage too.
    So feel free to ask me questions or informations if you need.
    In the same time i'm reading posts on the foum about this kindof installations.
    Thank u so much
    .anto.

    Dear Marcassin
    i am happy to help to your problem .
    first i would say you must read the Documentation. and you should familier with Mac Os installation System.
    in your Mac Server DVD you will find the schedule sheet . print that and plan your server first. it will really help full. then come and list down the all the requirements.
    may be you will need more services after that.
    But again again again . read that sheet and fill all the requirements. and come back or read specific captors in the Documentation.
    if you want more details about the installing sachira.herath at gmail
     certified Pro 10.6/10.5

  • Outlook doesn't want to connect with OSX Server on 2 out of 3 clients

    I have three computers on which I have installed Outlook 2011.  All three are running Mavericks.  On one of them, a MacBook air, I have established an outlook account connecting to my OSX server with no problems.  On the other two computers when I set the parameters the same way, I cannot establish an outlook account.  When I use Apple Mail on any of the three machines, I am able to establish accounts for iCloud and  the OSX server with no problems.  Can anyone point me to the source of this problem or a method for trouble shooting it?

    Hi tommy-ch,
    Apa kabar,
    Do visit and post your thread in boot camp discussion:
    http://discussions.apple.com/forum.jspa?forumID=1165&start=0
    There are more experience user on bootcamp that might gladly help you out.
    Good Luck.

  • ARD Reporting failing and causing thousands of entries in my system.log for my OSX Server clients

    I have a small four system network - all running latest version of Mavericks with latest (3.7.1 ARD)
    1) OSX Server running File Sharing, DNS, OpenDirectory, Web
    2) OSX Server running DNS (secondary), OpenDirectory (secondary)
    3) OSX Server - installed but not running any services
    4) OSX Client
    When using ARD from any of the systems, any attempt to generage an ARD report targeting system #1 or #2 - the ARD report task stops at "Collecting Report Data" and I start seeing:  sysinfocachegen[10506]: FSPathMakeRef error = -43 in the system.log that I'm targeting.  Currently over 11000 entries in my last log file (rolled over) and am over 8000 already in the log file after my last test. 
    If I target systems 3 or 4, reporting works fine. 
    Any ideas what is going on here?

    I'm getting this error too.
    20/5/2014 4:07:56.192 pm sysinfocachegen[27828]: FSPathMakeRef error = -43
    20/5/2014 4:07:56.192 pm sysinfocachegen[44825]: FSPathMakeRef error = -43
    20/5/2014 4:07:56.192 pm sysinfocachegen[63375]: FSPathMakeRef error = -43
    etc
    My OS is 10.9.3, ARD is 3.7.2 (372A19)
    I'm not trying to collect any report data as far as I know.
    I have a few ARD windows open.
    James.

  • OSX Server "Web Sites" port revocation?

    Hi:
    I'm trying to run a wordpress installation with MAMP on my MacMini late 2012, Running OS X 10.10.2 and OS X Server 4.0.3
    I have since played with the 'websites' feature but decided I didn't like it. So I installed MAMP and have set up wordpress inside of it. However because OS X Server's "websites" pane Auto fills the "server website" to have port 80 (and I can't seem to change it) I cant get MAMP to use port 80. It gives me the error attached by PNG to this post.
    I've disabled OSX Server 'websites' and attempted to remove the "server website" entry but I can't get it to release the port binding.
    Any help to get it to release ownership of port 80 would be most welcome.

    Couple of options. If you don't want to use any of the Server.app features, you can throw it in the trash and reboot.
    If you want to use some features, but nothing that uses apache, you could run:
    sudo launchctl unload -w /System/Library/LaunchDaemons/org.apache.httpd.plist
    The Server.app, when installed, will run apache on port 80 all of the time. No easy way around this without resorting to the command line.

  • Problems seeing website locally on osx server

    Hi..
    I wonder if someone can help me  i am quite new at all this .  I have a Imac wirelessly connected to an airport  extreme  which is connected  through a Gart2-4112 router . I am running Mountain lion  OSX10.8.5 and I  am trying to run a  website off this computer using mountain lion osx server.
    I have looked up several very good articles on the web and purchased osx server for dummies . Setting up the website looks easy   and I know I will run into future problems with trying to get the router port-forwarding   for my registered domain name  but for now I cannot get the website to show  on the server   “view Server Website” . From the default website I can see the default screen  for OSX server  I made the website up  in iweb ,  have published all the files into a desktop folder  which The store site files in  points to .
    The settings are drop down IP address  any   port 80   ssl none
    the error message i am getting is
    Not Found
    The requested URL /Falconsfc/Welcome.html was not found on this server.
    Apache/2.2.24 (Unix) DAV/2 mod_ssl/2.2.24 OpenSSL/0.9.8y Server at falconsfc.org.uk Port 80
    I am afraid I do not know what the problem is
    I would be grateful for any help   Many Thanks   Andy

    Don't store your files on your Desktop.
    Files on the desktop are, by default, owned by the individual user, and the Apache server doesn't have permission to view (or serve!) arbitrary files from a user's home directory or Desktop.
    By default, in Mountain Lion Server, web files should be stored in /Library/Server/Web/Data.
    You can use other directories if you like, but you'll need to jump through extra hoops to make sure Apache can see the files.

  • Website issue with osx server and hosting

    so i had a website hosted from my osx server and i had bought the domain name from godaddy it worked great but i desided to instead of hosting it on my osx server to just host it on  godaddy so i turned to server off and added the domain to my godaddy account hosting and now it works but one problem all computers can veiw the website but mine. i think it has somthing to do with the fact that my mac was the one hosting it. but if i go to my browser and go to my wesite i get a error but than i go to any other computer and it works great help please

    A couple ideas
    check our /etc/hosts file, you might have an entry for your domain.
    sudo pico /etc/hosts
         do you see any entries for your domain? If so:
         edit the file by navigating with the arrow keys, delete the line
         with your domain. Hit ctrl-x when done (enter 'y' to save the change)
    Clear your DNS cache
         dscacheutil -flushcache
    Try a different DNS server, go into your network settings (In System Preferences)
    Go to Ethernet or Wifi (whichever you are using), click Advanced and under the DNS tab enter:
         8.8.8.8
    Make sure no entries are ABOVE it.
    If none of this works, send the results of these commands:
         cat /etc/hosts
         cat /etc/resolv.conf
         dig +short mydomain.com   (replace with your domain)
    The results of these should point us in the right direction.
    Jeff

  • What are the right DNS records to host more than one site on OSX Server (ML). My conf in Server.app looks right but one of my sites lands on the default server. Any suggestion?

    I started using OSX Server on Mountain Lion a few days ago and it looks promising.
    I do however measure my ignorance in DNS matters...
    I defined two websites in addition to the the Default Server, so I have three names to deal with.
    For argument's sake
    - www.main.com is the default site
    - www.sitea.com is the first site
    - www.siteb.com is the second site
    I define a virtual host for www.sitea.com and another for www.siteb.com
    The resulting apache conf is what I would expect, I am pretty sure it is correct.
    So I modified my DNS entries (they were A records) to point to my new OSX Server.
    My result is:
    - www.main.com shows the default site
    - www.sitea.com shows the first site
    - www.siteb.com shows...the default site
    Any ideas?
    Cheers

    Thanks MrHoffman!
    My problem ended up being a name but not in the DNS!...In Apache.
    Your information allowed me to rule out possibilities and zoom in to the culprit faster.
    I just report here the conclusion hoping it can help someone else.
    When I installed OSX Server last week, I had in mind to principally run siteb.
    During the initial install, this is what I must have entered and then forgot about it.
    Then I defined my virtual hosts sitea and siteb and realised my machine was called siteb and changed its name to main to avaid a name collision. At which time I remember OSX Server telling me that changing the name could have consequences...But it apparently went ok, and it did except for one little thing.
    The consequence was this:
    in the main configuration file /Library/Server/Web/Config/apache2/http_server_app.conf the ServerName directive had remained siteb (instead of main). I manually updated it with TextEdit (could do vi from bash, its the same) and replaced siteb with main.
    There is a way to detect it.
    In Server.app, there is a "logs" panel, which displays all sorts of logs for everything including the websites.
    Each website's logs are presented as "access" and "error" logs. The information was there, but I could not see it because the viewing window in remarkably small for so much information in raw text...
    web logs are actually written to only two files in /var/log/apache2 (error.log and access.log)
    I openned two bash windows and run tail -f on error.log in one and tail -f access.log in the other.
    When I started the web service, apache threw a warning stating from mod_ssl saying that the certificate did not match the serve name...I the certificate was what I expected, I checked http_server_app.conf and found the ServerName directive that was not changed when I renamed my server...
    Easily fixed when its found, but it can take a while to find.
    BTW, I was using A DNS records for and it works, but I find your method of using CNAME records documents the administrator's intent better than with A records; I started to do the same. (A records a useful though, they can run a domain across multiple machines)
    Cheers mate!

  • How we set up multiple websites on OSX Server

    BACKGROUND
    After fiddling and futzing around for weeks (actually since last year) I've finally figured out how to set up multiple websites (virtual sites) using one port and one IP address. While there seems to be lots of discussion on this topic, it seems that the basic assumption is that one knows everything about websites, DNS and all that stuff, which I do not.
    When our network was originally established the engineer set up a wiki and also configured webmail, so we had two sites, one secured for mail and the other open for Calendar and the wiki. We were not hosting any websites locally because our school website is hosted by a company in New England.
    This year I wanted to set up websites for teachers and students. As great as the wiki is, there are some things it just can't do as well as a website. So I figured if I set up the sites teachers could link back and forth from one to the other. In addition kids could now start to use a real website instead of the cobbled together file mess I had when we ran a Windows network. Also iWeb is a much more accessible tool than FrontPage.
    SERVER SIDE:
    Snow Leopard Server - 10.6.4
    There are two - actually three pieces if you want your iWeb clients to connect to the server: Server Side Web Services, DNS and, in my case, FTP.
    ================================================ SERVER SIDE - WEB SERVICES
    If you haven't turned on Web services, you'll need to open Server Admin and do that. If you don't know how to set up web services - just reply and I'll step you through that as well.
    Once web services are set up and turned on, you'll see it listed under your server’s name in the Server Admin sidebar. Click on "Web" and then click on the "Sites" tab at the top of page. This is where you list all your sites.
    Click the plus button and enter the fully qualified name of your site, for example: "students.myschool.org". Don't use the defaults here (no name) - that's what got me in trouble before. BE SPECIFIC!
    You'll be looking at the "General" tab (the other tabs, "Options", "Realms", etc. we'll deal with in a second).
    On the "General Tab", the default IP address ("any") and port (80) is just fine. We'll run everything over port 80. (Apache figures all the virtual site stuff out - you don't need your rocket science degree for that.)
    "Web Folder:" is important because this is how you'll "segment" your websites. While I would NEVER do this again, we have a solid state hard drive for the OS and a RAID array for our data files. IF you have that, make sure you do NOT use the default "Web Folder" because it will store all your files on your solid state drive. There may not be enough room, over time, on that drive. I've not experienced it yet, but it's my understanding that if the drive fills up, the server shuts down.
    I store my web sites on a folder on the RAID array.
    Everything else on that tab can be left as the default. (Just make sure that you have an "index.html" or "index.php" file in your web folder root, but iWeb will take care of that for you.)
    I would put in your email address in the "Administrator Email:" field.
    Under "Options" you really don't have to put anything. I've tested making websites with iWeb and it doesn't appear that anything needs to be checked.
    Nothing needs to be entered in "Realms" as well from what I see working w/ iWeb.
    The defaults in "Logging" are fine.
    You can leave "Security" alone, but we do have a (self-issued) certificate listed for our webmail site.
    "Aliases" is important. Under "Web Server Aliases" you enter how you want the site to respond to when users type in a URL in their web browsers.
    When our web server was initially set up the engineer set up "wiki.myschool.org" on port 80 and "mail.myschool.org" on port 443. In the aliases section was nothing but a "*" (the wildcard character). That means, from what I can figure out, that the webserver will respond to these sites regardless of what is typed in the URL. (Well, something like that - point is, if you create OTHER websites, you'll NEVER get to them because the wildcard character in the "Aliases" section, in effect, grabs those web requests and redirects them to the sites that are already there.
    In my case I deleted both of those wild card characters. For my "wiki.myschool.org" site, I entered "mail.myschool.org". That means if you type EITHER "wiki." or "mail.", go to the site that’s stored in the “Web Folder” we set up when those sites were created.
    For "mail.myschool.org" I just DELETED the wildcard character. I wanted that site (since it was secured) only to respond to "mail." - nothing else. (You're not going to that secured site for any other reason than to get your mail.)
    "Proxy" can be left blank. Have no idea what that does. As time permits I'll do some research and figure out what it's used for.
    "Web Services" is if you want to provide any MORE services to this particular site. Most likely you'll want to uncheck all the boxes. For our "wiki." site, we have checked "Wikis", "Blogs", and "Calendar". For our "mail." site we have those checked PLUS "Mail".
    I would create a separate "Web Folder" for each of your sites. I don't know if that's a requirement but for housekeeping purposes, I would keep the sites separated. And I SUSPECT that it's "best practice" to separate your wiki from your other websites.
    SERVER SIDE - DNS
    OK...now you have to make your site reachable and the only way to do that is to set up DNS so that folks don't need to type in the IP address of your web server. You need to set up DNS inside your network and, if you want folks in the outside world to reach your website, you'll need to set up an external DNS as well. I'm going to cover INTERNAL DNS - if you don't know how to set up EXTERNAL DNS - reply or email me and I'll post those instructions.
    Most likely you have already created Zones for you network...all you really need to do is create "Aliases" so that when you type "students.myschool.org" your web browser will know that site resides on IP address XXX.XXX.XXX.XXX.
    If you've set up Zones then you already have a "Machine" setting that translates your server’s name to an IP address and vice versa.
    All you need to do is create an "Alias" (CNAME) record for, in this case, "students". You’ll see the choices for types of records when you click the "Add Record" button.
    There are only two fields to configure for a record: "Alias Name" - in this case "students" and "Destination" - in this case "servername.myschool.org". (You've already entered a machine record that says "servername" = 192.168.1.x.)
    That's it for Internal DNS.
    SERVER SIDE - FTP
    Now you have to get iWeb to communicate with the webserver.
    There are only three ways iWeb will communicate with webservers: MobileMe, Local Folder and FTP Server.
    Local Folder is really only practical if you want to host a website on a laptop (I was blown away initially when I found out that all Macs had a built-in web server - how neat is that?). I think there are some very cool things teachers could do with configuration, and, of course, you wouldn't need to set up any web services on the web server, but that's for another discussion. You need to set up FTP services on the web server.
    Turn on and enable FTP on your webserver.
    You can leave the defaults for "General", "Messages" and "Logging". "Advanced" is the only thing you want to set. I set "Authenticated Users See:" to "Home Folder Only". I set the "FTP Root" to the same root folder in which I plan to store my web sites (/VOLUMES/RAID Array/WebServer/Documents). This setting sets that folder only to be accessible via FTP.
    I would suggest returning to your DNS settings and adding one more "Alias". Set "ftp." to point to your webserver. Why? So folks can edit their sites from home (see below).
    CAVEAT: If you are running FTP on other servers, make sure that the settings here do not conflict with the settings on the other servers. For example, I'm running FTP on my file server so that my scanners can communicate with it. However, I configure my FTP settings by machine name and NOT "ftp.myschool.org".
    ================================================
    CLIENT SIDE - CONFIGURING iWEB
    Now you have to configure iWeb so that it will communicate with your server.
    Click on the "Site" icon so that "Site Publishing Settings" appears.
    Publishing:
    "Publish to:" = "FTP Server"
    You can set the "Site name:" and "Contact email:" to whatever you want. But see below!
    FTP Server Settings:
    "Server address"=ftp.myschool.org (you could also enter in servername.myschool.org or the IP address. However, if you want folks to be able to work on the site from home, you will need to configure external DNS for that. If you use the IP address, you're out of luck for remote access to the site. (You can do it but it's beyond the scope of this discussion.)
    "Username" & "Password" should be your user's network login credentials.
    "Directory/Path" - this is important. Remember, you set your "FTP Root" to be "/VOLUMES/RAID Array/WebServer/Documents". If you leave this field blank then the website will be dumped into this folder. If you are only setting up one site, that may be OK. However I wanted to set up a "students" site folder, a "faculty" site folder and a separate site for our literary magazine.
    THEREFORE: I have, in my ..../Documents folder (on the server), a "students" folder, a "faculty" folder, and a "litmag" folder.
    SO...in my "Directory/Path:" field, I have "/faculty". That means the full path to this website is "ftp root/faculty" or "/VOLUMES/RAID Array/WebServer/Documents/faculty" (You don't need a trailing "/" character. iWeb will automatically append the folder for you user depending on what you entered in "Site Name:" in the "Publishing" area.
    Website URL:
    This is the root website depending on whether it is "students" or "faculty". Since iWeb will append the site name to this root website, I accomplished what I hoped to accomplish in this post (http://discussions.apple.com/message.jspa?messageID=12288561#12288561).
    Faculty sites will be @ http://faculty.myschool.org/username. Students @ http://students.myschool.org/username. PERFECT!
    iWeb is such a GREAT tool - NOW the kids can start using it!
    I want to reiterate that this works for our school but it should work for you as well. There may be better ways to do this but it works for us.
    Hope this has been helpful and you won't have to spend weeks trying to figure this all out by yourself!

    OK...here's how we did it.
    To get access to the website you created from outside your network there are a couple of steps.
    First, you have to have a STATIC IP address from your ISP. If you have a T1 circuit, no problem...you usually get a couple of static IPs you can use. However, if you have a cable modem circuit, most likely you have a dynamic IP address which changes when you connect to the internet. Usually a static IP will cost a bit more because the ISP has to go through a couple of steps to set it up for you. But once you have the address, you now have a way for folks outside your network to connect with you.
    (I’m also assuming that you use a router of some sort through which traffic flows out to the internet and that you aren’t using connection sharing or something like that.)
    The next thing you need to do is have your new static IP address associated with the server on which you are hosting your website. You've probably already done that if your website works inside your network. However, you've associated a private ip (192.168.x.x, etc.) to your web server. That doesn't mean anything to folks on the outside because private IP addresses are just that - private - folks can't access them. (I won't get into VPN because that's a whole other topic.)
    The way you associate your new static IP address to your web server is through some sort of dns application from your ISP. For example, we use TierraNet to manage our external DNS information. They have a web interface control panel that is very similar to the DNS interface for XServer. You can create CNAME records (aliases - other ways that folks can access your servers).
    Basically you create an "A" (CNAME) record with a fully qualified domain name (e.g. webserver.myschool.org) and point it to your public IP address (XXX.XXX.XXX.XXX) which you just got from your ISP. It's going to take a while (24-48 hours) for this change to take effect. BTW, you can create as many “A” records as you want. For example mail.myschool.com and wiki.myschool.com could point to the same place.
    You want to make sure that the fully qualified domain name you enter in the external dns utility matches the name you used when you created your internal dns records on your XServer.
    OK...so now folks can get to your domain - but, remember, you have a private network IP scheme between them and you. You now have to tell your router that when web traffic arrives, allow it inside the network and direct it to your web server.
    Let's say your public IP address is 205.100.112.50 and your web server is 192.168.0.5.
    You have to create, in your router’s "Security Zone" (router companies call them different things) a couple of rules. Usually the first rule is: "Let everything inside the network get out to the web." You've probably already done that if folks inside the network can reach the internet.
    You then have to tell the router to allow web traffic (port 80) into your network AND redirect that traffic to 192.168.0.5.
    We use AdTran routers and they have a web interface which allows you to write "rules" affecting public and private traffic. Public is folks outside the network, private is folks inside.
    AdTran calls them "Security Zones" and you modify those zones with policies.
    So my "Policy" would say, in the above example, redirect traffic from my public IP (205.100.112.50) -> to my web server -> (192.168.0.5).
    THEN you have to modify this policy with what AdTran calls "Traffic Selectors". You've said, OK, you can get in, but WHAT can get in?
    The "Traffic Selector" is written to say: "Permit" "TCP" traffic from 205.100.112.50 only through Port 80. (That's the port that web traffic goes over. If you wanted a secure website, you'd add another traffic selector that opens port 443, for example.)
    I'll tell you I'm no genius when it comes to this. I called AdTran and had them configure my router for me. I told them what I wanted done, they remoted into the router and configured it. But then I could go to the web interface and see what they did and then added rules later on when I wanted, for example, to get access to the network via Apple Remote Desktop or VPN into the network on my iPad.
    I'd bet that your router has a maintenance agreement that includes this service and if it doesn't it should have.
    I did find that I still had issues when I tried to set this up originally and it had to do with the ORDER of the policies. I can’t remember exactly what the issue was, but, effectively one of the policies highjacked traffic before the policy that I wanted got triggered. Simply moving them around in the list fixed that issue. So if you have this set up but still can’t access the site, check the order of your rules.
    I don’t know if that helps or not, but I try to think about this stuff conceptually and then get someone to help me with the details. I work with this stuff so infrequently that I forgot how I did something 6 months or a year ago. I’m in the process of creating a wiki for the school which documents all this stuff, but that’s a major undertaking.
    Cheers,
    John

  • OSX Server DNS Setup

    Hi Folks,
    I am hoping someone out there can assist as its almost 2AM and I am still trying to get this thing working. I have a MacMini running OSX Server. I have 5 Mac Clients on my network and the purpose is basic file sharing, iCal, Address Book etc etc. I want to have a Local DNS service to resolve names on the LAN and have it forwarded to my ISP to resolve those its not authorative about.
    I have configured the server to the point where it will:
    - Resolve DNS queries from clients for addresses it is not authorative about by using the forward DNS servers.
    - Resolve reverse queries eg: nslookup 192.168.1.100 (fixed ip for my srvmacmini)
    But it will not resolve local hostnames, for example:
    watsonad-mbpro:~ watsonad$ nslookup 192.168.1.100
    Server: 192.168.1.100
    Address: 192.168.1.100#53
    100.1.168.192.in-addr.arpa name = srvmacmini.anthonywatson.net.au.
    watsonad-mbpro:~ watsonad$ nslookup srvmacmini
    Server: 192.168.1.100
    Address: 192.168.1.100#53
    ** server can't find srvmacmini: NXDOMAIN
    Looking into the logs which I have set into debug mode, I can see the following:
    <truncated>/IN/com.apple.ServerAdmin.DNS.public: has no NS records
    Now - I have tried recreating the zone entries, I can see them listed in /var/named/zones in the right db.* files and have walked through that configuration.
    I have set the DNS entry for the server itself to 127.0.0.1 and numerous other suggestions I have seen in the posts here but just cannot seem to get this working.
    Am hoping the guru's here can assist - ready and willing to trawl through logs etc if more info is needed. I can see others have had this problem but cannot seem to find the post where it got resolved in a way I could repeat the same steps.
    Cheers

    Looks like this ones not yet solved - I change the DHCP server from 127.0.0.1 to 192.168.1.100 and renewed the lease to refresh the settings:
    watsonad-mbpro:~ watsonad$ hostname
    watsonad-mbpro.anthonywatson.net.au
    watsonad-mbpro:~ watsonad$ nslookup watsonad-mbpro
    Server: 192.168.1.100
    Address: 192.168.1.100#53
    ** server can't find watsonad-mbpro: NXDOMAIN
    watsonad-mbpro:~ watsonad$ nslookup 192.168.1.16
    Server: 192.168.1.100
    Address: 192.168.1.100#53
    16.1.168.192.in-addr.arpa name = watsonad-MBPro.anthonywatson.net.au.
    watsonad-mbpro:~ watsonad$
    So here are the zone entries, now these have all been created by server admin utility - below is the db.anthonywatson.et.au.zone.apple file , the one in the "named" directory points to this one of course:
    ;GUID=3B5D7974-F072-4F38-B319-76FCFB4CCF1E
    ;selfResolvingHostname=0
    $TTL 10800
    anthonywatson.net.au. IN SOA 127.0.0.1 Anthony.anthonywatson.net.au (
    2011012912 ;Serial
    86400 ;Refresh
    3600 ;Retry
    604800 ;Expire
    345600 ;Negative caching TTL
    anthonywatson.net.au IN NS 127.0.0.1
    watsons-imac.anthonywatson.net.au IN A 192.168.1.51
    watsons-imac.anthonywatson.net.au IN HINFO "iMac 27" "OSX Snow Leopard"
    watsonad-MBPro.anthonywatson.net.au IN A 192.168.1.16
    watsonad-MBPro.anthonywatson.net.au IN HINFO "Macbook Pro 13" "OSX 10.6 Snow Leopard"
    srvmacmini.anthonywatson.net.au. IN A 192.168.1.100
    srvmacmini.anthonywatson.net.au. IN HINFO "Mac Mini" "MAC OSX Server 10.6"
    watsontm-MBPro.anthonywatson.net.au IN A 192.168.1.26
    watsontm-MBPro.anthonywatson.net.au IN HINFO "13 Macbook Pro" "OSX Snow Leopard"
    lb.dns-sd.udp IN PTR anthonywatson.net.au.
    b.dns-sd.udp IN PTR anthonywatson.net.au.

Maybe you are looking for