yes - and it presumes your DNS servers are based on Linux and use IPTables.
http://www.cryptonizer.com/dnsamp.html
http://serverfault.com/questions/418810/public-facing-recursive-dns-servers-iptables-rules
as an aside, the TAC engineer (Indian engineer #4) stuck with it, and has
found the bug that was causing the meltdown. Credit certainly needs to be
given for that.
On Mon, Sep 21, 2009 at 4:24 AM, Alan Buxey a.l.m.bu...@lboro.ac.uk wrote:
hi,
the webex option is worrying when you have a core
/nm_logging_count.html
On Mon, Sep 21, 2009 at 10:00 AM, Mark Tinka mti...@globaltransit.netwrote:
On Monday 21 September 2009 09:31:48 pm Steven Fischer
wrote:
as an aside, the TAC engineer (Indian engineer #4) stuck
with it, and has found the bug that was causing the
meltdown. Credit certainly needs
doing a compare, I found a single config element, ip ssh logging events
that was present on the device generating the messages, but not on the 4510
that isn't. Removed it, and will see what that does.
On Mon, Jun 8, 2009 at 5:36 AM, Tom Lanyon t...@netspot.com.au wrote:
On 08/06/2009, at 6:53
I have a 4510 in our environment that is reporting literally dozens of
changes to the running configuration throughout the day - days on which I am
certain no changes have been made to it - the syslog message is given with
the header - AUDIT-5-RUN_CONFIG. Cisco's support site doesn't give me a
:
cisco-nsp-boun...@puck.nether.net] On Behalf Of Steven Fischer
Sent: Sunday, June 07, 2009 10:48 PM
To: cisco-nsp@puck.nether.net
Subject: [c-nsp] 4510 reporting dozens of config changes throughout the
day...
I have a 4510 in our environment that is reporting literally dozens of
changes
When deploying our new network a few months ago, we set up Cisco Works to
manage it. Cisco Works detected and flagged the lack of the following
commands as configuration errors:
spanning-tree bpduguard enable
spanning-tree bpdufilter enable
Thinking this recommendation came from Cisco Works, it
On Thu, Mar 26, 2009 at 4:29 PM, a.l.m.bu...@lboro.ac.uk wrote:
Hi,
spanning-tree bpduguard enable
spanning-tree bpdufilter enable
Thinking this recommendation came from Cisco Works, it follows that this
would make sense to do, right? As some more information on the effect of
these
I am seeing weird behavior on OSPF between a 2811 Router, and a 4510R
switch. A number of google searches on this came up empty. It appears as
if OSPF is dropping with the following message on hourly intervals,
sometimes one hour, sometime two hours, sometimes three hours.
005840: Feb 26
