Hi Jean-Paul,
You're right DNSServerError = SERVFAIL. DNSNameError = NXDOMAIN
The object reference in the description of the thrown exception left
some uncertainty regarding what the error really was saying.
-J
On Wed, Jun 16, 2010 at 8:06 PM, wrote:
> On 15 Jun, 11:33 pm, jasonjwwilli...@gma
On 15 Jun, 11:33 pm, jasonjwwilli...@gmail.com wrote:
>Hi Guys,
>
>What is the best way to get at the underlying issue (i.e.
>non-responsive name server, NXDOMAIN, SERVFAIL, etc.) when receiving a
>twisted.names.error.DNSServerError?
DNSServerError is documented as indicating ESERVER (I think that
I would really like to know this too, but for DNSNameError instead (off
the top of my head). This is when using the LookupPointer() method. It
seems to return an error rather than a reverse DNS record if the forward
DNS of the reverse DNS hostname doesn't match the original IP address.
That'
Hi Guys,
What is the best way to get at the underlying issue (i.e.
non-responsive name server, NXDOMAIN, SERVFAIL, etc.) when receiving a
twisted.names.error.DNSServerError?
I'm issuing a resolver.lookupNameservers() BTW.
The failure received by the errback generates this for
failure.getErrorMes
