DNS problem on Snow Leopard Server.

I have a mac mini server on my network running DNS, File Sharing, Open Directory, and Web services. I believe that I have everything configured properly, but I'm having a perplexing issue with DNS. I also have some client machines on the network, and I need to be able to access the websites on those machines as well...(for testing purposes, etc.).
So, here is a little bit about my DNS config, and the issue that is happening:
I have a primary zone: domainname.com
under this zone, I have:
an A record:            server.domainname.com pointed to 10.0.1.2 (This points to my mac mini server)
another A record:    imac.domainname.com    pointed to 10.0.1.3 (a different machine)
another A record:    server2.domainname.com   pointed to 10.0.1.4 (another machine)
When I go to server.domainname.com, I get the correct machine (the mini server). This works.
Here is the issue:
But, when I try to go to imac.domainname.com or server2.domainname.com, they both resolve to the server's website.   If I'm on my server, and pull up safari, the domain names go to the correct machines, but from any machine other than the server, everything resolves to the server's website instead of re-routing to the correct machines.
So, it appears that the DNS records are written, because it works when I try to pull up the sites from my server machine, but there must be something going wrong because when I try from any machine other than the server, those domains (imac... & server2...) just resolve to my server website instead of going to the correct machines.
Has anyone seen this behavior before, or does anyone happen to have any ideas?
Thanks Community!
JMG

Try:
dscacheutil -flushcache
on the client. Then confirm you are configured with the correct DNS server:
ipconfig getpacket en0
Check value of server_identifier and make sure it is your DNS server.
Then explicitly resolve to it using'
nslookup imac.domainname.com 10.0.1.2
This assumes that 10.0.1.2 is you DNS server.

Similar Messages

Are there any problems with Snow Leopard Server (Xserve) and PPC Clients

Hi,
are there any problems identified yet with Snow Leopard Server, installed on a Xserve and PPC Clients running Mac OS X Tiger and Leopard?
Currently I have a Xserve Intel running Leopard Server and about 12 Mac Minis PPC running Mac OS X Tiger and Mac OS X Leopard. The Xserve serves services like DNS, OpenDirectory, Software Update Server, NetBoot, etc. All users have Home Directories stored on the Xserve.
Now I want to install Snow Leoaprd Server on the Xserve, but I wonder if there are any problems using the PPC Clients? I have read something like this on a german website.
Thanks!

We've actually found that the Server 10.6.3 DVD does an amazingly smooth job of upgrading 10.5.8. We've been upgrading our production servers and nothing has gone wrong yet. Snow Leopard employs an archive and install method of upgrading which results in an install which is very close to a clean install. So it's been very convenient for us because our servers are used as Windows PDCs and it's a pain in the *** to have to re-join all PCs to the domain if we start from scratch.

DNS problems with Snow Leopard

