On Tue, Aug 14, 2012 at 12:33 PM, Howard White <[email protected]> wrote: > Here I go again, trying to Bogart a presentation before it even starts. > > I am now managing (cringe and shudder) DNS for my employer. At least this > one is done in a manner to which I am accustomed. > > My new challenge is thus - we have an intranet configured with the Top Level > Domain (TLD) of .local and parallel intranet with the TLD of .vpn. We have > an internet zone configured with the TLD of .com. We use a variety of > services hosted by Comcast, most specifically smtp and imap. None of our > DNS config files have an MX record within but there is an smtp IN CNAME > record in the .com zone. > > We have servers upon which we need to configure a "null client" postfix > daemon. Null client is a system that may only send mail; a server that > needs to send error messages and such to admins (that would be me). Said > server is defined in the .local zone. The null client examples I have found > so far by searching only describe a homogeneous .com network. I see the > need for the .local server to relay to the Comcast smtp to be able to get > the mail delivered. > > But how??? > > Howard >
Configure a single postfix server to deliver mail to Comcast SMTP server and configure all your other systems to deliver mail using the previously mentioned smart host? Setting $mydomain in main.cf on each server to your actual .com domain would prevent any of the .local address showing up in mail being sent out to Comcast SMTP servers. Or, in theory you could skip the smart host set and just set relayhost to Comcast SMTP server on each machine. I don't think you'll need any special configurations in DNS for any of this work, unless I've missed a detail. -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en
