> I'm wondering how, given my scenario, I should set-up the MX record for > my domain (and all the domains I host)
In your primary domain, set up your main MX records as: $ORIGIN domain.com. mail IN A 192.1.1.1 mail2 IN A 192.2.2.2 @ IN MX 10 mail @ IN MX 20 mail2 Then in all of your hosted domains, simply use the names: $ORIGIN myotherdomain.com. @ IN MX 10 mail.domain.com. @ IN MX 20 mail2.domain.com. That way, you can change the ip's of the servers in your domain (domain.com), along with the serial, and all of the other domains will simply follow suit with no changes required. This is my preferred method for many servers, not just one. We host 300 domains and this makes it very nice to make changes. Steve > > I only have one physical server at the moment which does everyhing: web, > email, etc. > > For sub-domains, to same some time, I have a *.domain.com which forwards > all requests for anything anything.domain.com to the correct IP (where > Apache then handles it using VirutalHosts.) But, for the MX record, I'd > like to use mail.domain.com, so I can eventually set-up and migrate all > users to a specific mail server, whithout having to update all the SOA > records. For example, when I set-up a mail server, I'd like to change > one record in domain.com's SOA which says mail.domain.com in A > 123.456.78.1 and otherwise, *.domain.com in A 123.456.78.2. > > Does this make sense and is their a better, RFC compliant way of doing > this? > > p. > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