I have had this problem for a long time, but it is especially annoying me today. My Mountain Lion iMac (2012 model) is slow to establish an internet connection when it wakes from sleep. My Snow Leopard machine has a much crisper and reliable connection. And, once the connection on the iMac balks ("you are not connected to the internet"), it takes longer than it should to correct itself. I can get to new sites (ones I haven't tried) more quickly than I can with the ones that failed. That's why I think this is a DNS issue.
But there's more. The Apple-provided software actually takes the connection down almost always. The App Store and iTunes will almost certainly bust the connection. If I try to listen to a sample on iTunes, it will invariably stall at midpoint, say it's buffering, and then crap out. Lots of "Error -1009" messages (or something like that). What should I do?
When I get a connection going, as with Netflix or something streaming, it's generally stable. That's why it's only an aggravating problem and not quite a deal breaker. But still, why am I turing to a Snow Leopard machine to get my work done?
Thanks for your help!
[Other details: I use a lousy 2Wire router from ATT, which has always been somewhat sketchy with the connection. I stopped using Safari because, for some reason, it has a higher success rate than Safari. Just weird and no one has had an answer.]

Thanks, Barney. I've put these in and will let you know if things get better. My first check seemed better, but you know how these things go. I seem to remember putting the Google addresses in before and seeing the problem return. I can't say I really understand what DNS does.
Also, I added the DNS servers, but there is still a greyed out "Search Domain" listed as gateway.2wire.net, which, obviously, is a domain assocaited with this router.
I'll give you points once I figure out if this is a solutuion.

DNS problems with Snow Leopard. Can't upgrade to Mountain Lion either.

My Macbook Pro has been working quite well since I got it just over a year ago, until last week when I shut it down to go stay at my parents house. I turned it on when I got there and it automatically connected to the network because i go there often, however when I tried to open up a browser it would not work. I opened up several of the other browsers that I have but all of them kept saying they couldn’t connect to the server. I thought perhaps my dad had changed the router settings or something since last time I'd been there since the internet was working perfectly at my house only two hours previous. He said he hadn't changed anything and he was right, the internet worked perfectly through my sisters PC and through his ipad and my iphone. I later took it round to a friend’s house where it remembered his network too but still would not open addresses in the browser and when I finally got home to my house, I found I had the same problem. With every network I connected to I could update my apps and software, use my torrent client, ping certain IP's and connect with various other things that require internet connection, but the browser still never worked. After some research I came to the conclusion that it was most likely a DNS issue, I found this odd as I had not changed any sort of settings at all recently, except for turning the firewall on, which I turned off be3fore trying to troubleshoot. I have tried virtually everything that has been suggested on the internet like Flushing DNS cache, resetting PRAM, bringing my network to the top, turning airport on and off, connecting through ethernet, renewing DHCP lease, using google IP as DNS, checking for set proxies, repairing disk permissions, resetting router, checking router settings, the list goes on and on. The last thing I tried was to copy the com.apple.mDNSResponder.plist file then delete the old one and paste the new one back in, since then my Mac cannot connect to the internet in any of the previous ways.
After pulling my hair out for days, I thought the only option left was to upgrade to Mountain Lion, which I was planning on doing anyway. After downloading it though, I came to the option to select the disk I want to install to only to see my primary and only disk open my Mac coloured faintly and telling me that "This disk cannot be used to start up the computer". After more research I found that there were a few issues, none of which I have. I’ve never used time machine so there is no issue with any set partition for it, I have no other partitions on it at all either so I cannot use the resizing trick that seems to help most people. I would normally just backup all my data at this point and do a fresh install, but haven't got the funds to purchase a another TB at this point and I have over 650GB worth of valuable data on the Mac. Could someone pleeeease help me!?!?!

You cannot go to Mountain Lion, as stedman1 states.
But you can upgrade to Lion, possibly. See http://support.apple.com/kb/HT2404

New Snow Leopard server problems -need advice.

hello everyone. I just setup a mac pro with Snow Leopard server to replace our G5 which was setup up for simple file sharing as a fake server and am having several challenges listed below:
*I've made sure the new computer running SL server has the same local name and IP address as the previous G5 (now off of the network)
- Our windows (Vista) computer cannot see the server on the network. This was not a problem with the G5 and SMB filesharing.
- I cannot access server preferences due to this error: "Unable to set node credentials for /LDAPv3/127.0.0.1 with the record name server.mydomain.com$ There may be a problem with the Open Directory service."
- server admin is treacherously slow both locally and remotely.
I cold really use some help on these folks. I'd sincerely appreciate it.

Thanks for your input everyone. I turned off DNS (just to see) and it's still slow. Frankly I am not sure if I even need it yet. My goal is only to setup local services and then open the server up to the WAN.
My provides the DNS I suppose. MY ISP points to my WAN IP and my router directs that to my server's internal IP. At least that's how things are setup now and left over from when i was using Snow Leopard client as a fake server (for filesharing and DayLite).
I did setup the initial DNS settings of Snow Leopard Server after the install to the computer's IP address which I assigned manually and left the rest to get from my router's DHCP server. I setup the zone (home.mydomain.com)
Any ideas for the sluggishness.

DNS Configured-Best Practice on Snow Leopard Server?

How many of you configure and run DNS on your Snow Leopard server as a best practice, even if that server is not the primary DNS server on the network, and you are not using Open Directory? Is configuring DNS a best practice if your server has a FQDN name? Does it run better?
I had an Apple engineer once tell me (this is back in the Tiger Server days) that the servers just run better when DNS is configured correctly, even if all you are doing is file sharing. Is there some truth to that?
I'd like to hear from you either way, whether you're an advocate for configuring DNS in such an environment, or if you're not.
Thanks.

Ok, local DNS services (unicast DNS) are typically straightforward to set up, very useful to have, and can be necessary for various modern network services, so I'm unsure why this is even particularly an open question. Which leads me to wonder what other factors might be under consideration here; of what I'm missing.
The Bonjour mDNS stuff is certainly very nice, too. But not everything around supports Bonjour, unfortunately.
As for being authoritative, the self-hosted out-of-the-box DNS server is authoritative for its own zone. That's how DNS works for this stuff.
And as for querying other DNS servers from that local DNS server (or, if you decide to reconfigure it and deploy and start using DNS services on your LAN), then that's how DNS servers work.
And yes, the caching of DNS responses both within the DNS clients and within the local DNS server is typical. This also means that there is need no references to ISP or other DNS servers on your LAN for frequent translations; no other caching servers and no other forwarding servers are required.

Nslookup Snow Leopard Server DNS problems

I have a mac mini that I'm trying to turn into a snow leopard server. Attached to the mac mini I have three external hard drives which act as back ups to our mac book pro laptops. I have installed the server software and downloaded all the updates and I can see the drives on the server and I can acess the external drives and backup to them with out a problem. The issue that I have is that when I run nslookup I get an error message which tells me that it can't find my name and that I need to rerun so software commands.
I'm also unable to run either dns or podcast producer which was the main reason for buying the server software. I have a static ip address and believe I have configured everything correctly but I just can't seem to sort out the DNS and problems.
Any thoughts - thanks
Russell

This is the Discussions > Mac OS X v10.6 Snow Leopard > Installation and Setup forum. Your questions involve Mac OS Server, which is a different OS product. Thus, you will get better results posting to the Apple - Support - Discussions - Mac OS X Server forums.

How to resolve network issue or dns to access web page on snow leopard server?

I have my network setup like as follows:
internet > router 1 > ethernet ports > switch > router 2
I have a mac osx snow leopard server connected to "router 1", but it is so slow when accessing a web page hosted on the server from a browser on a workstation connected to either router 1 or router 2?
Is there a problem with my network setup or maybe because I changed the name to newservername.local?

@Jeff and @Camelot,
I think it is a DNS issue. I completely reset the DNS settings on server and the local name with the steps below, but now cannot access the site hosted on the server at all
I used a modified version of http://www.mkahn.com/2010/09/configuring-dns-on-mac-os-x-10-6-snow-leopard-serve r-for-hosting/ to reset the server set
1. Stop DNS Service in Server Admin
2. Close Server Admin
3. Obtain 10.6 DNS Default files (below)
4. Overwrite the DNS files with DNS Default files:
/etc/dns/loggingOptions.conf.apple
/etc/dns/options.conf.apple
/etc/dns/publicView.conf.apple
/var/named/named.ca/etc/named.conf
/var/named/named.local
/var/named/localhost.zone
5. Restart your server
All machines have 1ms ping responses within the network including this snow leopard server that I am trying to setup. There is another test web server that return pages instantly within this network so I doubt it is a network issue, but a DNS issue.

Unable to access gateway and DNS via VPN (L2TP) with Snow Leopard Server

Summary:
After rebooting my VPN server, i am able to establish a VPN (L2TP) connection from outside my private network. I am able to connect (ping, SSH, …) the gateway only until the first client disconnects. Then i can perfectly access all the other computers of the private network, but i cannot access the private IP address of the gateway.
Additionally, during my first VPN connection, my DNS server, which is on the same server, is not working properly with VPN. I can access it with the public IP address of my gateway. I can access it from inside my private network. A port scan indicates me that the port 53 is open, but a dig returns me a timeout.
Configuration:
Cluster of 19 Xserve3.1 - Snow Leopard Server 10.6.2
Private network 192.168.1.0/255.255.255.0 -> domain name: cluster
-> 1 controller, which act as a gateway for the cluster private network, with the following services activated:
DHCP, DNS, firewall (allowing all incoming traffic for each groups for test purposes), NAT, VPN, OpenDirectory, web, software update, AFP, NFS and Xgrid controller.
en0: fixed public IP address -> controller.example.com
en1: 192.168.1.254 -> controller.cluster
-> 18 agents with AFP and Xgrid agent activated:
en1: 192.168.1.x -> nodex.cluster with x between 1 and 18
VPN (L2TP) server distributes IP addresses between 192.168.1.201 and 192.168.1.210 (-> vpn1.cluster to vpn10.cluster). Client informations contain the private network DNS server informations (192.168.1.254, search domain: cluster).
_*Detailed problem description:*_
After rebooting the Xserve, my VPN server works fine except for the DNS. My client receives the correct informations:
Configure IPv4: Using PPP
IPv4 address: 192.168.1.201
Subnet Mask:
Router: 192.168.1.254
DNS: 192.168.1.254
Search domain: cluster
From my VPN client, i can ping all the Xserve of my cluster (192.168.1.1 to 18 and 192.168.1.254). If i have a look in Server Admin > Settings > Network, i have three interfaces listed: en0, en1 and ppp0 of family IPv4 with address 192.168.1.254 and DNS name controller.cluster.
The DNS server returns me timeouts when i try to do a dig from my VPN client even if i am able to access it directly from a computer inside or outside my private network.
After i disconnect, i can see in Server Admin that the IP address of my ppp0 interface has switch to my public IP address.
Then i can always establish a VPN (L2TP) connection, but the client receives the following informations:
Configure IPv4: Using PPP
IPv4 address: 192.168.1.202
Subnet Mask:
Router: (Public IP address of my VPN server)
DNS: 192.168.1.254
Search domain: cluster
From my VPN client, i can access all the other computers of my network (192.168.1.1 to 192.168.1.18) but when i ping my gateway (192.168.1.254), it returns me timeouts.
I have two "lazy" solutions to this problem: 1) Configure VPN and DNS servers on two differents Xserve, 2) Put the public IP address of my gateway as DNS server address, but none of these solutions are acceptable for me…
Any help is welcome!!!

