Ben Burke wrote:
Yes, I know about dig. But the problem I'm having appears to be failure
of dns server to respond, or a communications problem with dns server(s)
I admittedly haven't delved deep into the dig man page, but a suggestion
would be to add a suitable dig incantation to your cron
Rick,
Thanks - yes, that will help, though I don't think I'll get close enough
to the problem to decide if it's ip communications or a windows dns
server issue. (I could do other connectivity tests to the dns servers,
same result)
I came across these options when working with a really
2010/1/27 Ben Burke ben.bu...@internode.on.net:
Rick,
Thanks - yes, that will help, though I don't think I'll get close enough to
the problem to decide if it's ip communications or a windows dns server
issue. (I could do other connectivity tests to the dns servers, same result)
I came
Hi Ben,
You can debug most (all?) of the DNS client resolution issues with dig.
You can test all the DNS client features, from a simple query to a
full transfer zone.
Regards
Rodolfo Martínez
Dirección de Proyectos
Aleux México | http://www.aleux.com
On Tue, Jan 26, 2010 at 5:04 PM, Ben
Thanks Rodolfo,
Yes, I know about dig. But the problem I'm having appears to be failure
of dns server to respond, or a communications problem with dns server(s)
The problem I'm having is intermittent. I have a number of cron jobs
that fail occasionally, failing to resolve a host name.
The
