Lame server

[Peter Rose]

It's not your problem - a lame server is one that has been delegated a
domain that it's not authoritative for. Do nothing!

Peter Rose
London UK

In message <t691jrc41r6qe7 at corp.supernews.com>, dd <doug at schwoo.com>
writes
>I am running DNS server on a Redhat 6.1 with bind-8.2.2_P7-0.6.2 and i keep
>getting these messages in my dns logfile
>
>Jan 16 13:21:23 named[18661]: Lame server on '41.5.67.206.in-addr.arpa' (in
>'5.67.206.IN-ADDR.ARPA'?): [198.6.1.81].53 'auth01.ns.uu.net'
>Jan 16 13:21:23 named[18661]: Lame server on '41.5.67.206.in-addr.arpa' (in
>'5.67.206.IN-ADDR.ARPA'?): [198.6.1.65].53 'auth00.ns.uu.net'
>Jan 16 13:22:11 named[18661]: Lame server on '139.68.105.64.in-addr.arpa'
>(in '68.105.64.IN-ADDR.ARPA'?): [208.230.117.66].53 'NS1.LASERLINK.NET'
>Jan 16 13:22:28 named[18661]: Lame server on '175.139.42.216.in-addr.arpa'
>(in '139.42.216.IN-ADDR.ARPA'?): [192.67.14.16].53 't.ns.verio.net'
>Jan 16 13:22:28 named[18661]: Lame server on '175.139.42.216.in-addr.arpa'
>(in '139.42.216.IN-ADDR.ARPA'?): [129.250.35.32].53 'b.ns.verio.net'
>Jan 16 13:22:29 named[18661]: Lame server on '103.175.103.210.in-addr.arpa'
>(in '175.103.210.IN-ADDR.ARPA'?): [203.255.112.4].53 'ns2.nuri.net'
>Jan 16 13:22:29 named[18661]: Lame server on '103.175.103.210.in-addr.arpa'
>(in '175.103.210.IN-ADDR.ARPA'?): [203.255.112.34].53 'ns.nuri.net'
>Jan 16 13:22:45 named[18661]: Lame server on '6.124.164.207.in-addr.arpa'
>(in '124.164.207.IN-ADDR.ARPA'?): [198.235.216.2].53 'ns2.bellglobal.com'
>Jan 16 13:25:01 named[18661]: Lame server on 'ads.smartclicks.com' (in
>'SMARTCLICKS.com'?): [209.1.235.120].53 'SCA02.SEC.DNS.EXODUS.NET'
>
>Can anyone helpme and/or tell me what can be the cause of this and/or how to
>fix this?
>
>Doug
>
>
>
>

Cyberscreen Internet Services.
25, Oak Hill,
Woodford Green,
Essex IG8 9NS
UK

Tel/Fax: +44 (0)208 504 6316
Mobile: +44 (0)7771 987452
www.cyberscreen.com