Andrew Pollack's Blog

Technology, Family, Entertainment, Politics, and Random Noise

Here is an obscure mail routing problem I ran into - and the solution

By Andrew Pollack on 10/28/2011 at 05:47 PM EDT

Problem:

Some mail servers are unable to route to #######@subdomain.domain.com

In this environment, the Windows based Domino servers were affected, but the Linux based Domino servers were not. It turns out that the affected servers are those running Microsoft Windows server operating systems, and of those, only those sites where the local dns domain use a "default" address for misspelled or incorrect server names within the domain. In other words, those where typing wwww.domain.com would work just as well as www or even noplace.domain.com. It's a valid configuration, but not used in all cases.

Cause:

The remote site does not have an "MX" (mail exchange) record in their DNS configuration for "subdomain.domain.com".

The Microsoft Windows DNS client lookups use a non-standard approach to name resolution. If a host name is not found exactly as requested, the Microsoft Windows server or workstation attempts to find the server as if it were in the local domain by adding the local domain name to the server named being looked up. That's a fine approach when you're looking for a server address in general, but NOT when you're looking for MX records. This is because it skips a step. First it looks for the MX record for subdomain.domain.com. When it fails to find that, what it should do, is look for ANY record for that address as specified. Since a CNAME or an Address record does exist, that IP address should be used. Instead, the Microsoft DNS server skips that and immediately goes looking for a record for "subdomain.domain.com.localdomain.com". If "localdomain.com" is using a wildcard default to return misspelled requests to their web server, even though that is NOT an MX record, that address will be returned to the application making the DNS request.

In other words, in the lack of a valid MX record which is an exact match for the request, the Microsoft DNS resolver will return a NON-MX answer that it created itself by adding the local domain to the request AHEAD of a NON-MX record which is an exact match for the request. This clearly backwards -- but not something that Microsoft will likely change, given that they've done it that way for 15 years or so.

A walk through example:

Sending mail from "mydomain.com" to "subdomain.yourdomain.com"

1. The Windows based Mail server attempts to send a message to "user@subdomain.yourdomain.com"
2. The Mail servers does a DNS lookup for the MX record for "subdomain.yourdomain.com"
3. No MX record exists for "subdomain.yourdomain.com"
4. Microsoft DNS skips doing a lookup to find a NON-MX (A or CNAME) record for "subdomain.yourdomain.com"
5. Microsoft DNS changes the lookup to find a record for "subdomain.yourdomain.com.mydomain.com"
6. Sites with default (or wildcard) DNS entries in their domain return that default value in this case (e.g. www.mydomain.com)
7. The Microsoft DNS never goes back to check for a NON-MX record that exactly matches "subdomain.yourdomain.com"
8. The mail server attempts to send the message to the invalid address returned for subdomain.yourdomain.com.mydomain.com" and the message fails.
9. Mail isn't delivered.

The behavior is incorrect on the part of the Microsoft server, but that's not going to change any time soon -- it's been the case for nearly 15 years.

What I've done to work around this issue:

Within my own domain, I've had to set up a fake CNAME entry which actually resolves as "subdomain.yourdomain.com.mydomain.com" and points to the address of the other server "subdomain.yourdomain.com.". This way, when Microsoft does the wrong thing, it gets a workable result -- so the mail goes through.

Obviously what I've done is a wierd workaround and not something that most site admins will be willing (or frankly able) to do.

What the remote side must do to really fix this issue

This issue is probably affecting other people trying to send mail. They would likely be failing, but since they don't have any access to the person who manages their mail servers or those people aren't willing or able to track down an obscure issue like this, those users are simply unable to make it work.

The remote side can resolve this issue, by asking whoever manages their DNS to create a valid MX record for "subdomain.yourdomain.com" If they are using a unix or linux based dns server, it will look something like this:
; ------------------------------------------------------------------------------------------------------------------------------------------------------------
subdomain.yourdomain.com. IN MX 100 123.123.123.123
; ------------------------------------------------------------------------------------------------------------------------------------------------------------


There are  - loading -  comments....

re: Here is an obscure mail routing problem I ran into - and the solutionBy Devin Olson on 10/29/2011 at 08:51 AM EDT
Excellent detective work and analysis. Thanks!


Other Recent Stories...

  1. 05/05/2016Is the growing social-sourced economy the modern back door into socialism?Is the growing social-sourced economy the modern back door into socialism? I read a really insightful post a couple of days ago that suggested the use of social network funding sites like “Go Fund Me” and “Kickstarter” have come about and gained popularity in part because the existing economy in no longer serving its purpose for anyone who isn’t already wealthy. Have the traditional ways to get new ventures funded become closed to all but a few who aren’t already connected to them and so onerous as to make ...... 
  2. 04/20/2016Want to be whitelisted? Here are some sensible rules for web site advertisingAn increasing number of websites are now detecting when users have ad-blocking enabled, and refuse to show content unless you "whitelist" their site (disable your ad-blocking for them). I think that is a fair decision on their part, it's how they pay for the site. However, if you want me (and many others) to white list your site, there are some rules you should follow. If you violate these rules, I won't whitelist your site, I'll just find content elsewhere. 1. The total space taken up by advertisements ...... 
  3. 12/30/2015Fantastic new series on Syfy called “The Expanse” – for people who love traditional science fiction[] “The Expanse” is a new science fiction series being broadcast onthe Syfy channelthis winter. It’s closely based on a series of books by author James S. A. Corey beginning with “Leviathan Wakes”. There are 5 books in the “Expanse” series so far. If you’re a fan of the novels you’ll appreciate how closely the books are followed.TIP: The first five episodes are already available on Syfy.com. If you’re having trouble getting into the characters and plot, use those to get up to speed.The worlds created for ...... 
  4. 10/20/2015My suggestion is to stay away from PayAnywhere(dot)com  
  5. 08/07/2015Here is one for you VMWARE gurus - particularly if you run ESXi without fancy drive arrays 
  6. 08/06/2015The Killer of Orphans (Orphan Documents) 
  7. 06/02/2015Homeopathic Marketing: Traveler on my Android is now calling itself VERSE. Allow me to translate that for the IBM Notes community... 
  8. 03/17/2015A review of British Airways Premium Economy Service – How to destroy customer goodwill all at once 
  9. 02/26/2015There's a bug in how @TextToTime() and @ToTime() process date strings related to international standards and browser settings. 
  10. 01/21/2015Delivering two new presentations at Developer Camp (EntwicklerCamp) 2015 in Germany 
Click here for more articles.....


pen icon Comment Entry
Subject
Your Name
Homepage
*Your Email
* Your email address is required, but not displayed.
 
Your thoughts....
 
Remember Me  

Please wait while your document is saved.