[c-nsp] Strange corrupt DNS Cache in IOS

Łukasz Bromirski lukasz at bromirski.net
Fri Aug 15 16:12:05 EDT 2014


Open a case with TAC. That's what they are for, right?

-- 
./

> On 15 Aug 2014, at 18:05, Sascha E. Pollok <sp at iphh.net> wrote:
> 
> Frank, Jared,
> 
> I understand your point and I even share it. Sometimes there are setups
> that do not make much sense any other way (this box with DNS server
> mainly serves one single device and no other DNS server around that is
> suitable for the job).
> 
> And before I go ahead and try to deploy some other device for that
> purpose I simply wanted to see if I can make it work with what there is.
> 
> Thanks
> Sascha
> 
> Am 15.08.2014 16:46, schrieb Frank Bulk:
>> Right, but that's all non-Cisco.  My comments were intended to be
>> constrained to Cisco.  
>> 
>> Frank
>> 
>> -----Original Message-----
>> From: Jared Mauch [mailto:jared at puck.nether.net] 
>> Sent: Friday, August 15, 2014 9:42 AM
>> To: Frank Bulk
>> Cc: Sascha E. Pollok; cisco-nsp at puck.nether.net
>> Subject: Re: [c-nsp] Strange corrupt DNS Cache in IOS
>> 
>> 
>>> On Aug 15, 2014, at 10:34 AM, Frank Bulk <frnkblk at iname.com> wrote:
>>> 
>>> Don't use a router as a DNS resolver for customers.  Just don't.
>> 
>> Or if you are, use something that is properly designed for that function.
>> Check out the UBNT EdgeRouter stuff, cheap, vyatta (JunOS-like), and gives
>> you shell access to do other more advanced stuff.  Basically, you can't lose
>> at the unit cost, etc.
>> 
>> - Jared
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/



More information about the cisco-nsp mailing list