Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Jun 19 05:17:48 shakti named[20003]: lame server resolving '242.212.149.202.ipwhois.rfc-ignorant.org' (in 'ipwhois.rfc-ignorant.ORG'?): 127.0.0.1#53
Jun 19 05:17:48 shakti named[20003]: lame server resolving 'rsginfotech.com' (in 'rsginfotech.com'?): 202.54.119.135#53
No attack. Nothing urgent. The remote DNS just doesn't resolve the name while it should (being authoritative and all that). Turn off by
echo -en "logging {\n\tcategory lame-servers {null; };\n};\n" >> ${CONFDIR:=/etc}/named.conf &&\
/etc/init.d/named reload
BTW, did you search LQ for this? I'm sure we've handled this before.
Thanks for that.
Sorry for I have not searched lq before posting.
But still I do have one more question.
I googled too much and found that there is a lot of controversial stuff on the Internet about lame server...
My DNS was working fine and properly before that and I have not made any changes with any other daemons so misconfiguration is out of question altogether.
We can remove the option of logging in those errors but still I do have some confusion because of different views in different articles
what does that "127.0.0.1#53" thing in the logs mean?
Have I misconfigured something? (Which I dont seem to be as I have not made any changes since long back!)
And the confusion is in that why terminal junkie has blocked the addresses, and what role qmail or mail scanner has played.
Well, basically it boils down to more of the same if you ask me. Something local relies on resolving a domain or hostname for something to work (like RBL's). Something somewhere else should resolve things (or isn't there anymore to resolve things) and that's what the errors is causing. Instead of fixing it the majority opts for the ostrich policy. Nothing controversial I can see. So in short:
Thanks for the help, at last it got into this dumbhead .
Still, I need to know how come there are so many log entries that point out that 127.0.0.1 has querried so much.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.