Technical article 110924

What do errors about a "Lame server" in my syslog mean?

OpenServer 5.0.5UnixWare 7.1.0

Written · Last revised

Problem

I see errors in my /usr/adm/syslog file that look similar to this:

Lame server on 'ns1.incentre.net' (in 'incentre.net'?): [192.5.5.241].53 'F.ROOT-SERVERS.NET': $

Cause

A "lame server" is one that supposedly is authoritative for a zone, according to the NS records that delegate authority for that zone, but it really isn't authoritative (or doesn't think it is).

In this example, a query to "ns1.incentre.net" failed to retrieve
information for the incentre.net records.  This could be because it
hasn't been configured to load the zone, is misconfigured, or
because it is a secondary master that has expired the zone.

Solution

Once a nameserver discovers that another nameserver is "lame" for a given zone, it won't query that nameserver for data in the zone for a long period of time, so it is important to clear up this problem.

The primary domain name server for this domain should have an "NS" entry (both A and PTR records) for the ns1.incentre.net machine. There should be a separate NS entry for each nameserver in the zone.

In this example, the primary domain name server should also be
configured as authoritative for the incentre.net domain.  To do
this, update the /etc/named.boot file to include a "primary"
directive for both the domain name and the corresponding reverse
(in-addr.arpa) domain address.  If you are updating the
/etc/named.conf file directly, use the "type master" directive
instead of "primary".
Secondary nameservers should be configured in a similar manner
as the primary, but will use the "secondary" directive in
/etc/named.hosts and/or the "type slave" directive in
/etc/named.conf.  Double-check that the address of the primary
nameserver is correct, since you will be querying it to do the
zone transfers.

Remember also that secondary nameservers will expire their data for a domain if the secondary nameserver fails to contact the primary within the time period specified in the named.soa "Expire" field.

See also

DNS & Bind (3rd ed.), Albitz & Liu, Oreilly & Associates

From the Xinuos technical article database, record 110924. Reproduced with permission. The original is at www.sco.com/ta/110924, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.