RichardPWolf
asked on
Exchange 2010 won't receive email on alternate Domain
First thanks in advance.
OK, I have two email domains. I'll call them texas.org and texas1.com. The primary domain is texas.org and mail flows normal using that. I setup an alternate accepted domain under organization-> hub transport for texas1.com as authoritive. I've setup with our domain registrar the A record and the MX record to point to the correct IP address which is also the IP address of the primary email (texas.org). When I do a test using DNS-Stuff.com I get a report that is saying there isn't an MX record. When I do a smtp test telneting to the domain name using the texas1.com it connects but when doing an ELHO it returns the texas.org name. I'm in the final stages of migrating from exhange 2003 to 2010 and everything is migrated over and I'm fixing to remove the 2k3 box. Could that have an impact?
What am I missing.
OK, I have two email domains. I'll call them texas.org and texas1.com. The primary domain is texas.org and mail flows normal using that. I setup an alternate accepted domain under organization-> hub transport for texas1.com as authoritive. I've setup with our domain registrar the A record and the MX record to point to the correct IP address which is also the IP address of the primary email (texas.org). When I do a test using DNS-Stuff.com I get a report that is saying there isn't an MX record. When I do a smtp test telneting to the domain name using the texas1.com it connects but when doing an ELHO it returns the texas.org name. I'm in the final stages of migrating from exhange 2003 to 2010 and everything is migrated over and I'm fixing to remove the 2k3 box. Could that have an impact?
What am I missing.
When you registered record? As it can take upto 72 hours to update Globally.
ASKER
Been longer than that. Did that first part of the week.
One thing, do I need to create a new send connector?
One thing, do I need to create a new send connector?
Yes, connectors are required. Check this
http://technet.microsoft.com/en-us/library/aa996314%28v=exchg.150%29.aspx
http://technet.microsoft.com/en-us/library/aa996314%28v=exchg.150%29.aspx
ASKER
OK, setup send connector but am getting confused on email policy template. The specifics are that right now I only have two users that will use the new email domain texas1.com. So I set their primary email address under there individual mailboxes. Will this work? Or do I need to setup a filtered second email policy?
You need to setup a new policy for these users.
ASKER
OK no problem. Setting up a filtered policy. All the examples I've seen show using the Company name for the filter. These users are with the same company. Can I use something else, say the OU that their in?
ASKER
OK, answered my own question about department. However creation failed because of legacy email servers detected. I'm assuming that I can't do this until I've finalized my migration to 2010 by removing the old 2k3 box.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks, I remember reading something about that.
ASKER
OK, used this command - Get-EmailAddressPolicy | where {$_.RecipientFilterType –eq “Legacy”} to find out if any policies were still legacy but it didn't return anything.
Hello,
An Email Address Policy is not required. If you only have two users who need addresses added with this new domain, you can just manually add them. If you want them set as the primary address, you will need to disable automatic email address updates on the E-mail addresses tab of these mailboxes.
Also, a new send connector is not required when you add a new authoritative domain.
If you do an nslookup on the new domain and can't find an MX record, that is your main problem. You need to go to whoever manages this domain and have them fix this issue.
JJ
An Email Address Policy is not required. If you only have two users who need addresses added with this new domain, you can just manually add them. If you want them set as the primary address, you will need to disable automatic email address updates on the E-mail addresses tab of these mailboxes.
Also, a new send connector is not required when you add a new authoritative domain.
If you do an nslookup on the new domain and can't find an MX record, that is your main problem. You need to go to whoever manages this domain and have them fix this issue.
JJ
ASKER
jjmck - that's the way I had it originally. Now I'm more confused.
This-is-the-domain-that-I.docx
This-is-the-domain-that-I.docx
ASKER
I did just add the domain name to our local DNS.
You have no MX records for texaspartners.com. You need to have whoever manages this domain set them up.
JJ
JJ
ASKER
Yes I do. I know that if using DNS-Stuff it doesn't say so but it's there. I've been on the phone with our registrar for help also.
This is a section from our domain registrar page.
NS Records
@ » NS4.PAIRNIC.COM.
@ » NS3.PAIRNIC.COM.
A Records
mail » 24.242.182.210
MX Records
mail » 1 mail.texaspartners.com.
As I mentioned in my 1st post. If you do a SMTP test using our texaspartners.com it returns texaspartnersfcu.org for HELO and EHLO. That's why I was looking back at our Exchange box.
But for verification I will call them again to test.
This is a section from our domain registrar page.
NS Records
@ » NS4.PAIRNIC.COM.
@ » NS3.PAIRNIC.COM.
A Records
mail » 24.242.182.210
MX Records
mail » 1 mail.texaspartners.com.
As I mentioned in my 1st post. If you do a SMTP test using our texaspartners.com it returns texaspartnersfcu.org for HELO and EHLO. That's why I was looking back at our Exchange box.
But for verification I will call them again to test.
No, you do not have an MX record or something isn't configured properly. I did an nslookup and no MX is returned.
The exchange server can only return one banner FQDN so what you are seeing is normal. You can't have it return a different FQDN depending on what hostname you use to connect. You can change the FQDN it uses to texaspartners.com if you want.
JJ
The exchange server can only return one banner FQDN so what you are seeing is normal. You can't have it return a different FQDN depending on what hostname you use to connect. You can change the FQDN it uses to texaspartners.com if you want.
JJ
ASKER
Did find one thing in talking to our registrar......wait for it:) Our MX record was set for a "sub"domain i.e. mail.texaspartners.com and not at the root texaspartners.com. So I've been chasing my tail trying to figure this out.
ASKER
jj - thanks for the info on the banner. As I'm going down this road I'm finding out rather quickly how much I don't know. Per my previous post I did find out what most likely is wrong. We have a TTL of 1 hour so I'll let things propagate and test again. I apologize if it sounded like I was getting a bit fiesty but I thought I had all my bases covered. Also thanks for the info on the manual settings for the users. As I said that's how I had it setup before but was getting confused by the articles.
No problem. Once the MX records show up, post back if you still have issues and we'll work through them.
JJ
JJ
ASKER
Thanks, One question about banners. In a case where I have 2 domains I thought that the SMTP query to the specific domain would return that domain as long as it was authoritive. So what I take from you is that if I had 10 authoritive domains that ALL would return the default domain banner?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks.
ASKER
Well at this time the MX record is showing up correctly. Now I'm testing the email.
ASKER
Finally it's working. Everything. It's amazing that as simple (yah right) thing like DNS would cause me about 2 months worth of sleep.
Thank you both very much. Very inlightning.
Thank you both very much. Very inlightning.
ASKER
I split the points accordingly. Both answers were great and on target but jj's was the one that solved the problem more epediantly.