Re: [expert] lame server resolving
Jay wrote: > > Hey, my syslog has a dozens of entries similar to the following > > lame server resolving 'xxx.xxx.xxx.xxx.in-addr.arpa' (in > 'xxx.xxx.xxx.in-addr.arpa'?): xxx.xxx.xxx.xxx#53 > > all with different IP's... > > As far as I can tell, some client is asking my server for information on an IP > but my server doesn't have that information? Is that what lame server > resolving is? > > Jay > Are you running a public dns server? What this message means is that some other dns server is running on the internet, and it does not have its namespace in an upstream dns server. This means that recursion is not working for this lame server's in-addr.arpa zone (reverse lookup). This is not your foul up, it is some other person's foul up, namely the person that setup the "lame" dns server. They did not do it correctly. The reason for asking you if your dns server was public, and, therefore, on the internet was because you need to have at least two other dns servers that have your dns server's namespace in their RR's (resource records). These two other dns servers will point back to your dns server, and they will provide your dns server with recursive functionality. Therefore, you will not be the "lame server". I would assume that the x's in your ip address example, from your log file, are NOT your dns server's ip address, right? In this case, some other person has screwed up their dns setup. You can not do much about these messages, except to email the clown, and tell him/her to get their shit together (you will do this to no avail. Take it from one who has tried a time or two). > -- > Crowded elevators smell different to midgets. > Now I have seen some sick sigs in my time but this one is certainly one of the sickest I have ever seen. You win, hands down, with this one. I certainly hope it is attached to all your mail, especially your important business correspondence. The world is in need of this kind of sickness. Keep up the good work :-) drjung -- J. Craig Woods UNIX/NT Network/System Administration http://www.trismegistus.net/resume.html Character is built upon the debris of despair --Emerson Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] lame server resolving
Jay wrote on Tue, Aug 20, 2002 at 04:53:23PM -0400 : > > lame server resolving 'xxx.xxx.xxx.xxx.in-addr.arpa' (in > 'xxx.xxx.xxx.in-addr.arpa'?): xxx.xxx.xxx.xxx#53 > As far as I can tell, some client is asking my server for information on an IP > but my server doesn't have that information? Is that what lame server > resolving is? Some client equals YOUR machines. And no, it's not your server that has the problem, it's other people's servers. Let's say that whois on domain mrball.net results in dns entries: DNS15.REGISTER.COM 216.21.234.78 DNS16.REGISTER.COM 209.67.50.246 NIXBOX.NIXIT.CA24.101.148.92 If you query dns15 and dns16, you will get an answer for hostnames in the mrball.net domain. However, the proprietor of the third entry does not have any real information about mrball.net. (The real whois results are just the first two). When you try to ping/lynx/whatever to www.mrball.net, you ask your nameserver for the IP address, it gets the list of authoritative DNS servers, and then asks one of them. If it finds that one says "I don't know anything about mrball.net" even though the above records indicate it _should_, then THAT is a lame server and your dns server records it in your logs. The problem is much more frequent with reverse lookups than it is with forward lookups. Blue skies... Todd -- Todd Lyons -- MandrakeSoft, Inc. http://www.mandrakesoft.com/ UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. -- Doug Gwyn Cooker Version mandrake-release-9.0-0.3mdk Kernel 2.4.19-4mdk msg57152/pgp0.pgp Description: PGP signature
[Fwd: [expert] lame server resolving]
oops, forgot about sending it to the list.. -- J. Craig Woods UNIX/NT Network/System Administration http://www.trismegistus.net/resume.html Character is built upon the debris of despair --Emerson --- Begin Message --- Jay wrote: > > Hey, my syslog has a dozens of entries similar to the following > > lame server resolving 'xxx.xxx.xxx.xxx.in-addr.arpa' (in > 'xxx.xxx.xxx.in-addr.arpa'?): xxx.xxx.xxx.xxx#53 > > all with different IP's... > > As far as I can tell, some client is asking my server for information on an IP > but my server doesn't have that information? Is that what lame server > resolving is? > > Jay > Are you running a public dns server? What this message means is that some other dns server is running on the internet, and it does not have its namespace in an upstream dns server. This means that recursion is not working for this lame server's in-addr.arpa zone (reverse lookup). This is not your foul up, it is some other person's foul up, namely the person that setup the "lame" dns server. They did not do it correctly. The reason for asking you if your dns server was public, and, therefore, on the internet was because you need to have at least two other dns servers that have your dns server's namespace in their RR's (resource records). These two other dns servers will point back to your dns server, and they will provide your dns server with recursive functionality. Therefore, you will not be the "lame server". I would assume that the x's in your ip address example, from your log file, are NOT your dns server's ip address, right? In this case, some other person has screwed up their dns setup. You can not do much about these messages, except to email the clown, and tell him/her to get their shit together (you will do this to no avail. Take it from one who has tried a time or two). > -- > Crowded elevators smell different to midgets. > Now I have seen some sick sigs in my time but this one is certainly one of the sickest I have ever seen. You win, hands down, with this one. I certainly hope it is attached to all your mail, especially your important business correspondence. The world is in need of this kind of sickness. Keep up the good work :-) drjung -- J. Craig Woods UNIX/NT Network/System Administration http://www.trismegistus.net/resume.html Character is built upon the debris of despair --Emerson --- End Message --- Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
[expert] lame server resolving
Hey, my syslog has a dozens of entries similar to the following lame server resolving 'xxx.xxx.xxx.xxx.in-addr.arpa' (in 'xxx.xxx.xxx.in-addr.arpa'?): xxx.xxx.xxx.xxx#53 all with different IP's... As far as I can tell, some client is asking my server for information on an IP but my server doesn't have that information? Is that what lame server resolving is? Jay -- Crowded elevators smell different to midgets. Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
