Skip to main content
added 23 characters in body
Source Link
Marcus Müller
  • 51.2k
  • 4
  • 77
  • 119

SERVFAIL is quite clear: instead of telling your client "no sorry, no such record", the DNS resolver asked replies with "sorry, I'm broken".

So, you need to fix that DNS resolver, not the client you're using.

The --ipv4 flag helping suggests it might be your name server's IPv6 connectivity is broken when asked via IPv6, for whatever reason. Maybe check that.

SERVFAIL is quite clear: instead of telling your client "no sorry, no such record", the DNS resolver asked replies with "sorry, I'm broken".

So, you need to fix that DNS resolver, not the client you're using.

The --ipv4 flag helping suggests it might be your name server's IPv6 connectivity is broken. Maybe check that.

SERVFAIL is quite clear: instead of telling your client "no sorry, no such record", the DNS resolver asked replies with "sorry, I'm broken".

So, you need to fix that DNS resolver, not the client you're using.

The --ipv4 flag helping suggests it might be your name server's is broken when asked via IPv6, for whatever reason. Maybe check that.

Source Link
Marcus Müller
  • 51.2k
  • 4
  • 77
  • 119

SERVFAIL is quite clear: instead of telling your client "no sorry, no such record", the DNS resolver asked replies with "sorry, I'm broken".

So, you need to fix that DNS resolver, not the client you're using.

The --ipv4 flag helping suggests it might be your name server's IPv6 connectivity is broken. Maybe check that.