Solved

DNS question for a brand new 2003 server running exchange.

Posted on 2004-09-23
2
145 Views
Last Modified: 2010-04-19
I just setup a new windows 2003 server. I installed the basic server plus IIS and exchange. It is running on a dsl line with a static ip through a linksys router. I setup port forwarding for all of the ports I am going to need. When I login to godaddy the first thing I did was setup domain forwarding through their wizard. I set the domain to point to the static ip. This worked great and when you type in the domain the website comes up. Next I loaded up their mx wizard. the only options it gives me are to add a mx record and then specify a server for it. I put in the static ip of the server and set it as the first mx record. Now when I send mail to one of the accounts I created I get this error - PERM_FAILURE: SMTP Error (state 10): 550 5.7.1 Unable to relay

I can login to exchange from the webclient and send mail but I cannot receive mail. I have never setup dns before and when I look at the dns settings on the server the records point to 192.168.0.157 which is the local static ip I have setup that the router forwards to. I assume that the dns is correct because the website loads fine its just the mail that doesnt work. I can enter an advanced mode on the godaddy page for setting my DNS where I can change all the records. If someone can help me out I would be much appreciative.
0
Comment
Question by:dfluxnet
2 Comments
 

Accepted Solution

by:
j0hnhawk earned 500 total points
ID: 12156687
http://support.microsoft.com/servicedesks/webcasts/wc011801/wcblurb011801.asp

I know this is windows 2000 but a good coverage for basic understanding of Internet Mail with Exchange.

One thing to do is to verify connectivity from the Internet into your smtp relay

Take the dns record of your MX for your domain which should be pointing to your linksys routers ip.

then do a telnet [domainnameOfMXRecord] 25

You should get  a response on port 25 then type helo domain

If this works, it means your relay is available to Internet users.
0
 

Author Comment

by:dfluxnet
ID: 12156798
Thanks for the info. It turned out that the DNS had not updated yet and that was the reason for the problems but the info you provide is very helpful and I will use in the future.
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Join & Write a Comment

by Batuhan Cetin In this article I will be guiding through the process of removing a failed DC metadata from Active Directory (hereafter, AD) using the ntdsutil tool in a Windows Server 2003 environment. These steps are not necessary in a Win…
On July 14th 2015, Windows Server 2003 will become End of Support, leaving hundreds of thousands of servers around the world that still run this 12 year old operating system vulnerable and potentially out of compliance in many organisations around t…
This demo shows you how to set up the containerized NetScaler CPX with NetScaler Management and Analytics System in a non-routable Mesos/Marathon environment for use with Micro-Services applications.
This video shows how to remove a single email address from the Outlook 2010 Auto Suggestion memory. NOTE: For Outlook 2016 and 2013 perform the exact same steps. Open a new email: Click the New email button in Outlook. Start typing the address: …

759 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now