All,
I understand this would be easier if it were not obfuscated. But alas that
is not something that can be done.
Thank you to all who have responded. A lot of the information I'm
receiving is indicating something on the authority level. Who has it, Who
is supposed to have it, and the like.
This would really be a lot easier if it were not anonymized. However...
On Tue, Jan 06, 2015 at 02:43:30PM -0600, Levi Pederson wrote:
> Packet 840 Upstream-NS ---> Local-NS
[...]
> Frame 840: 245 bytes on wire (1960 bits), 245 bytes captured (1960 bits)
[...]
> .0.. = Auth
um.com>
>
> o: +1.650.587.1513
>
>
> * adrian.beau...@nominum.com *
> --
> *From:* bind-users-boun...@lists.isc.org [bind-users-boun...@lists.isc.org]
> on behalf of Levi Pederson [levipeder...@mankatonetworks.net]
> *Sent:* Tuesday, January 06, 2015 3:25 PM
>
: Evan Hunt
Cc: bind-users@lists.isc.org
Subject: Re: Odd response from upstream DNS servers
Alrighty,
There could be a lot of sensitive information in the wire shark and I'm looking
at how to parse that now. Currently here is the RESPONSE.log and default.log
information
RESPONSE.log
16-
Alrighty,
There could be a lot of sensitive information in the wire shark and I'm
looking at how to parse that now. Currently here is the RESPONSE.log and
default.log information
RESPONSE.log
16-Dec-2014 23:11:21.417 fetch 0x7f9d85d591d0 (fctx
0x7f9d7f856010(Domain-request/NAPTR)): created
16-D
I'll see about getting that information colluded and sent.
Thank you,
*Levi Pederson*
Mankato Networks LLC
cell | 612.481.0769
work | 612.787.7392
levipeder...@mankatonetworks.net
On Tue, Jan 6, 2015 at 1:56 PM, Warren Kumari wrote:
> On Tue, Jan 6, 2015 at 2:48 PM, Evan Hunt wrote:
> > On
On Tue, Jan 6, 2015 at 2:48 PM, Evan Hunt wrote:
> On Tue, Jan 06, 2015 at 01:03:10PM -0600, Levi Pederson wrote:
>> However I can see the request come back to my server only to be rejected as
>> FORMERR and DNS format error badresp:1
>
> It looks like the upstream server send a badly formatted r
On Tue, Jan 06, 2015 at 01:03:10PM -0600, Levi Pederson wrote:
> However I can see the request come back to my server only to be rejected as
> FORMERR and DNS format error badresp:1
It looks like the upstream server send a badly formatted response. We'd be
better equipped to diagnose the problem
All,
I have an ODD issue with a request to an upstream DNS server
1. I receive the Downstream request and can't fill it locally so I send
request up to upstream server
2. Upstream receives it and does it's thing and sends back a response with
the proper servers for the client to query (this res
9 matches
Mail list logo
