Re: lame servers resolving

From: T. Nifty Hat Mitchell (mitch48_at_sbcglobal.net)
Date: 06/28/04

  • Next message: Clint Harshaw: "Re: yum and automatic updates" 
    Date: Mon, 28 Jun 2004 13:23:06 -0700
To: For users of Fedora Core releases <fedora-list@redhat.com>

    On Thu, Jun 24, 2004 at 05:20:07PM +0200, Alexander Dalloz wrote:
    > Am Do, den 24.06.2004 schrieb olga@urbantimes.net um 16:56:
    >
    > > Since I am on the topic of logs... Here's another question.
    > > I am getting a lot of 'lame server resolving' messages in the
    > > /var/log/messages.
    > >
    > > Here's an example:
    > > Jun 24 09:02:25 isis named[1340]: lame server resolving
    > > '71.68.90.80.in-addr.arpa' (in '68.90.80.in-addr.arpa'?): 80.90.64.38#53
    > >

    > You can safely ignore such lame server messages, or even suppress them
    > with following entry in the logging section of named.conf:
    >
    > category lame-servers {
    > null;
    > };
    >
    > A "lame server" is one that should be authoritative for a zone,
    > according to the NS records that delegate authority for that zone, but
    > really isn't, perhaps because it hasn't been configured to load the zone
    > or because it is a secondary master that has expired the zone.
    >

    How do you filter lame-server messages so you can discover
    problems with your own domain and toss those that are out
    of your control?

    My practice when I had responsibility of a large name space was to not
    filter any errors going into the logs. When scanning the logs I would
    often build filters on the fly and verify that none of the errors
    had their root cause in anything I had responsibility for.

    On boxes that were a consumer of DNS data then filtering this error
    might be ok. i.e. a local caching name server (SOA for
    localhost.localdomain and look up all the rest). No filters on mail
    relays and MX hosts that might hide a problem.

    And yes, Alexander is correct.
      "> You can safely ignore such lame server messages, or even suppress them"
    unless you are responsible for the net or name space. 

    -- 
	T o m  M i t c h e l l 
	/dev/null the ultimate in secure storage.
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
  • Next message: Clint Harshaw: "Re: yum and automatic updates"

    Relevant Pages

    • Re: Thunderbird / Norton
      ... > ZoneAlarm Pro hat einen Filter für das Windows-Nachrichtensystem. ... > Der Bericht, dass breakout.c mit Zone Alarm Pro nicht funktioniert, ist ... Next by Date: ...
      (de.comp.security.firewall)
    • Re: Warum provoziert man durch korrektes Fahren?
      ... weil dieser Camin sich einen Platz im Filter verdient hat. ... Ohhhhhh unser armer Mr. Filter :-) ... Das ist mehr als genug Grund für 50 in der 70er Zone. ... Aber es gibt ja bestimmt ein paar Tiltdeppen, ...
      (de.etc.fahrzeug.auto)
    • Re: Help with Combo Box
      ... Advanced filter on the data sheet? ... Is it because you want just that data associated with the selected "zone" to ... Might be Ron de Bruin's Easy Filter add-in would help. ...
      (microsoft.public.excel.misc)
    • Re: New Pond
      ... my filter will it freeze in the pump? ... We recently purchased a fish pond. ... the question we have is for the the winter months do we just unplug the ... Tri-Cities WA Zone 7a ...
      (rec.ponds)
    • Re: Sun M-class hardware denial of service
      ... then if you NEED that zone back, you have to power the machine down. ... attachments is expressly prohibited. ... VIRUS: Every care has been ... It is your responsibility to ensure virus ...
      (Bugtraq)