[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cobalt-users] lame server



On Mon, 29 Jan 2001, Carrie Bartkowiak wrote:

> Seems that my server needs hobbling, or shot. *L*
> Obviously, little old me does NOT host verio.net... and these aren't my IPs.
> They're not even *close* to my IPs.
> 
> Jan 30 12:40:32 www named[916]: Lame server on '19.66.241.207.in-addr.arpa'
> (in '19.66.241.207.in-addr.arpa'?): [192.67.14.16].53 't.ns.verio.net'
...
> Any ideas?
> Should I call up Verio and tell 'em to get their sh*t straight and quit
> trying to send requests to my machine? *L*  (Yeah that would go over real
> well...)

well, yes, you should, they have a confused nameserver, you are seeing
these because looking up IP's when doing web logs or to verify pop3 access
needs to lookup the IP and get a domain name, the lame server message is
because the response from the nameserver that should have the info for
that reverse is giving bogus info back in reply, for example telling your
nameserver to go ask a machine that doesn't make sense (like the machine
that it just asked, or yourself, or a machine that isn't plausabily
authorative for it) , in this case, the server is giving a totally bogus
reply..

    QUESTIONS:
        19.66.241.207.in-addr.arpa.localhost, type = A, class = IN
    AUTHORITY RECORDS:
    ->  localhost
        nameserver = localhost

(eg, ask yourself)