I have a question about this thread: do i have to create an SPF Record for every host on
my mail server?
We're running one IP-host and tons of virtual hosts.
If you're running BIND, the "include" statement in named.conf and the $include control statement in zone files provides enormous leverage for managing DNS for virtual hosts. When trying to scale up to manage DNS for 100s or 1000s of zones, a GUI is your worst enemy. Actually, a GUI doesn't scale for anything.
Many virtual domains can share a single generic zone file (all zones have exactly the same records. Or, zones could be grouped into 2 or 3 groups, each group has exactly the same records, so just 2 or 3 generic zone files). So modifying the generic zone file modifies 100s or 1000s domains. btw, zone statements should be included into name.conf.
Many (virtual) domains share common records, so one or more "$INCLUDE filename" in their zone files allow you manage
SPF records for virtual domains could be managed with $INCLUDE.
eg, in the zone file db.any-virtual.tld :
$INLCUDE db.def_tll ; default TTL @ SOA ... $INCLUDE db.common_ns ; contain NS records $INCLUDE db.common_mx ; contains MX (and now SPF) records ... zone-specific records (if any) ;end of zonefile
With $include, adding an SPF record to 1000s of zones is reduced to adding just one SPF record to just the one included file db.common_mx.
Len
_____________________________________________________________________
http://IMGate.MEIway.com : free anti-spam gateway, runs on 1000's of sites
_____________________________________________________________________
"Our enemies are innovative and resourceful, and so are we,'' shrub said. ``They never stop thinking about new ways to harm our country and our people, and neither do we." 5_Aug_04
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