I would suggest taking a look at:
server admin:vpn:settings:client information:network route definitions.
as I understand your setup it should be something like
192.168.1.0 255.255.255.0 private.
at least as a start. I just got done troubleshooting a similar issue but via two subnets:
http://discussions.apple.com/thread.jspa?threadID=2292827&tstart=0

SNOW LEOPARD SERVER PROBLEMS REQUIRE CERTIFIED CONSULTANT TO HELP

I've had a pretty unstable Snow Leopard server install since it was upgraded from Leopard a few months ago. Some of the problems were said to be hardware related, but I've been unable to migrate it to a different computer (Mac Mini).
The current installation is running, albeit poorly.
We had a Mac consultant involved in these issues, but he has proven to be unstable and unreliable as well - so we're on a search for a new consultant to give us some paid assistance in straightening this thing out.
We're not on the US mainland, but can make the server accessible by ARD and/or SSH to someone.
Someone with Apple certification would be preferred.

Hi Brian,
I'm an IT consultant dealing with Mac OS Servers and Windows Servers as well as Linux. I can offer a few helpful suggestions since just recently I transferred data from a Mac OS 10.5.8 Server to a 10.6.2 Server.
My first question to you is what data are you immigrating from? example 10.5.8 Server Data to 10.6.2 server?
The reason why I ask this since IMAP data in 10.5.8 and before was using Cyrus and starting in 10.6 apple switched to Dovecot.
Initially, I did not realized that apple made the switch and had stalling problems using the apple migration tool. (Personally I don't think the tool works well since a lot of others are running into this problem when researching this issue).
In the end I decided it was best to important everything manually, mail and not use the apple immigration tool since I think it has some issues.
The first thing I would do is make sure the DNS is configure right so that the server can resolve it's name which is very important.
Hopefully you're been running Open Directory . Export the users from the old server and import it to the new 10.6.2 server.
Next transfer the IMAP mail from 10.5.8 server to the 10.6 server to the same locations.
Example in 10.5.8 server default location is
/var/imap
and
/var/spool/imap
note this is where cyrus stored imap data in 10.5.x and maybe before. I have to look at my old 10.4 server since I'll be upgrade my own server soon.
My clients Servers have been upgrade fine by doing the manual method.
anyway...
keep those two locations in mind of where you mail is stored.
next I would copy your old cyrus mail to the new server. Don't use the migration tool at all. Just setup the new server and get the DNS running so it can resolve itself before you do this.
also make sure mail server is not running and it's off.
open up a terminal window
copy and paste this but change the name of the volume/hard drive name (HD_name)
sudo /usr/libexec/dovecot/migratemaildata.pl --cyrusBin "/Volumes/HD_name/usr/bin/cyrus/bin" --database "/Volumes/HD_name/var/imap" --sourceSpool "/Volumes/HD_name/var/spool/imap" --targetSpool "/var/spool/imap/dovecot/mail"
ok do this will convert all of your cyrus mail to dovecot. Make sure you've already imported the users from Open Directory before doing this script.
after all of this
there's still one more step
for some reason the postfix "main.cf" file is configured to use cyrus in 10.6.2 update.
/etc/postfix/main.cf
you can use the pico editor if you like.
example
type in at terminal window
sudo pico /etc/postfix/main.cf
it should be near the end of the file
don't bother with anything that's in # which is ignored.
look for
mailbox_transport = cyrus
then change it to
mailbox_transport = dovecot
save the changes
edit settings in the mail server with server admin to what you had... I recommend don't importing the mail settings from the old server admin since some people reported that its better just to manually configure it.
however for other server admin settings you might try to export and import to the new server.
If you have any questions just let me know and I'm glad to help the mac community.

Configure DNS on Snow Leopard Server for Web Hosting

Hi Everyone,
I put together an article on my blog about Snow Leopard DNS setup for web hosting. http://www.mkahn.com/?p=279
I'll be revising it over the next few weeks to make it more informative based around feedback. Let me know if you have any questions or trouble setting up DNS on Snow Leopard Server for web hosting.

Thanks for your replies. I realize I'm not making clear the way this network is configured . Also, the only services running on the Snow Leopard server are (at this time):
dhcpd - in the 10.136.31.x range;
dns - same as before;
planned to add are:
Open Directory (for network logins)
Software update;
Web (only on the 10.136.31.x Ethernet);
mySQL (localhost only - for moodle);
NAT is not set up on the Snow Leopard server itself. We have an outside router, a Cisco 2811. This router provides routing for both the public IP range, and the NAT range is configured in this router. The forwarding dns is located in LR and Fayetteville. So what I need is dns on Snow Leopard to forward outside queries to the state DNS servers, and resolve the local NAT IP only for Open Directory and a set of Snow Leopard clients.
Is this going to be possible?

Creating a versatile DNS and redirection service on Snow Leopard Server

For the few of us who use Snow Leopard Server as a main DNS for our small network, the following is a workflow that I would like to share with the board for creating redirection services to not just sites found on the locally hosted apache but also external sites.
+IF you are adding a second domain name, the reverse domain lookup will not appear and you will need to add a Machine/A record with the fully qualified domain "domainname.com." (don't forget the . at the end) into the new zone and it will point to the "server" Machine/A record ip address.+
*DNS Portion* : (ServerAdmin > DNS > Zones >
Add Zone > Primary > Create a fully Qualified Domain name and dns "server" in the Machine / A Record
Create the (add Record > Alias/ CNAME) subdomain pointing to the server.domainname.com e.g. (library)
*Web / Apache Portion :*
Create a new site (ServerAdmin > Web > Sites > Plus button)
With General > host name exactly as spelled in above subdomain in full (library.domainname.com)
Select Web Folder where the site is hosted
If you are creating a redirection, create a folder on the server, add an index.php (with the script below)
Add Alias with the same subdomain as number 2
_PHP script :_
<?php
$location = "http://example.net";
header("Location: ".$location, "301 Moved Permanently");
?>
// Edit the "http://example.net" to which ever e.g. "http://apple.com"
_Alternatively you can also mask the page with :_
<html>
<head>
<title>Same Title As Your Homepage</title>
<script type="text/javascript">
function changeTitle()
if (top.frames['main'].document.title)
top.document.title=top.frames['main'].document.title;
</script>
</head>
<frameset>
<frame name="main" src="http://actual-url.anotherhost.com/page.html"scrolling="auto" target="main" ONLOAD="changeTitle();">
<noframes>
<body>
Place a suitable message here for people with browsers that can't read frames.
</body>
</noframes>
</frameset>
</html>

Ok, local DNS services (unicast DNS) are typically straightforward to set up, very useful to have, and can be necessary for various modern network services, so I'm unsure why this is even particularly an open question. Which leads me to wonder what other factors might be under consideration here; of what I'm missing.
The Bonjour mDNS stuff is certainly very nice, too. But not everything around supports Bonjour, unfortunately.
As for being authoritative, the self-hosted out-of-the-box DNS server is authoritative for its own zone. That's how DNS works for this stuff.
And as for querying other DNS servers from that local DNS server (or, if you decide to reconfigure it and deploy and start using DNS services on your LAN), then that's how DNS servers work.
And yes, the caching of DNS responses both within the DNS clients and within the local DNS server is typical. This also means that there is need no references to ISP or other DNS servers on your LAN for frequent translations; no other caching servers and no other forwarding servers are required.

Small problem: how using "Remote Desktop" on Snow Leopard Server

Hello,
How can I login to the Mac Mini Snow Leopard Server from 2 different Macs ?
Before I bought my Mac Mini Server in July, I asked the Apple Support if Snow Leopard Server has the equivalent of the Windows Remote Desktop functionality. He told me that it is possible. He did not tell me how, but I believed him.
I cannot find it in the documentation. Only 1 person can use screensharing. But I need more than 1 person working on the Mac OS X Server.
I moved our Photo library to the Mac OS X Server. With filesharing it takes 5 minutes to start iPhoto on our client iMac ( 1Gbps network). That is unworkable. So, from more iMacs users have to login to the server and start iPhoto on the server.
Thanks for the solution.
Hubert Anemaat

As per Jason's reply, there are two Terminal Server products available for Mac OS X. I have been testing both, both work in the same sort of way and will allow multiple simultaneous users to connect.
The typical approach is to (obviously) first to install one of these Terminal Server programs on your server. Then you (ideally) need another server hosting your Mac network home directories, and it needs to share the network home directories via NFS rather than AFP.
Note: Due to the way Mac OS X handles mounting AFP shares, you cannot have two users using the same share at the same time as the login defines the privileged's and the first logins privileged's would not be suitable for the second user, this is also why you cannot use "Fast User Switching" with two network login accounts when using AFP.
So, a client uses an RDC client (e.g. the free Microsoft Remote Desktop Client) to connect to the Terminal Server, this initiates a network login which access the users home directory via NFS.
RDC client (Mac or PC) ------> Mac Terminal Server <------ Mac network home directories
I have not tried iPhoto, but have tried various other applications, e.g. FileMaker, AppleScript, Microsoft Office 2004, etc. and the only problem I have hit so far is that Visual Basic in Office 2004 generates errors but Word and Excel otherwise work. Remember Office 2008 does not support Visual Basic (i.e. Macros).
I would actually expect iPhoto to work for multiple users as long as you use NFS. Using NFS for network home directories rather than AFP has actually 'fixed' a couple of badly written applications that had problems with AFP based network home directories, e.g. Adobe Acrobat 9.
I am using Mac OS X 10.6.4 Servers.

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.

Problem connecting with VPN after migrated to SNOW LEOPARD SERVER,

Hi,
I recently migrated to Snow Leopard server, I have a strange issue when connecting to the VPN Server.
Please find the below error.
Fri Jan 1 14:38:22 2010 : CHAP peer authentication succeeded for jasmine
Fri Jan 1 14:38:22 2010 : DSAccessControl plugin: User 'jasmine' authorized for access
Fri Jan 1 14:38:22 2010 : MPPE required, but keys are not available. Possible plugin problem?
Fri Jan 1 14:38:22 2010 : sent LCP TermReq id=0x2 \"MPPE required but not available\"
Fri Jan 1 14:38:22 2010 : Connection terminated.
Fri Jan 1 14:38:22 2010 : Connect time 0.0 minutes.
Fri Jan 1 14:38:22 2010 : Sent 0 bytes, received 0 bytes.
Fri Jan 1 14:38:22 2010 : PPTP disconnecting...
Fri Jan 1 14:38:22 2010 : PPTP disconnected
2010-01-01 14:38:22 IST --> Client with address = 192.168.1.76 has hungup
Please let me know what is the cause and how can i fix it.
Thanks,
Gulab Pasha

Did you turn on the Printer Sharing in the "Share" preferences panel?
And, for Windows computers to access your printer, they need to install "Bonjour for Windows", which is a part of the iTunes+Quicktime install package, I believe.
Alternatively, you can turn on SMB sharing on your Mac, which is also in the "Share" preferences panel. You first highlight and turn on "File Sharing", then there is an "Options..." button to the right, clicke it and check the checkbox of "Share files and folder via SMB (Windows)".

DNS problem on Snow Leopard Server.

Similar Messages

Maybe you are looking for