At 9:58 AM -0600 2/20/02, Joe Laffey imposed structure on a stream of electrons, yielding: >On Wed, 20 Feb 2002, Kevin Windham wrote: > >> It looks like the DNS Resolver is having a problem getting an MX record >> for the domain fkphoto.com. The problem also occurs for me when I run a >> lookup from here. I think you need to check your DNS. > >See previous email about this being unlikely (tested).
Your pubns2 tells me there is an A record but no MX record for mail.fkphoto.com. >I think this must be some other problem. Other mailservers can send mail >to that domain fine. It is only that one server that is reporting the >error. Why would the error get reported at the SMTP level anyway? The >foreign mailserver has obviously found my relay if it is connecting to it! It looks like this may be a non-problem and you have to look elsewhere. I think SIMS will report that error whenever there is no MX for the domain part of incoming mail, even though it might proceed to find and use an A record. Was mail actually rejected? If you are going to have mail aimed at [EMAIL PROTECTED], you can make it work a little better by making sure mail.fkphoto.com has an MX record. Everything that handles mail will look for the MX first before backing off to use the A record, and it is technically acceptable for a machine to simply refuse to handle mail aimed at addresses whose domain-part has no MX. >I wonder if that message is coming from the other server or what. I know I >have that domain setup to ignore blacklisting (in theory): ><*%fkphoto.com@blacklisted>=fk-* ><*@fkphoto.com>=fk-* >Maybe that is it. I will remove the first line... Note that those lines will have no effect on mail aimed at [EMAIL PROTECTED] addresses. The log line implied to me that someone was trying to send mail to such an address. The subtext of this is that there is no magic in 2-level domains. Setting up DNS records and SIMS routing for foo.tld doesn't do anything about bar.foo.tld and that is absolutely correct behavior. Outside of the .com zone, there are many name hierarchies where the most common real differentiation is at the third level or higher, so it would be foolish for any software to impose an assumption about 2-level domains on how names work. -- Bill Cole [EMAIL PROTECTED] ############################################################# This message is sent to you because you are subscribed to the mailing list <[EMAIL PROTECTED]>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
