Re: Odd response from upstream DNS servers

like. I'm going to continue in that skein until I have found an answer. case closed : Thank you to all for your help and additions and your time. Thank you, *Levi Pederson* Mankato Networks LLC cell | 612.481.0769 work | 612.787.7392 levipeder...@mankatonetworks.net On Tue, Jan 6, 2015

Re: Odd response from upstream DNS servers

. ...0 = Non-authenticated data: Unacceptable 0010 = Reply code: Server failure (2) Questions: 1 Answer RRs: 0 Authority RRs: 0 Additional RRs: 0 Queries DOMAIN-NAME-REQUEST: type NAPTR, class IN Any and all help would be appreciated Thank you,

Re: Odd response from upstream DNS servers

err:0,findfail:0,valfail:0] While I know the Time stamps are different the same thing happens with each request. Now onto the wireshark parse. *Levi Pederson* Mankato Networks LLC cell | 612.481.0769 work | 612.787.7392 levipeder...@mankatonetworks.net On Tue, Jan 6, 2015 at 1:48 PM, Evan Hunt w

Re: Odd response from upstream DNS servers

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

Odd response from upstream DNS servers

r in this issue exists? I have wire sharked and can see the response packet come back to my servers outside interface and the rejection Thank you, *Levi Pederson* Mankato Networks LLC cell | 612.481.0769 work | 612.787.7392 levipeder...@mankatonetworks.net _

FORMERR on packet received from Forwarder

010(QUERIED-HOSTNAME/NAPTR'): add_bad 16-Jun-2014 09:53:59.683 fctx 0x7f92321d1010(QUERIED-HOSTNAME/NAPTR'): try 16-Jun-2014 09:53:59.683 fctx 0x7f92321d1010(QUERIED-HOSTNAME/NAPTR'): query The big thing to NOTE is we're recieving the UPSTREAM packet back with the correct informa