MX Records Resolving to IIS

Discussion forum for Enterprise Edition.
Post Reply
netmo
Posts: 31
Joined: Mon Jun 20, 2011 7:46 pm

MX Records Resolving to IIS

Post by netmo » Fri Jun 24, 2016 4:29 pm

Hello,

Recently noticed the mx records resolve to IIS when entering the address in a web browser. for example: mx.domian.com will resolve to the servers IIS default website. Under the default website MEADMIN and MEWebMail are listed. Why is port 25 resolving to the web servers IIS?

rfwilliams777
Posts: 1321
Joined: Thu Nov 11, 2004 5:26 pm
Location: Kingsville, Texas

Re: MX Records Resolving to IIS

Post by rfwilliams777 » Wed Jun 29, 2016 8:49 pm

Either your DNS (probably) is not set up correctly or your bindings in IIS are not. Mine is not doing what you have.
Robert Williams, Owner
www.WWSHosting.net
#1 in MailEnable Business-Class Email Hosting - Switch to Williams Web Solutions and get your first 2 months FREE!
We can be hired to help you with your Mail Enable server, too!

netmo
Posts: 31
Joined: Mon Jun 20, 2011 7:46 pm

Re: MX Records Resolving to IIS

Post by netmo » Fri Jul 08, 2016 1:06 pm

Thanks for you reply. We've removed the default web pages from the server and now we're getting forbidden access to mx.domain.com.

Just curious if you have setup SSL Certificate for your server. We've bought a certificate for one of our domains mx.domain.com and we setup autodiscover on the server. When we use autodiscover for this domain and other domaisn on the server. The one we purchases the domain is fine, but when we do autodiscover for the non default domain, we get a certificate mismatch error. Isn't the certificate suppose to support all the domains on the maileanble server for SSL?

Garre
Posts: 32
Joined: Thu Jun 08, 2006 3:58 pm
Location: Boise, Idaho USA

Re: MX Records Resolving to IIS

Post by Garre » Fri Jul 08, 2016 4:14 pm

First you need to set your domain providers DNS MX redirect to the default name for the server, such as "mail.defaultdomain.com" Where the server name is "mail" inside Windows, and defaultdomain.com is setup as the default domain inside Mailenable. Thus the SSL certificate needs to be assigned to "mail.defaultdomain.com" as well. That way the SSL certificate will work for all your Mailenable domains.

Garre

Post Reply