On 2011-02-15, at 9:52 AM, Tom Evans wrote:
> On Tue, Feb 15, 2011 at 4:38 PM, Norman Fournier
> wrote:
>> Krist
>>
>> Hello,
>> I thought it was all part and parcel of the Apache configuration. The
>> relevant part of the .db file looks like this:
>> $ORIGIN .
>> $TTL 14400; 4 hours
>> e4ed
On Tue, Feb 15, 2011 at 4:38 PM, Norman Fournier
wrote:
> Krist
>
> Hello,
> I thought it was all part and parcel of the Apache configuration. The
> relevant part of the .db file looks like this:
> $ORIGIN .
> $TTL 14400 ; 4 hours
> e4edmonton.com IN SOA
> ns1.normanfournier.com. post
On 2011-02-15, at 6:45 AM, Krist van Besien wrote:
> On Mon, Feb 14, 2011 at 4:54 PM, Norman Fournier
> wrote:
>
>> I have a website running with an expiry date set for 1 week in the database
>> file. Once the .db file expires the site goes offline. I then have increment
>> the serial number,
On Mon, Feb 14, 2011 at 4:54 PM, Norman Fournier
wrote:
> I have a website running with an expiry date set for 1 week in the database
> file. Once the .db file expires the site goes offline. I then have increment
> the serial number, to grep for "named" and -HUP the process to bring the
> sit
Hello,
A newbie question:
I have a website running with an expiry date set for 1 week in the database
file. Once the .db file expires the site goes offline. I then have increment
the serial number, to grep for "named" and -HUP the process to bring the site
online again.
All of my other sites
