Showing posts with label dns. Show all posts
Showing posts with label dns. Show all posts

Thursday, December 10, 2009

MOSS 2007 server not sending email for domain

So one of our Sharepoint 2007 Servers was not sending out email to anyone anymore after a datacenter move. The reason was dns issues related to the move.

Here is how it was solved:
MB - per yesterdays research and changes: A request was sent to NetSource to create a reverse DNS for the IP 68.70.161.12 to point to portal.harmonicconsulting.com. HarmonicConsulting.com MX records we edited to add portal.harmonicconsulting.com as a e-mail server with a low priority. The SMTP server was reconfigured to relay mail for the harmonicconsulting.com domain to google and Sharepoint was configured to use the local SMTP server to send mail. Rlaying to harmoinic from the SMTP server worked - I can't seem to add myself to the notification list here so I will wait to hear badck from the real bacuff to verify this is working now. - Mark

Tuesday, November 03, 2009

MOSS 2007 External Web Resolution Issues/Alternate Access Mappings

So when building a MOSS site, you cannot simply assign an IP say 64.24.232.177 and then make a DNS A record say moss1.yourdomain.com point to it, then in IIS configure that MOSS Web Site to run on say, port 80 for example.

No, that is not good enough, you have to tell Sharepoint about it -- go into Central Administration, then there is a slew of different alternate access mappings you can configure for the site.

There are different zones (dont you just love IIS/Internet Explorer?!?):
default, intranet, public, extranet, custom (blah blah)

All you really need to do to enable your moss site to be viewed externally (assuming you set the DNS as explained above) is:

1. In IIS, configure the host header for the site (right click it go to properties, Advanced, Add the DNS name i.e. moss1.yourdomain.com in the host header box).

and

2. In MOSS Central Administration, Operations, Alternate Access Mappings add a public URL as http://moss1.yourdomain.com (I just added it into the default zone and erased what was there -- the http://hcmoss02 which is the internal name of the server)

VOILA you are done. Now your site resolves externally. Take a coffee break.

Wednesday, July 01, 2009

DirectAdmin DNS issue same shared Linux server-cannot send email to other domain hosted on same server

So we are running Direct Admin on one of our shared linux web hosting servers and ran into a problem where one domain had switched email services to google apps (another mail server not hosted on the Direct Admin shared mail server).

So all other domains on that server could not send email to that domain since they thought the local server was still serving mail even though they changed the MX records to google servers.

Long story short to fix this go to:
Click on the domain in question, Click on Modify DNS Records, Click on Modify MX records, then uncheck the local mail server box as follows:
Local Mail Server
Use this server to handle my emails.
If not, change the MX record and uncheck this option
*Note: Making modifications to the MX records can potentially disable all of your email accounts from recieving mail.
ONLY make modifications if you know what you are doing.
Make sure to include the period at the end of the domain. (eg: mail.domain.com. )