ccc2716 at vip.cybercity.dk
Sat Oct 7 16:41:11 UTC 2006
You would still have to change the mail address in the SOA. That is much
easier of course; I assume that @ can not be used there?
Barry Margolin wrote:
> In article <eg763f$2mfn$1 at sf1.isc.org>,
> "Josh Hyles" <josh.maillists at gmail.com> wrote:
>> I am running a windows BIND server and am trying to figure out what
>> the best template would be for creating new sites. I currently use the
>> $ORIGIN .
>> $TTL 86400 ; 1 day
>> domain_hosted.com IN SOA NS1.domain.com. root.domain_hosted.com. (
>> 2006053001 ; serial
>> 3600 ; refresh (1 hour)
>> 7200 ; retry (2 hours)
>> 604800 ; expire (1 week)
>> 43200 ; minimum (12 hours)
>> NS NS1.domain.com.
>> NS NS2.domain.com.
>> A 22.214.171.124
>> MX 5 mail.domain_hosted.com.
>> $ORIGIN domain_hosted.com.
>> ftp A 123.456.789.012
>> mail A 123.456.789.012
>> www A 123.456.789.012
>> All of the "domain_hosted" entries must be changed to the new domain
>> that I am hosting... is there any better to do this?
> I'd leave out all the $ORIGIN statements, and use relative names (or @)
> for the zone name. Then you don't have to change anything for the new
> domain -- the origin defaults to the name from the 'zone' statement in
> $TTL 86400 ; 1 day
> @ IN SOA NS1.domain.com. root.domain_hosted.com. (
> 2006053001 ; serial
> 3600 ; refresh (1 hour)
> 7200 ; retry (2 hours)
> 604800 ; expire (1 week)
> 43200 ; minimum (12 hours)
> NS NS1.domain.com.
> NS NS2.domain.com.
> A 126.96.36.199
> MX 5 mail
> ftp A 123.456.789.012
> mail A 123.456.789.012
> www A 123.456.789.012
No improvements come from shouting:
"MALE BOVINE MANURE!!!"
More information about the bind-users