[Twisted-Python] Getting at the underlying issue in a DNSServerError failure.
Jason J. W. Williams
jasonjwwilliams at gmail.com
Wed Jun 16 22:55:51 EDT 2010
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, <exarkun at twistedmatrix.com> wrote:
> On 15 Jun, 11:33 pm, jasonjwwilliams at 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's what
> "SERVFAIL" means in your list). So that's the underlying issue. Are
> you encountering it in other circumstances?
>
> Jean-Paul
>
> _______________________________________________
> Twisted-Python mailing list
> Twisted-Python at twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
>
More information about the Twisted-Python
mailing list