Hi, I just now did an nslookup mail.bcwebhost.net on each of our DNS servers, including the now no longer used ns1.xname.org. They all, even that last one, gave the correct IP address of .200. My observations about ns1.xname.org from last week was that sometimes it had the right serial number and sometimes not. I got the impression that someone was reloading it with old records, possibly due to hardware crashing. Anyway, we no longer use that server.
So what is the extra complexity that you think we have in our DNS configuration? I wasn't intending to make anything complicated. I have the MX records pointing to A record mail, which points to the .200 IP address. I also have a second A I record mail1 pointing to the same IP. I don't see why any of this should be a problem? Also, did you understand the Comcast guy's reference to subdomain? I know an address such as mail.bcwebhost.net can be a host or a subdomain, but I didn't consider the two phrases to be synonymous. And we don't have any subdomains. Thanks, Ben -----Original Message----- From: SM Admin Sent: Thursday, November 22, 2012 12:22 PM To: Declude.JunkMail@declude.com Subject: Fw: [Declude.JunkMail] MX, DNS and other weird stuff -----Original Message----- From: Sanford Whiteman Sent: Thursday, November 22, 2012 11:55 AM To: imailad...@bcwebhost.net Subject: Re: [Declude.JunkMail] MX, DNS and other weird stuff [I'm not subscribed using this address, but it's the only one on my mobile. Pls feel free to forward to the list.] This guy's idea that <host> IN MX <host> is incorrect and "will cause issues" should really get him fired if he's the highest-level tech on this. When you want to set up a proper MX record to catch replies to postmas...@mysmtpserver.example.com, you of course do this by setting up such a record. Otherwise the implication would be that you can never receive mail at the same machine that originated it, but have to come up with some fake additional hostname? Ridiculous. Servers have been set up this way since the old days, when it was common to see addresses like u...@host.example.com (as opposed to just @example.com). Likewise, the idea that an intermediate host that is exempt from anti-spoofing measures can't reroute DNS requests is ridic. This is how our egress filters work: a machine listens using a network monitoring port and sends synthesized replies back if a website is in the block list. (The machine isn't a proxy, it's just listening to the switch's mirroring port in promiscuous mode). However, it is true that you have some complexity in your NSs that you need to work out. If you hadn't asked about interception it wouldn't have been my first guess. When you directly query each NS, what do you get? -- S. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to imail...@declude.com, and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to imail...@declude.com, and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
