Re: Can't find DNS for domain when domain does exist
JWM wrote: Stefano, I really appreciate your help in this ordeal. I copied your response to Register. According them, RFCs are now simply 'suggestions'... Is that true? I thought they were already mandatory. Hi JWM, I just wrote a unittest for the current James trunk to test the scenario and it seems that James trunk already correctly resolve this mx server. I'm not able to run the test against 2.2.0 right now. Are you able to run a test using 2.3.0a1 or a recent nightly build? Stefano JWM wrote: Stefano, The domain in question is: brandilyncollins.com # host -t mx brandilyncollins.com brandilyncollins.com mail is handled by 0 mxmail.register.com. # host -t a mxmail.register.com. mxmail.register.com is an alias for rcom-outblaze-com.mr.outblaze.com. rcom-outblaze-com.mr.outblaze.com has address 205.158.62.41 rcom-outblaze-com.mr.outblaze.com has address 205.158.62.200 rcom-outblaze-com.mr.outblaze.com has address 205.158.62.206 rcom-outblaze-com.mr.outblaze.com has address 205.158.62.207 rcom-outblaze-com.mr.outblaze.com has address 205.158.62.229 rcom-outblaze-com.mr.outblaze.com has address 205.158.62.230 So, it is clear that the mx host name for brandilyncollins.com does not have A or RR but instead it only provide a CNAME. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Can't find DNS for domain when domain does exist
Stefano, I am currently running 2.2.0a17. I have no problem installing 2.3.0a1 and testing. But can you tell me if I have to make changes to my config file in order to upgrade? If so, is it massive? I seem to remember that I had significant amount of changes required when I moved up to where I am now. I'd love to move up and test it (and hopefully solve the problem). But I don't have the bandwidth to do a major migration. Will everything still work as-is on the new version? Thx for continuing to pursue this. JWM -Original Message- From: Stefano Bagnara [mailto:[EMAIL PROTECTED] Sent: Thursday, March 02, 2006 3:03 PM To: James Users List Subject: Re: Can't find DNS for domain when domain does exist JWM wrote: Stefano, I really appreciate your help in this ordeal. I copied your response to Register. According them, RFCs are now simply 'suggestions'... Is that true? I thought they were already mandatory. Hi JWM, I just wrote a unittest for the current James trunk to test the scenario and it seems that James trunk already correctly resolve this mx server. I'm not able to run the test against 2.2.0 right now. Are you able to run a test using 2.3.0a1 or a recent nightly build? Stefano JWM wrote: Stefano, The domain in question is: brandilyncollins.com # host -t mx brandilyncollins.com brandilyncollins.com mail is handled by 0 mxmail.register.com. # host -t a mxmail.register.com. mxmail.register.com is an alias for rcom-outblaze-com.mr.outblaze.com. rcom-outblaze-com.mr.outblaze.com has address 205.158.62.41 rcom-outblaze-com.mr.outblaze.com has address 205.158.62.200 rcom-outblaze-com.mr.outblaze.com has address 205.158.62.206 rcom-outblaze-com.mr.outblaze.com has address 205.158.62.207 rcom-outblaze-com.mr.outblaze.com has address 205.158.62.229 rcom-outblaze-com.mr.outblaze.com has address 205.158.62.230 So, it is clear that the mx host name for brandilyncollins.com does not have A or RR but instead it only provide a CNAME. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can't find DNS for domain when domain does exist
JWM wrote: Stefano, The domain in question is: brandilyncollins.com # host -t mx brandilyncollins.com brandilyncollins.com mail is handled by 0 mxmail.register.com. # host -t a mxmail.register.com. mxmail.register.com is an alias for rcom-outblaze-com.mr.outblaze.com. rcom-outblaze-com.mr.outblaze.com has address 205.158.62.41 rcom-outblaze-com.mr.outblaze.com has address 205.158.62.200 rcom-outblaze-com.mr.outblaze.com has address 205.158.62.206 rcom-outblaze-com.mr.outblaze.com has address 205.158.62.207 rcom-outblaze-com.mr.outblaze.com has address 205.158.62.229 rcom-outblaze-com.mr.outblaze.com has address 205.158.62.230 So, it is clear that the mx host name for brandilyncollins.com does not have A or RR but instead it only provide a CNAME. The specification is REALLY clear about this, you can see that they provided a full paragraph to say that an hostname used as MX record must NEVER be a CNAME (alias) RFC2181 10.3: Thus, if an alias is used as the value of an NS or MX record, no address will be returned with the NS or MX value.. If I understand correctly, supporting the CNAME for the MX would be AGAINST the rfc. So the problem is that RFC is extremely clear but Sendmail, postfix, qmail, and exim, all support the aliased MXs. We could consider to add this option to James, too, but don't expect to happen soon. The Register is not RFC compliant, so they are not providing a compliant DNS service, and you should complain again. I added an improvement request in our issue tracker to remember this issue. Stefano --- here is the full 10.3 paragraph from rfc2181 (Clarifications to the DNS Specification) 10.3. MX and NS records The domain name used as the value of a NS resource record, or part of the value of a MX resource record must not be an alias. Not only is the specification clear on this point, but using an alias in either of these positions neither works as well as might be hoped, nor well fulfills the ambition that may have led to this approach. This domain name must have as its value one or more address records. Currently those will be A records, however in the future other record types giving addressing information may be acceptable. It can also have other RRs, but never a CNAME RR. Searching for either NS or MX records causes additional section processing in which address records associated with the value of the record sought are appended to the answer. This helps avoid needless extra queries that are easily anticipated when the first was made. Additional section processing does not include CNAME records, let alone the address records that may be associated with the canonical name derived from the alias. Thus, if an alias is used as the value of an NS or MX record, no address will be returned with the NS or MX value. This can cause extra queries, and extra network burden, on every query. It is trivial for the DNS administrator to avoid this by resolving the alias and placing the canonical name directly in the affected record just once when it is updated or installed. In some particular hard cases the lack of the additional section address records in the results of a NS lookup can cause the request to fail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Can't find DNS for domain when domain does exist
Stefano, I really appreciate your help in this ordeal. I copied your response to Register. According them, RFCs are now simply 'suggestions'... Is that true? I thought they were already mandatory. The one thing that is still nagging at me is the fact that James is widely used, and Register.com is not exactly a tiny outfit. Yet I'm the only person in the world having this problem (). According to what everyone has said, it would seem EVERY instance of James in the world sending mail to any domain hosted by Register.com would have the same problem. I don't see it. I don't know any other domains offhand that are hosted by Register. I'd love to find out that other mx records are actually correct at Register. In the meantime, apparently two wrongs will have to make a right. If you could consider adding the incorrect implementation to deal with screwups like Register, I'd appreciate it. Here is their response... I give up = Thank you for contacting Register.com. We understand your position, and sincerely apologize for any inconvenience this may cause. However, as the email from apache stated, many services support the aliased mx records we are currently using as the RFCs are still suggested practices. Until such time that the RFC guidelines become mandatory, our email services will remain in the manner they are currently configured for our customers. You can disable the cname check on your end to have the emails send/receive properly, however we do not have plans to make changes to our mx records at this time. -Original Message- From: Stefano Bagnara [mailto:[EMAIL PROTECTED] Sent: Friday, February 03, 2006 3:16 AM To: James Users List Subject: Re: Can't find DNS for domain when domain does exist JWM wrote: Stefano, The domain in question is: brandilyncollins.com # host -t mx brandilyncollins.com brandilyncollins.com mail is handled by 0 mxmail.register.com. # host -t a mxmail.register.com. mxmail.register.com is an alias for rcom-outblaze-com.mr.outblaze.com. rcom-outblaze-com.mr.outblaze.com has address 205.158.62.41 rcom-outblaze-com.mr.outblaze.com has address 205.158.62.200 rcom-outblaze-com.mr.outblaze.com has address 205.158.62.206 rcom-outblaze-com.mr.outblaze.com has address 205.158.62.207 rcom-outblaze-com.mr.outblaze.com has address 205.158.62.229 rcom-outblaze-com.mr.outblaze.com has address 205.158.62.230 So, it is clear that the mx host name for brandilyncollins.com does not have A or RR but instead it only provide a CNAME. The specification is REALLY clear about this, you can see that they provided a full paragraph to say that an hostname used as MX record must NEVER be a CNAME (alias) RFC2181 10.3: Thus, if an alias is used as the value of an NS or MX record, no address will be returned with the NS or MX value.. If I understand correctly, supporting the CNAME for the MX would be AGAINST the rfc. So the problem is that RFC is extremely clear but Sendmail, postfix, qmail, and exim, all support the aliased MXs. We could consider to add this option to James, too, but don't expect to happen soon. The Register is not RFC compliant, so they are not providing a compliant DNS service, and you should complain again. I added an improvement request in our issue tracker to remember this issue. Stefano --- here is the full 10.3 paragraph from rfc2181 (Clarifications to the DNS Specification) 10.3. MX and NS records The domain name used as the value of a NS resource record, or part of the value of a MX resource record must not be an alias. Not only is the specification clear on this point, but using an alias in either of these positions neither works as well as might be hoped, nor well fulfills the ambition that may have led to this approach. This domain name must have as its value one or more address records. Currently those will be A records, however in the future other record types giving addressing information may be acceptable. It can also have other RRs, but never a CNAME RR. Searching for either NS or MX records causes additional section processing in which address records associated with the value of the record sought are appended to the answer. This helps avoid needless extra queries that are easily anticipated when the first was made. Additional section processing does not include CNAME records, let alone the address records that may be associated with the canonical name derived from the alias. Thus, if an alias is used as the value of an NS or MX record, no address will be returned with the NS or MX value. This can cause extra queries, and extra network burden, on every query. It is trivial for the DNS administrator to avoid this by resolving the alias and placing the canonical name directly in the affected record just once when it is updated or installed. In some particular hard cases the lack of the additional section address records in the results of a NS lookup can cause
Re: Can't find DNS for domain when domain does exist
Jerry Malcolm wrote: I'm getting a bounce when trying to send mail to a valid domain. I get an error in the log that says it can't find the dns entry. The dns entry is clearly there when I do an nslookup. However, I went to dnsreport.com and got the following error when it analyzed the DNS for the domain: === FAIL MX A lookups have no CNAMEs WARNING: One or more of your MX records points to a CNAME. CNAMEs are prohibited in MX records, according to RFC974, RFC1034 3.6.2, RFC1912 2.4, and RFC2181 10.3. The problem MX record(s) are: mxmail.register.com.-rcom-outblaze-com.mr.outblaze.com.-205.158.62.206 === OK, seems pretty obvious that there's something wrong with the DNS. But is this what's causing James to be unable to send the mail? Even if the error I would say yes: DNS is the routing information for the mail systems. If it's wrong mail systems will not deliver messages. The only bug I found in James about DNS handling is described here: http://issues.apache.org/jira/browse/JAMES-413 If this is your case then it's fixed in the current trunk. Many MTA will follow the CNAME anyway, but this is an unsupported behaviour and not standard. They should fix their MX. Send the dnsreport result to the bad domain owner and let him know he's loosing mail because of this misconfiguration and he will be happy to ask his provider to fix this. Stefano is with the destination, my customer tells me other people have no problem emailing this person. So the question is, how can make James not be so overly sensitive to this problem? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Can't find DNS for domain when domain does exist
Stephano, Thanks. That appears to be the situation. Does this fix that you reference make james follow a cname in the mx record even though it's an unsupported behaviour? (i.e. make james work despite the error?) Is there any way to patch this fix into my existing installation of James (e.g. replace one jar file, etc), or do I need to do a complete reinstall of the latest version? I just don't have the bandwidth in my schedule now to risk a massive upgrade. Thanks for the info. Jerry -Original Message- From: Stefano Bagnara [mailto:[EMAIL PROTECTED] Sent: Thursday, January 26, 2006 3:18 AM To: James Users List Subject: Re: Can't find DNS for domain when domain does exist Jerry Malcolm wrote: I'm getting a bounce when trying to send mail to a valid domain. I get an error in the log that says it can't find the dns entry. The dns entry is clearly there when I do an nslookup. However, I went to dnsreport.com and got the following error when it analyzed the DNS for the domain: === FAIL MX A lookups have no CNAMEs WARNING: One or more of your MX records points to a CNAME. CNAMEs are prohibited in MX records, according to RFC974, RFC1034 3.6.2, RFC1912 2.4, and RFC2181 10.3. The problem MX record(s) are: mxmail.register.com.-rcom-outblaze-com.mr.outblaze.com.-205.158.62.206 === OK, seems pretty obvious that there's something wrong with the DNS. But is this what's causing James to be unable to send the mail? Even if the error I would say yes: DNS is the routing information for the mail systems. If it's wrong mail systems will not deliver messages. The only bug I found in James about DNS handling is described here: http://issues.apache.org/jira/browse/JAMES-413 If this is your case then it's fixed in the current trunk. Many MTA will follow the CNAME anyway, but this is an unsupported behaviour and not standard. They should fix their MX. Send the dnsreport result to the bad domain owner and let him know he's loosing mail because of this misconfiguration and he will be happy to ask his provider to fix this. Stefano is with the destination, my customer tells me other people have no problem emailing this person. So the question is, how can make James not be so overly sensitive to this problem? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can't find DNS for domain when domain does exist
JWM wrote: Stephano, Thanks. That appears to be the situation. Does this fix that you reference make james follow a cname in the mx record even though it's an unsupported behaviour? (i.e. make james work despite the error?) No. The fix contains the reference to the behaviour that was not implemented in James. The problem fixed was that a host name does not have an MX name associated but it has a CNAME address associated. A compliant SMTP server should resolve the CNAME and ask the MX servers for the CNAME host. That was a COMPLIANCE fix, I don't think it is the same of your case (not as you described it) but I pointed to it because it is the only issue reported against James MX resolution. I think we shouldn't fix the issue you are describing because James seems to be compliant and the dnsreport site confirms that the destination domain dns is bad. The fix for your problem is to write to the DNS mantainer for that domain, attaching the dnsreport response. Stefano Is there any way to patch this fix into my existing installation of James (e.g. replace one jar file, etc), or do I need to do a complete reinstall of the latest version? I just don't have the bandwidth in my schedule now to risk a massive upgrade. Thanks for the info. Jerry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Can't find DNS for domain when domain does exist
I'm getting a bounce when trying to send mail to a valid domain. I get an error in the log that says it can't find the dns entry. The dns entry is clearly there when I do an nslookup. However, I went to dnsreport.com and got the following error when it analyzed the DNS for the domain: === FAIL MX A lookups have no CNAMEs WARNING: One or more of your MX records points to a CNAME. CNAMEs are prohibited in MX records, according to RFC974, RFC1034 3.6.2, RFC1912 2.4, and RFC2181 10.3. The problem MX record(s) are: mxmail.register.com.-rcom-outblaze-com.mr.outblaze.com.-205.158.62.206 === OK, seems pretty obvious that there's something wrong with the DNS. But is this what's causing James to be unable to send the mail? Even if the error is with the destination, my customer tells me other people have no problem emailing this person. So the question is, how can make James not be so overly sensitive to this problem? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
