• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1162
  • Last Modified:

FQDN Change Question

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.
0
chad_morris
Asked:
chad_morris
  • 3
  • 2
1 Solution
 
OneHumpCommented:
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
0
 
chad_morrisAuthor 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
0
 
OneHumpCommented:
No, that's not what I'm saying.  What I'm saying is that you can change the FQDN in SMTP VS properties.  You never ever want to change your server name.

The FQDN of your server makes little difference.  The most important components of an SMTP server are your MX and PTR records.  The MX records is used to route to your server and most servers won't take email from your server without a PTR record.

It's best to have a matching FQDN but not at all important.  Many ISPs route for hundreds of domains with a server that has a different FQDN.

Don't change your server name!!!!!   :)

OneHump
0
 
chad_morrisAuthor Commented:
PTR record nailed it!!!

Thanks a ton!!!
0
 
OneHumpCommented:
My pleasure.
0

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now