Question Locked

Do you attach the port number to DNS fowarded

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I just wanted to make sure I didn't forget a step. I opened the email and pop3 ports on the firewall. I updated the DNS with the firewalls IP. Should I have added the port number to the end of the IP in DNS?

I am a bit new to DNS

9 replies

by jgreer

We are just installing a new Exchange server. So I opened up the ports on the firewall and have them forwarded to the server. My concern is the MX Records. Currently I have them configured to just the firewall IP.

by choppit

So assuming you've forwarded TCP port 25 on your public interface to TCP 25 on your exchange server. Your MX needs to point to your public firewall IP.

by jgreer

Which is what I have done = However, no email today. Tests failed.

When I send to the firewall's IP I am receiving:
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 550 550 5.7.1 Unable to relay for myname@firewallsip

by dumphrey

to act as a relay to send mail to another domain. Its a generic Exchange error for mis configured access controls usually.
Check your authentication and Recipient Policies, and that you have one for the domain in question defining its email address. But, in spite of what the server error said, its NOT a relay issue, so please leave the relay tab alone unless you want to be the next spam king....

by jgreer

So far I have been informed by Covad that they corrupted a dns update. So we are having to wait. I hope its that simple.

by choppit

Assuming you're using windows, to check your mx record(s);

From the command prompt

nslookup
>set q=mx
>insert your domain name here

by dumphrey

No DNS == No mail flat and simple. its the first link in the chain.

This discussion is closed to new replies.