MX Record Hosting Issues

We currently are running Exchange 2003 inside of our domain.  However, we do not host our domain name for our email address (  We have our web host point our MX record to our Exchange server.  We are having our 2nd major issue with our web host and not being able to receive email.

What can I do about this?  We are using as our web host.  Should we allow our web host to host that MX record?  Do we have to?  What are alternatives to this (and yes, saying get a better web host is an acceptable answer)?
Who is Participating?
Rajith EnchiparambilConnect With a Mentor Office 365 & Exchange ArchitectCommented:
Normally most of the companies gives you a control panel to manage your own records, some are still old fashioned and will ask you to give any changes in writing. Hosts won't change your records, if fact they won't touch it.

If yours is one that keeps on changing the records, you need to move it to a different company like (for home/small companies, they give you a control panel).

Google and you will find many hosts.

Rajith EnchiparambilOffice 365 & Exchange ArchitectCommented:
You need someone to host your MX record, some company where you register your domain. And as you say, it is pointing to your exchange server (public ip address). SO, what is your probem?
>>You need someone to host your MX record, some company where you register your domain.

Not true. You can always host your own publc DNS records so you don't have to rely on someone else to make changes. I have done it before. Your registrar will just foward DNS entries to whichever public IP address you tell them to and you host DNS on that server's IP. Nothing to it really.

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

set up a dns server
go to or whoever your local registar is
and point the NS records to your dns server

thus taking control of your own domain...
r270baAuthor Commented:
I already have it hosted.  My problem is that the host does not allow me to manage it.  Therefore, if they run some script that changes, I am handcuffed to having them fix it.
CuteadderConnect With a Mentor Commented:
They do not allow you to manage it?

People like Nominet are the actual registar - all domains are registered with them even if you bought the domain off some third party. You can't go much higher than that.

Plus if you have a spare server already on 24/7 then put dns server on it and host your own Name Server, forget manage it, you will have complete control and it won't even touch your "host"

The internet and it's services are meant to work around you, not you be controlled by it!
mikeleebrlaConnect With a Mentor Commented:
>>I already have it hosted.  My problem is that the host does not allow me to manage it.
we understand that, but your current situation isn't working for you. Thus your question here.
that is why I (and others) suggested hosting your own. It's very simple to do and then you will have full control and can make changes whenever you want to.

Another alternative would be to switch your hosting company to one that actually does their job. Remember, they work for you, not the other way around. I personally use network solutions  for all my DNS registering and hosting needs.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.