At 10:01 AM -0400 07/12/2002, Neil Herber wrote: >Dale > >I know close to nothing about DNS, but what I have been trying to convince Warren in >my emails (which must sound tedious to the list) is that his problem had very little >to do with SIMS - it was just handling mail that was delivered to its IP and destined >for an IP which was also itself. > >The only way this could be true was if a DNS server somewhere mapped his client's >domain name to his server's IP number. He stated that he had removed all of the DNS >records related to this client - hence my assumption that there was a rogue DNS (his >secondary?) that was still pointing to his server.
As stated originally: I have removed the mindcorral zone from all of my name servers. There is still one secondary name server, not belonging to me, that still has the zone on it and is returning authoritative data for mindcorral lookups. Those of you who said you got responses from my own NS1 and NS2 name servers failed to note that the data you received were NOT authoritative. That means when you queried my servers, they in turn did a lookup and found data available on the one authoritative server out there -- the secondary over which I have no control. My NS1 and NS2 boxes are QuickDNS Pro running on Mac OS and there is no way I can turn off recursive lookups or limit the range of clients who are able to do (recursive) lookups through my server. You could do a lookup through my servers on microsoft.com and get a response, but that doesn't make me Bill Gates. I have done all I can DNS-wise to remove mindcorral.com. The domain owner is also the administrator of those domains through his registrar and I have never had the ability to modify the listed domain name servers for his domains -- so I cannot even remove my name servers from the list of authoritative hosts for his domains. At this point, I don't care if I can stop the incoming mail for this domain. Right now I'm just highly curious as to why this is happening. I've stepped up my logging again so as to catch, in more detail, what happens when this mail comes in. I'd like to have a better understanding of both SIMS and SMTP so I'll let things run as-is for a while until the answer is clear. It has been speculated that because mindcorral.com resolves to the same IP address as my SIMS server, this accounts for why SIMS thinks mindcorral.com is a local client, despite there being no router entries. I've seen no indication that SIMS does a DNS lookup on the recipient domain (mindcorral.com) to determine this. Perhaps my stepped up logging will show that this actually occurs. If so, I'll have had my curiosity satisfied and learned a bit more about SIMS. Perhaps I should modify my original question too. In light of what detailed logs show -- that a bounce message is sent, and in light of the fact that when I send (through another MTA, not my SIMS box) to a former account at mindcorral.com, I get: Final-Recipient: rfc822; [EMAIL PROTECTED] Action: failed Status: 5.0.0 It's pretty clear that SIMS *is* generating bounces -- which is just what I wanted it to do. So I guess my question should be modified to: Once a bounce message is sent, why does SIMS keep all this undeliverable mail in my queue? The answer is probably, "So the postmaster will know what's going on." Eh? -- "President Bush said the 9-11 terror strikes were an attack on our freedoms. "John Ashcroft has decided that it's better to destroy those freedoms than to leave them exposed as such an easy target." - Pauly & Maury, Weakly Politics newsletter ############################################################# 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]>
