The domain has TTL set to 360 seconds and each fetch Non-recoverable
resolver failure is exactly in the time when TTL was expired and new
query to authoritative nameservers must be done:
; DiG 9.4.-ESV hiden.example.com
;; global options: printcmd
;; Got answer:
;; -HEADER- opcode: QUERY, status
On Tue, Sep 28, 2010 at 10:59:04PM +0200, Miroslav Lachman wrote:
Jeremy Chadwick wrote:
On Tue, Sep 28, 2010 at 08:12:00PM +0200, Miroslav Lachman wrote:
Hi,
we are using fetch command from cron to run PHP scripts periodically
and sometimes cron sends error e-mails like this:
fetch:
Hi,
we are using fetch command from cron to run PHP scripts periodically and
sometimes cron sends error e-mails like this:
fetch: https://hiden.example.com/cron/fiveminutes: Non-recoverable
resolver failure
The exact lines from crontab are:
*/5 * * * * fetch -qo /dev/null
On Tue, Sep 28, 2010 at 08:12:00PM +0200, Miroslav Lachman wrote:
Hi,
we are using fetch command from cron to run PHP scripts periodically
and sometimes cron sends error e-mails like this:
fetch: https://hiden.example.com/cron/fiveminutes: Non-recoverable
resolver failure
The exact
Jeremy Chadwick wrote:
On Tue, Sep 28, 2010 at 08:12:00PM +0200, Miroslav Lachman wrote:
Hi,
we are using fetch command from cron to run PHP scripts periodically
and sometimes cron sends error e-mails like this:
fetch: https://hiden.example.com/cron/fiveminutes: Non-recoverable
resolver
On Tue, Sep 28, 2010 at 08:12:00PM +0200, Miroslav Lachman wrote:
The exact lines from crontab are:
*/5 * * * * fetch -qo /dev/null
https://hiden.example.com/cron/fiveminutes;
*/5 * * * * fetch -qo /dev/null
http://another.example.com/wd.php?hash=cslhakjs87LJ3rysalj79;
In addition to
