[SATLUG] Attention SAC authorized personnel

Henry Pugsley henry.pugsley at gmail.com
Sat Jan 3 12:01:07 CST 2009


On Sat, Jan 3, 2009 at 8:16 AM, David Kowis <dkowis at shlrm.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> Geoff/W5OMR wrote:
> |
> | Can someone explain this?
> |
> | Jan  3 02:49:04 w5omr named[3256]: lame server resolving
> | 'sol.cis.sac.accd.edu' (in 'cis.sac.accd.edu'?): 151.164.1.1#53
> | Jan  3 02:49:04 w5omr named[3256]: lame server resolving
> | 'sol.cis.sac.accd.edu' (in 'cis.sac.accd.edu'?): 151.164.1.1#53
> | Jan  3 02:49:05 w5omr named[3256]: lame server resolving
> | 'ticker.cis.sac.accd.edu' (in 'cis.sac.accd.edu'?): 151.164.1.1#53
> | Jan  3 02:49:05 w5omr named[3256]: lame server resolving
> | 'venus.cis.sac.accd.edu' (in 'cis.sac.accd.edu'?): 151.164.1.1#53
> | Jan  3 02:49:05 w5omr named[3256]: lame server resolving
> | 'venus.cis.sac.accd.edu' (in 'cis.sac.accd.edu'?): 151.164.1.1#53
> |
>
> http://www.linuxquestions.org/questions/linux-networking-3/caching-dns-server-error-lame-server-resolving-294136/
>
> Use djbdns! It doesn't suck as much! ;P
>
> - --
> David Kowis

Doesn't suck as much, or sucks in totally new and interesting ways? ;)
 I'd like to see a Windows admin who barely understands Microsoft DNS
trying to admin djbdns on a *NIX box .. you'd have a lot more problems
than lame servers.

Besides, changing DNS software won't do a bit of good if the correct
records aren't entered into the zone files.  A lame server is a server
that is listed as authoritative in a higher level zone, but doesn't
contain records about the zone it is supposedly authoritative for.
The problem could be at the higher level (they enter the wrong
authoritative servers) or at the lower level (they don't realize they
are authoritative or just forgot some records).

The repercussions range from annoying to disastrous.  If only one of
three DNS servers is lame, then you just generate extra traffic and
error messages in remote DNS servers (which are normally supressed).
If the only DNS server listed for a zone is lame, then DNS resolution
simply doesn't work for that zone and people tend to notice.

-Henry


More information about the SATLUG mailing list