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.

Similar Messages

  • Help with OSX server mail setup

    Please if anyone can tell me what I am doing wrong, I would be very grateful.  I have a company with an externaly hosted website and an an internally hosted email (OSX server).  I have everything kind of working, but some things don't seem quite right.  I'll explain below:
    I have a purchased domain: mycompany.com hosted by godaddy.
    I am using Godaddy name servers: ns65.domaincontrol.com and ns66.domaincontrol.com
    The external godaddy DNS has an a name entry for my mail server: mail pointing to 123.123.123.123 (which is my companies external static IP address).
    There is also a null (@) a name record for my website hosting service (squarespace) pointing to 456.456.456.456
    There is a cName record www pointing to the squarespace domain "www.squarespace6.com"  (know this is unusual, but it is how squarespace asks this to be set up and does not work otherwise)
    There is an MX record with priority 10 and host name @ pointing to mail.mycompany.com
    I have a airport extreme router with the appropriate ports forwarded to the OSX server.
    The DNS servers on the router are pointed to the internal IP address of the OSX server
    I did not change the domain name on the router (mistake?) it is currently san.rr.com
    On the OSX server I have set up host name to be mycompany.comDNS is set up with primary zone being mycompany.com
    Primary Zone entries include
    nameserver = mycompany.com
    machine record host name is mycompany.com and the IP address is the internal IP address of the OSX server
    another machine record with host name "mail" and IP address is the internal IP address of the OSX server.
    Finally, there is a mail exchanger record with mail server "mail.mycompany.com" and priority 10
    There are 2 entries autocreated in the Reverse zone
    Mail is setup and running on the OSX server providing mail for "mail.mycompany.com"
    Users are setup with email address: [email protected] (note: without the mail subdomain - I think this is OK?)
    I am using self signed certificate.
    In my clients (windows Thunderbird, Mac Mail, iOS mail), the settings are for the incoming mail server host name to be "mail.mycompany.com" and the outgoing also to be "mail.mycompany.com"
    I woud have expected this to be imap.mycompany.com and smtp.mycompany.com respectively, but it doesn't work when I input these values and works with the former.  Have I set this up wrong??  imap seems to require SSL on port 993 and SMTP seems to require TLS on port 587.Outlook on PC gives me an error that after googling appears to be a problem with not recognizing a fuly qualified hostname form the SMTP client.  I see the fix, but wanted to know if that meant that my server didn't have a fully qualified host name and whether I should change that rather than just remove that restriction???
    The final problem is that my outgoing emails seem to be getting caught up in other people's spam filters too frequently.  What is the main reason for this?  Is it because I have set something up wrong and it brings up flags or is it simply because I am not a huge hosting company, or somethign else althogether?
    If you've gotten this far, big thanks!  If you can help me, even more thanks!

    Well, actually they are both getting caught up in spam filters and bounced back.  I actually realized that part of the problem is that I have a dynamic IP address, but it doesn't change.  Regardless, on the bounce back it looks like hotmail and other domains are rejecting email from my IP and recognize it as dynamic.  This was a test server that i would by physically taking to my business where there is a static business IP address (Cox).
    Sorry for the very long original message, but it seems that most people don't post enough information for the problem to be solved in their original posts and I was hoping to provide as much detail as possible.
    The other is the question of "are things set up right?"  It seems strange to me that both my outgoing and incoming servers are "mail.mycompany.com" and not imap.mycompany.com and smtp.mycompany.com and I wonder if this is going to cause me to have problems?
    Is it a problem that my email addresses are [email protected] and not [email protected]?
    Was I supposed to change the domain name on the router?
    Also is it going to be a problem that I am using a self signed certificate?

  • Snow Leopard Server DNS setup

    Where is there a step by step setup for making my Snow Leopard Server with DNS? Essentially, I am looking to setup a mail server but seem to be missing what information I need to gather from the folks that host my domain and how to point traffic to my network.

    When I started setting up my first Mac OS X Servers a few years ago I had to completely retrain my brain because the MacOS does not follow the traditional nomenclature of Windows Active Directory and DNS setup. That being said like AD for Windows MacOS relies very very heavily on a healthy and properly running DNS system, both internally and externally. So one great resource I found was about 10+ hours of training on Leopard Server over to Lynda.com. I think you can sign up for a month long membership but it's well worth the investment if your looking for some basics thru advanced setup of Leopard Server. Now SLS is much much easier at the setup and deployment and some of the fundamentals of the setup interface have changed greatly (as an improvement) but the videos are still very applicable.
    Basically it comes down to the following steps in order to get your website/e-mail/wiki services working.
    1. Purchase your .whatever with a registrar, godaddy, doster, network solutions ect...
    2. Make sure you have a fully routable PUBLIC IP address from your ISP that you can assign to the WAN (internet side of your router)
    3. Contact your ISP and ask then to create an rDNS entry for your .something to the IP address they assigned you. Usually this will look like xxx.xxx.xxx ---> mail.mydomain.com when you test later on.
    4. Modify the DNS records with your registrar to point the MX & A record to your new IP. You will log in create an A record for mail.mydomain.com ---> xxx.xxx.xxx (your public IP on router) and then you will create an MX record for e-mail which will simply be mail.mydomain.com with a value of 10 (there is usually a screen for this).
    5. Once all the DNS is setup and working properly (Can take several days for these changes to take affect and be visible by your ISP) then you can begin the configuration of your router. You will need to determine what IP internally you want your Mac to be. Usually 10.0.0.1 or 192.168.1.1 or other and document that. Program your router to port forward ports 25,110, 80, 143 to the IP that you decided your Mac will be at so those services will be publicly available to you to user. Otherwise nobody will ever be able to send you e-mail or visit your site.
    6. This is a good time to check your work and settings by visiting www.mxtoolbox.com and you verify your rDNS (setup by ISP) and your DNS (Setup by you) before beginning your setup of OS X SLS. If everything checks out then start the install if not STOP HERE and fix it because it will haunt you in the long run.
    7. Start the install of SLS and at some point the system will get you to the screens at which you input your domain information. If all was setup properly up to now SLS will auto-populate the domain and local hostname of your Mac Server. U can change the local hostname if you wish but the domain name information should reflect your rDNS and A record information of mail.mydomain.com and you can hit next and proceed with the rest of the install.
    8. Once up and running you will need to make a small adjustment to the alias of your e-mail. For some reason the engineers at Apple left a flaw in (my opinion) that is as such. Whenever you send e-mail it will go as [email protected] instead of what you really want which is [email protected]. So follow this post below and you will be all fixed up in a jiffy.
    http://discussions.apple.com/message.jspa?messageID=10110723#10110723
    Hope this helps.

  • Mac OSX Server DNS

    Hello Community,
    I am trying to do something really simple, and some how its become really advanced.
    I have a Snow Leopard server that will become an imaging system. The system sits on a closed network so no FQDN is required.
    I want to name the server MelbImage.local but for some reason I am unable to do this without defining nameservers which a one computer network won't have.
    I have tried binding an NS to the local machines static IP but the information disappears upon save. Any ideas?

    I have the same issue, alex238.
    Sorry Sven-Goran Ljungholm1, I don't understand your reply.

  • 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.

  • 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.

  • New server Network & DNS Setup

    I just got a New Dual G5 Server and set it up using the pdfs from apple. Mainly the Getting Started Appendix B page 149 Small Business Setup using the Gateway Setup assistant. I ran into all sorts of problems like being unable to login to the open directory and i think it was my DNS setup that was the problem i then changed the setup multiple times using various How-tos in this thread to no avail.
    So i have reinstalled the the Server software and will start again using the following steps.
    This is my first post so i please let me know if i have provided enough info or to much?
    SETUP:
    ADSL 2 connected to DLINK 4 port Wireless Router (24Mbps) 1 port plugged into Ethernet 1 on Server. Router is setup as a DHCP using 192.168.0.1 and 192.168.0.2 for xserve. subnet mask is 255.255.0.0 (dynamic ip address from ISP)
    Xserve Ethernet 2 will provide DHCP and NAT via a 16 port switch to Computers and Printers. Setup as 192.168.2.1, 255.255.255.0
    I want to use the xserve as a file server, filemaker database server, web server for a test site for some of our content and also possibly an email server.
    INSTALL
    1. Install OSX 10.4 with ethernet settings above eth1 is DHCP eth2 is manual
    assigned, no services will be set to start up and i choose Standalone
    Server
    2. Update with Software Update
    3. Setup DHCP for the Clients - Start Service
    4. Setup DNS use " company.private" for the host name and the DNS server ip
    will be the 192.168.2.1 address
    5. Upgrade to Open Directory Master and Kerberize
    6. Setup Sharepoints for Data Storage and Home directory location
    7. Start Apple File Services AFP
    8. Create user Accounts / Groups
    9. Setup Directory Access on clients to see LDAP server and DHCP.
    Login from clients to get an automounted sharepoint and Home directory,
    "sounds easy when i type it up like that".
    Could anyone let me know if i am doing it the right way or if there is anything i have missed wrong order or something important.
    Should i change the routers subnet mask to 255.255.255.0 ?
    Obviously wireless clients will have access direct to internet due to the router and the routers DHCP. Can wireless users access their Home directory in this manner via the ethernet 1 port?
    Should i just let the router handle the DHCP for everyone and plug it into the switch with only 1 ethernet being used on the server?
    I will eventually have to have another subnet for student computers in the future.
    I would greatly appreciate any advice

    Pretty long post, and I doubt anybody here will want to go through the entire setup process. However, I'd re-think your baisc hardware configuration.
    I don't know why everybody gets so excited about using that second ethernet port on the Xserve. It's necessary in some setups, but if you already have a router providing DHCP on a small network it seems like overkill.
    I'd setup the chain in this order:
    Internet - ADSL Modem - Router - Switch - Xserve / Computers / Printers
    Setup your server with a manual IP address (192.168.0.2 is fine). Point it to itself as the DNS server.
    Leave the router at 192.168.0.1, and configure the router to assign DHCP above the Xserve's address (say, from 192.168.0.10 and up). Also let the router handle NAT.
    Network homes work over wireless, but it's not an entirely satisfactory experience. You might consider using portable homes instead; sync times will still be slow, but overall you'll cut down on network traffic and it should at least appear faster to your users.

  • Mail Setup at OSX Server issues

    I have several devices (iPad, iPhone, Desktop and Laptop) that access my email accounts (Personal-POP and Business-IMAP accounts) without any issues.
    I'd like to use my Mac Mini OSX Server as a main client to all these emails account and collect emails and distribute it at my local network.
    Is it possible? I'd like to use all resources from my ISP that can handle with virus, security ... but at the same time I'd like to keep local at this OSX Server all messages that we usually send and receive when we are using local network at office. I read manual several times but is not clear for me if this feature is available.
    All suggestions will be welcome.
    Edison

    OS X Server and most mail servers do not include the ability to collect mail from remote servers, though it is possible to build a somewhat precarious scheme  based on forwarding messages from the remote servers involved. Google's mail service and its gmail client do have the ability to retrieve mail from other remote mail servers without resorting to forwarding mail around, but you'd need to integrate something like imapsync or fetchmail to perform this on OS X Server.  (Related — my old replies to related questions here in the forums will often mention imapsync, as well.)
    In general when running a mail server that's accessible to the Internet, you'll need DNS and also static (fixed) IP from your provider for OS X Server and this is the preferred and most reliable means, this if if you want to send outbound mail through the server, or you'll need to relay your inbound and outbound mail through one of the relay services providers.  Static IP and proper DNS can also be a factor when receiving mail from some of the more cautious mail servers around.  Failing to have IP and DNS correct mails mail sent from your server can be dropped, and sometimes mail sent to your server will be dropped before being passed to your server.
    OS X Server does include some spam- and malware-related capabilities and various Postfix, Amavis, ClamAV and related pieces to keep a lid on most typical spam shenanigans, though you might want additional services or the replacement of the OS X Server mail server with the mail package from Kerio.

  • Help with Proper DNS Setup for Leopard Standard Server Setup

    Hello All,
    Problem Description-
    I was reviewing some training today on DNS setup and checking for proper setup with the sudo changeip - checkhostname tool and I seem to have an incorrectly configured DNS setup. So I need some help on correcting it. When I go to the "Server Preferences" tool I cannot log in using apple.ourdomainname.com instead in order to use the tool I have to input localhost as the server name. Now I just thought that the system was broken or something and with the help of my training I now see it's a DNS problem. I thought I had everything proper since I followed the steps of creating proper DNS/RDNS entries with my ISP. Now I am stuck wondering what else isn't working properly due to the DNS issue. Thanks in advance.
    Technical Info-
    My ISP provides us with 5 static IP's and we have asked them to create entries and verified the setup of apple.ourdomainname.com = x.x.x.x which is one of our public IP's assigned currently assigned to the WAN port of our Apple Airport Extreme. We have also had them create a PTR record which also is present, verified and functional. Our MacMini running 10.5.5 is connected directly to one of the ethernet ports on our Apple Airport Extreme which is our NAT/Firewall for the LAN. So during the setup of the Standard Server install the OS configured the Airport with the required ports for chat/web/vpn. And mobile Mac's can VPN in and gain folder access and web works fine too. We don't use the e-mail portion so I can't say how that works. The server is using the DNS of 10.0.200.1 which is the IP of the Airport and the airport is programmed with the DNS of OpenDNS servers 208.67.222.222 and 208.67.220.220. The reason for this whole long shpeal is that I want to give as much technical background as possible for the best possible help.
    Thanks
    DM

    What happens when you use 'Localhost' instead of 'localhost' (i.e. capitalizing the 'L')?

  • 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!

  • Osx lion dns server, forward certain domain searches to other dns server

    Hi!
    i'm configuring the DNS service in OSX 10.7.1. I want to forward all queries to certain domain (f.e. *.special_domain.com) to certain dns server (f.e. 192.168.0.1 & 2)
    i remember in previous OSX Server versions that you can do that in an easy way:
    there were a /etc/resolver directory where you can place a text file in order to forward certain domain queries to certain dns server, like this:
    filename: /etc/resolver/special_domain.com
    content of this file:
    nameserver 192.168.0.1
    nameserver 192.168.0.2
    now in lion there is no such directory... someone knows how to do that??
    thanks for reading and regards!
    D

    i've just read about the "scutil" tool
    From the reply of the command "scutil --dns" i understand that is possible and also supported (i guess)
    Now i have to discover what files that tool reads, and which is the proper way to modify that
    I'll keep investigating tomorrot, now i'm saved by the bell!!

  • How do we setup OSX Server 10.4.9 to allow Windows XP SP2 to print?

    Background information:
    We have 3 printers setup on OSX Server 10.4.9.
    All 3 are shared in the Print Server as IPP & SMB.
    Windows Services are up and running as a PDC allowing users to login and use anything in their respective home folders from the Windows computers.
    All computers are on the same network/subnet.
    We have made no major changes to OSX Server at this point.
    Problem:
    Someone logs into one of the Windows computers using the Domain ran by OSX Server.
    In Windows explorer they goto \\SERVER. Once there they see all 3 printers and a "Printers and Faxes" folder containing the same 3 printers.
    The 3 printers inside "Printers and Faxes" allow their queues to be looked at in Windows but will not allow themselves to be connected to the Windows computer. They give the same message that the 3 printers outside of the "Printers and Faxes" folder give:
    "A policy is in effect on your computer which prevents you from connecting to this print queue. Please contact your system administrator."
    Question:
    What must we do in order to get the printers working for use with Windows?
    PowerBook G4 12 867MHz   Mac OS X (10.4.9)   iMac G5 20 2GHz, iPOD Nano 1GB, iPOD 60GB

    print:currentQueues = 3
    print:setStateVersion = 1
    print:currentJobs = 0
    print:logPaths:logPathsArray:arrayindex:0:name = "Print Service Admin log"
    print:logPaths:logPathsArray:arrayindex:0:path = "/Library/Logs/PrintService/PrintService_admin.log"
    print:logPaths:logPathsArray:arrayindex:1:name = "CUPS: error_log"
    print:logPaths:logPathsArray:arrayindex:1:path = "/var/log/cups/error_log"
    print:logPaths:logPathsArray:arrayindex:2:name = "CUPS: access_log"
    print:logPaths:logPathsArray:arrayindex:2:path = "/var/log/cups/access_log"
    print:logPaths:logPathsArray:arrayindex:3:name = "CUPS: page_log"
    print:logPaths:logPathsArray:arrayindex:3:path = "/var/log/cups/page_log"
    print:logPaths:logPathsArray:arrayindex:4:name = "AppleTalk: HPLJ4250"
    print:logPaths:logPathsArray:arrayindex:4:path = "/Library/Logs/atprintd/atprintd.100_151.log"
    print:logPaths:logPathsArray:arrayindex:5:name = "AppleTalk: HPJ4250CSR"
    print:logPaths:logPathsArray:arrayindex:5:path = "/Library/Logs/atprintd/atprintd.100_152.log"
    print:logPaths:logPathsArray:arrayindex:6:name = "AppleTalk: HPLJ2200"
    print:logPaths:logPathsArray:arrayindex:6:path = "/Library/Logs/atprintd/atprintd.100_153.log"
    print:state = "RUNNING"
    print:readWriteSettingsVersion = 1
    print:pluginVers = "10.4.140"
    print:startedTime = "2007-05-24 16:55:05 -0400"
    ================================
    All 3 queues are setup for SMB.
    ================================
    Access has:
    "Use same access for all services" checked.
    "Print" does not show up on the grayed out list underneath it.
    However, AFP, FTP, iChat, Login Window, Mail, SSH, VPN, Web, Weblog, Windows and Xgrid all do.
    "Allow all users and groups" is chosen as well.
    ================================
    PowerBook G4 12 867MHz   Mac OS X (10.4.9)   iMac G5 20 2GHz, iPOD Nano 1GB & 60GB, AppleTV 40GB

  • Maverick osx server and dnssec for dns master/slave services

    Hi,
    I have some questions to the maverick osx server.
    Is this possible to configure dnssec keys for the maverick osx dns server?
    Where are the configuration files from the dns server located?
    Thomas

    Okay - shortly after posting I found the checkbox "allow zone transfer" in the zone settings but there seems to be no way to control which secondary servers are allowed.
    Anyhow I would like to know, where the config and zone files ar on Yosemite Server.

  • Which mac mini should I get to setup osx server

    Hello!
    I run a small development team though we are fairly new at working together and we're trying to setup an efficient development environment for us.  I've recently stumbled on to 'continuous integration' and had heard that a Mac Mini server can go a long way toward reaching that goal. 
    Keep in mind, though we're iOS developers and are technologically competent, none of us have server admin experience.
    Unfortunately the latest update to Mac Mini does not have a server model.  That leads me to the following questions:
    1) Should I purchase an older mac mini that is already setup as a server?  (aka, Mac mIni server)
    2) Should I purchase one of the newer models and install OSX Server myself?  I heard it's cheap off the Mac App store, so price is not a concern, but I'm not sure what the tradeoffs are of getting one that is already a supposed server, and setting one up myself as a server.
    3) If I do purchase one of the three newer models, how do I know which one I need to support our environment?  Lower cost is obviously better, but I don't want to short change ourselves on the required power.  We would use the server mostly for file sharing, collaborating, code repos, CI, etc.  We have a website that we host on Godaddy and I would move it to our server if I could, but this is low on the priority list.
    I'm also open to options such as, do none of the above and wait for a new Mac mini server model to come out, but I'm anxious and want to get started
    Thanks so much for your help and advice!
    Frankie

    A server model is NOTHING but a 2nd 2.5" HD and the OSX Server APP
    buy a quad core mini (on sale now at best buy), and purchase a 1TB Hitachi ($65) 7200RPM HD off ebay
    and purchase the server APP from the APP STORE.
    OR, just find a new or used server model 2012 Mini
    dont even think about fooling with the new 2014 Mini.   Lost cause.
    I use godaddy as well, and ergo have NO need for a Mini server, even though I own 4 Mac Minis.
    godaddy is cheaper and easier ......you should possibly consider the same

  • DNS setup on server bound to AD and using domain controllers for DNS

    My server is bound to our AD network and in the network pref I have entered the two IPs for the domain controllers on our network that serve DNS.
    My question is, am I right not to enable/configure and start the DNS service on the Mac server since it is getting DNS already?
    If yes, how do I confirm that my Mac server is correctly listed in our domain controllers DNS? Should I be concerned that I get the following?
    knws3135:~ mactech$ sudo changeip -checkhostname
    Password:
    Primary address = 10.31.3.135
    Current HostName = knws3135.ad.ewsad.net
    The DNS hostname is not available, please repair DNS and re-run this tool.

    Hi
    It looks all OK to me? As for the hostname having capitals could pose a problem but only if the Mac Server was its own KDC. Which it is not. If the hostname is defined as you have it now in the AD's DNS Service then leave it alone.
    Sometimes even when DNS checks out OK you can still have fundamental errors that only demotion to Standalone will cure. I think this is the point that you are at now. To be honest I would do this. Judging from what you've said there would be very little to lose when you do this apart from managed preferences. These can easily be re-applyed on successful promotion.
    needs to be changed so it is configured in Open Directory as connected to a Directory Server
    Not sure what you mean by this?
    If you have or are about to update your Server to 10.5.4 - which I recommend you do. Then you could follow this procedure:
    Demote to Standalone
    Stop all Services
    Restart the Server
    Update to 10.5.4. Restart the Server (this happens anyway)
    Make sure your Server resolves on the forward and reverse pointers (again)
    If you want run changeip again (you may be surprised)
    Use the Active Directory plug in in Directory Utility to bind the Server to the AD. Make sure you use an AD admin account that has authority to do this. De-select 'force home directory creation on startup disk' I have a feeling this will be de-selected anyway.
    After successful binding quit out of Directory Utility and launch Server Admin
    Select the Open Directory Service
    Change the role from Standalone to Open Directory Master
    Create the Directory Administrator account's username and password. Don't be tempted to change the UID or use the system admin account's user name. You can use the same password if you wish. What I've done before in the past is to create the diradmin account on the AD first with full authority for the domain.
    On successful promotion you should now see in the Overview Pane everything running apart from Kerberos which should be Stopped. This is how it should be. Apple's 10.5.4 Update has took a lot of the donkey work out of this whole process. No need for the command line. Simply click.
    If you launch Directory Utility you should now see the server's loopback address has been added in the LDAPv3 Plugin. Also the Server should be topmost in the Search Order under the Authentication and Contacts field. Bind your clients first to the AD and then the OD (make sure use for authentication and contacts are unchecked).
    Browse the two nodes, add your groups and apply MCX in the usual way.
    Does this help?
    Tony

Maybe you are looking for