Exchange 2010 FQDN when telnet port 25

Posted on 2011-04-22
Last Modified: 2012-05-11
I am migrating from Ex2003.  In Ex2003 I remember changing the FQDN that was presented when I would telnet to port 25 on the local box. I created a reverse pointer record in DNS that matched the name present in my banner header.
In other words I would telnet to port 25 and it would come back Then I created a reverse PTR record in DNS to point back to the IP of my mail server. This was needed because certain mail servers would not accept mail until I did it.
I am having problems doing this in Exchange 2010. I go to Server Config->Hub Transport-> Receive Connectors.  I am not able to put in my FQDN into the Default Connector. The only name it will accept is my local AD domain name (ie  exchange2010.myserver.lcl).  Since this is not a FQDN, how do I enter one in to keep the other mail servers on the net happy?
Hope I was clear on this.

Question by:nachtmsk
    LVL 10

    Expert Comment

    Will you please clearify your needs, as far as I understood your problem you wanted to start your mails from exchange 2010,for this you don't need to modify your default connectors for exchange 2003 bcoz there is an routing group connector automatically been created at the time of coexistance with exchange 2003 and this will start your mail flow from exchange 2010.
    LVL 3

    Expert Comment

    If you are reffering to the reverse DNS lookup then you need to publish/Set at your ISP level, not your local DNS level.. get in touch with your ISP for that
    LVL 1

    Expert Comment

    I'm sorry, I guess I wasn't clear. I don't know the correct terminology. So I will explain better.
    I have an Exchange 2010 server. I DID have an Exchange 2003 server but I am taking that offline. I am talking about my Exchange 2010 server and how it communicates with other EXTERNAL servers when making an SMTP connection.

    More specifically:
    When a mail server connects to another external mail server it often checks what the HELO FQDN name is. You can test what this is by doing a telnet localhost 25. The FQDN that is brought back is what other mail servers will see. This FQDN that is brought back needs to have a reverse pointer entered into DNS of the local ISP (or server provider as in my case: Rackspace). If the FQDN reported by the server in the HELO banner isn't the same as the reverse pointer DN, then the other mail server sometimes will reject the mail.
    In Ex2003 it was easy to change what the FQDN was that was reported by the current mail server. All I had to do was going into the SMTP connector and change the name.
    In Ex2010 though it doesn't seem to easy. The Receive connectors for Ex2010 have the FQDN as the local AD domain name (in my case mydomainame.lcl) and it's not possible to alter this to the external domain name (
    So my question is, how to I change the FQDN in the HELO on my Ex2010 server that is received by other mail servers trying to make a connection to my server?

    Hope that explains it better.
    LVL 12

    Expert Comment

    did you try to do telnet to port 25 from command prompt,
    if yes and the connection is closed after that, maybe it is because POP3 is a feature that can be set to every mailbox,
    LVL 1

    Expert Comment

    This doesn't have anything to do with POP3. This has to do with setting up a reverse DNS pointer record in Exchange 2010 and the response that is sent to other mail servers when they issue an HELO command.
    LVL 23

    Accepted Solution

    from organisation configuration, hub transport -->"send  connector" properties -->change FQDN.


    Featured Post

    How to run any project with ease

    Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
    - Combine task lists, docs, spreadsheets, and chat in one
    - View and edit from mobile/offline
    - Cut down on emails

    Join & Write a Comment

    Create high volume marketing opportunities using email signatures with these top 10 DOs and DON'Ts of email signature marketing.
    Find out how to use Active Directory data for email signature management in Microsoft Exchange and Office 365.
    In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…
    To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…

    732 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

    18 Experts available now in Live!

    Get 1:1 Help Now