Ondřej Surý wrote:
> I am 99% sure the fpdns is wrong and this is not djbdns. The fpdns relies on
> subtle differences between various DNS implementations and is often wrong
> because there’s either not enough data or just not enough differences. That’s
> what I’ve seen when we started with Knot
On Sat, Jul 30, 2022 at 11:14 AM Ondřej Surý wrote:
> I am 99% sure the fpdns is wrong and this is not djbdns. The fpdns relies
> on subtle differences between various DNS implementations and is often
> wrong because there’s either not enough data or just not enough
> differences. That’s what
I am 99% sure the fpdns is wrong and this is not djbdns. The fpdns relies on
subtle differences between various DNS implementations and is often wrong
because there’s either not enough data or just not enough differences. That’s
what I’ve seen when we started with Knot DNS - the quality
Puneet Sood writes:
> Jaap up-thread used fpdns to figure out the first question.
> fingerprint (e.ns.email.sonyentertainmentnetwork.com, 207.251.96.133): DJ
> Bernstein TinyDNS 1.05 [Old Rules]
Subtle correction: to figure out one possible answer to the first question.
--- Begin Message ---
On Sat, Jul 30, 2022 at 10:26 AM Dave Lawrence wrote:
> Greg Choules via dns-operations writes:
> > I am including in this mail the RNAME from the SOA (same for both
> > zones) in the hope that someone who is responsible for DNS at Sony
> > entertainment will see this and
I am betting on “load balancers”…
--
Ondřej Surý (He/Him)
> On 30. 7. 2022, at 16:39, Dave Lawrence wrote:
>
> Greg Choules via dns-operations writes:
>> I am including in this mail the RNAME from the SOA (same for both
>> zones) in the hope that someone who is responsible for DNS at Sony
>>
Greg Choules via dns-operations writes:
> I am including in this mail the RNAME from the SOA (same for both
> zones) in the hope that someone who is responsible for DNS at Sony
> entertainment will see this and take note.
And tell us what in the world DNS software they're running, and why
they
Puneet Sood via dns-operations writes:
> While the affected operators are spread around the world, the similarity of
> the bad response across operators appears to suggest the DNS software may
> be from the same or closely related source. These servers do not respond to
> a version.bind
rators appears to suggest the DNS software
> may be from the same or closely related source. These servers do not
> respond to a version.bind query.
>
> Have you seen similar bad responses? Do you have an idea of the provenance
> of this software?
&
On Fri, Jul 29, 2022 at 05:04:28PM -0400, Puneet Sood via dns-operations wrote:
> $ dig m.email.sonyentertainmentnetwork.com. TXT
> @e.ns.email.sonyentertainmentnetwork.com
> ;; Warning: Message parser reports malformed message packet.
> ;; Truncated, retrying in TCP mode.
Indeed this response
--- Begin Message ---
Hello,
While making our DNS response validation stricter, we have noticed that a
number of name servers return badly truncated UDP responses. This sometimes
happens with incorrect Answer section RR count.
$ dig m.email.sonyentertainmentnetwork.com. TXT @
11 matches
Mail list logo
