lame

Encode an audio file to MP3 using CBR 320 kbit/second

$ lame -b 320 [path/to/file].wav [path/to/output].mp3

$ lame -V 0 [path/to/file].wav [path/to/output].mp3

$ lame [path/to/file].wav [path/to/output].aac

lame [-d] [-n nameserver] [-q querytype] [-t timeout] [-h host command] domain

-d
    Enable debugging mode.

-n nameserver
    Specify the nameserver to query.

-q querytype
    Specify the query type (e.g., A, MX, NS). Default is NS.

-t timeout
    Set the timeout in seconds. Default is 5 seconds.

-h host_command
    Use host command instead of dig.

domain
    The domain to check for lame delegation.

The `lame` command is a network diagnostic tool used to identify DNS servers that are providing incorrect or inconsistent DNS information. It leverages `dig` or `host` commands to query DNS servers and analyzes the responses. The primary purpose is to detect 'lame delegation,' which occurs when a DNS server is configured to delegate authority for a domain to a nameserver that is not authoritative or is misconfigured. This can cause DNS resolution failures and intermittent connectivity issues. It helps network administrators quickly pinpoint DNS servers causing problems.
The command uses `dig` by default, but allows to specify the tool.
If a server answers a query but is not authoritative for the domain, that means it is not lame. A server that is authoritative for the domain must be authoritative in its answer.

The `lame` command relies on the availability of `dig` or `host` on the system. The results can be affected by network connectivity issues or firewalls blocking DNS queries.

To check for lame delegation for the 'example.com' domain using the default settings:
lame example.com
To check using a specific nameserver and a timeout of 10 seconds:
lame -n ns1.example.com -t 10 example.com
To check using host:
lame -h host example.com

The `lame` command will output information about the DNS servers queried and their responses. Look for indications of servers that are not authoritative or provide inconsistent data. 'LAME' messages will appear if misconfigurations are detected. Examine the server names displayed to find the problematic entities.

The history and development specifics of the `lame` command are not broadly documented in common Linux distributions' man pages or documentation. The command likely originated as a custom scripting tool to help system administrators troubleshoot DNS issues. Specific release details are hard to trace without knowing the exact source code repository or distribution where it originated.

dig(1), host(1), nslookup(1)