We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

FQDN Change Question

chad_morris
chad_morris asked
on
Medium Priority
1,202 Views
Last Modified: 2009-12-16
This may seem like a silly question but I am new to Exchange for the most part so...  

It is my understanding that the FQDN can be changed in the Virtual SMTP Server Properties under the Advanced Delivery dialogue box.  I have the Exchange Server registered in external DNS as mail.domain.com.  We had someone set the server up for us as we did not posess the knowledge to do it ourselves at the time.  The problem is that the FQDN is set to our internal DNS settings.  (eg. ServerName.Domain.Local)

Now that more and more admin's are filtering mail by performing a reverse DNS lookup we are running into issues naturally.  My question is:

Will this cause a problem if I change the FQDN to the externally registered DNS name?  (eg. mail.domain.com)

Is this the correct way to fix this problem to begin with?

Thanks in advance for any response.
Comment
Watch Question

Commented:
I answered this in the other thread.  You can change it, no problem.  It doesnt make a huge amount of difference, but the right thing to do would be to change it.  Check the other thread for more details.  :)

OneHump

Author

Commented:
So you are saying that the proper way to change the FQDN would be to change the server name?

Would that cause any problems with my fully functioning Exchange 2000 Server?

The server is not a domain controller so we wouldn't have any problems there.  Basically we are having problems with a couple small clients that are doing a reverse DNS lookup on the mail server and rejecting our mail in an effort to mitigate SPAM from private IP addresses.  I just want to nail this down prior to having a large client having issues receiving mail from us.

At this point I partially agree with you when you say no biggie because the majority don't seem to be performing these lookups, but it is inevitable that there will be a large client that is performing a reverse DNS lookup to thwart SPAM and it will then be a major problem for us.

In re-reading your post on the other thread I am getting that it makes no difference if I change the FQDN to the external DNS.  Correct me if I am wrong.

Basically, if I change the FQDN in the Virtual SMTP Server Properties under the Advanced Delivery dialogue box to mail.domain.com which is registerd in the external DNS will that resolve the problem with the remote mail servers rejecting messages?

Again,

Thanks in advance for any information you can provide!!!

Chad
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Author

Commented:
PTR record nailed it!!!

Thanks a ton!!!

Commented:
My pleasure.
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.