Re: How to avoid a second-level domain name random query
In message <201306171132543202...@114.com.cn>, ShanyiWan writes: > How to avoid a second-level domain name random query,logs as follow: You find the software / site that is generating the queries and remove it. There really isn't much else you can do. -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
How to avoid a second-level domain name random query
How to avoid a second-level domain name random query,logs as follow: 15-Jun-2013 14:34:45.361 queries: client 121.12.219.79#2434 (odqb.x.com): query: odqb.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.407 queries: client 121.15.253.192#56078 (dogd.x.com): query: dogd.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.407 queries: client 116.16.127.250#3286 (ghsb.x.com): query: ghsb.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.407 queries: client 182.90.91.251#2650 (gsq.x.com): query: gsq.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.407 queries: client 61.128.130.231#23459 (lag.x.com): query: lag.x.com IN A -EDC (21.5.79.20) 15-Jun-2013 14:34:45.407 queries: client 58.20.125.162#1356 (pedm.x.com): query: pedm.x.com IN A -EDC (21.5.79.20) 15-Jun-2013 14:34:45.407 queries: client 61.180.213.26#3070 (rdxnb.x.com): query: rdxnb.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.407 queries: client 59.46.60.51#31885 (mrlvs.x.com): query: mrlvs.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.407 queries: client 117.81.222.217#1729 (wagtd.x.com): query: wagtd.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.407 queries: client 124.244.193.115#3886 (oova.x.com): query: oova.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.407 queries: client 183.245.2.161#3297 (djsrd.x.com): query: djsrd.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.408 queries: client 218.76.86.242#53194 (yxd.x.com): query: yxd.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.408 queries: client 183.60.101.134#10555 (ebi.x.com): query: ebi.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.408 queries: client 122.118.176.136#62131 (wtix.x.com): query: wtix.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.408 queries: client 183.60.101.132#49290 (umf.x.com): query: umf.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.408 queries: client 221.1.65.28#40579 (lgefy.x.com): query: lgefy.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.408 queries: client 221.13.136.168#1633 (vrq.x.com): query: vrq.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.408 queries: client 125.80.128.38#3251 (tgpu.x.com): query: tgpu.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.408 queries: client 61.153.251.130#5619 (ydbkp.x.com): query: ydbkp.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.408 queries: client 117.35.144.230#24855 (swke.x.com): query: swke.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.409 queries: client 119.236.180.34#53594 (wss.x.com): query: wss.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.409 queries: client 171.12.4.205#3277 (cbhb.x.com): query: cbhb.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.409 queries: client 117.79.232.217#41566 (mpti.x.com): query: mpti.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.409 queries: client 110.17.12.124#2552 (bxki.x.com): query: bxki.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.409 queries: client 125.89.71.86#8149 (tap.x.com): query: tap.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.409 queries: client 119.189.219.110#3071 (yjden.x.com): query: yjden.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.409 queries: client 114.25.32.17#1203 (rme.x.com): query: rme.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.409 queries: client 123.53.100.103#26508 (tbb.x.com): query: tbb.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.409 queries: client 218.21.78.10#4428 (tnmv.x.com): query: tnmv.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.409 queries: client 222.172.68.53#56814 (ypmb.x.com): query: ypmb.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.409 queries: client 111.255.39.55#4237 (xuhfr.x.com): query: xuhfr.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.409 queries: client 58.19.217.116#4990 (jvpnm.x.com): query: jvpnm.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.410 queries: client 112.172.134.148#51471 (xnbo.x.com): query: xnbo.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.410 queries: client 218.4.201.10#3017 (ovgi.x.com): query: ovgi.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.410 queries: client 119.236.180.34#53606 (lalhl.x.com): query: lalhl.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.410 queries: client 60.164.164.98#35739 (bylvv.x.com): query: bylvv.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.410 queries: client 36.248.153.148#29284 (hrk.x.com): query: hrk.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.410 queries: client 1.189.115.63#1097 (xvd.x.com): query: xvd.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.410 queries: client 218.13.33.54#2402 (iiv.x.com): query: iiv.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.410 queries: client 121.41.238.123#61439 (euvt.x.com): query: euvt.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.411 queries: client 222.188.115.74#2216 (aupl.x.com): query: aupl.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.411 queries: client 110.52.253.225#53372 (qro.x.com): query: qro.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.411 queries: client 124.239.208.19#58949 (tefwc.x.com): query: tefwc.x.com IN A + (21.5.79.20) 15-Jun-2013 14:34:45.411 queries:
Re: Thank you Warren!!! - WAS::Re: This list's prefix
Great! Now step 2 is to remove the tag from the subject line before sending mail back to the list. :) On 06/16/2013 02:50 PM, Jerry K wrote: Hello Warren, Thank you so much for this post. Long time procmail user here. I'm only sad I didn't think of this myself first. Its been working great for me on this list, and a couple of others. Jerry On 06/ 5/13 12:46 PM, Warren Kumari wrote: On Jun 5, 2013, at 11:43 AM, Narcis Garcia wrote: It's not the only mailing list where I'm subscribed. Could please the administrator setup a prefix for messages' subject? You have unwittingly walked into a religious argument. If, like me, you really like list prefixes, *and* you use procmial, you can add them yourself: # Add an [6MAN] to messages to the "IPv6 Maintenance Working Group \(6man\)" :0 fw * ^List-Id:[ ].*\ |/bin/sed -e 's/^Subject:[ ]*/Subject: [6MAN] /' Nice to meet another member of the Church of Prefixes. We meet on Saturdays, and wear tricorn hats. Sure, folk laugh at the hats, but at least it draws attention away from our list prefix kink. Warren For example: [bind-u] Thanks. ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
[BIND-users] Thank you Warren!!! - WAS::Re: This list's prefix
Hello Warren, Thank you so much for this post. Long time procmail user here. I'm only sad I didn't think of this myself first. Its been working great for me on this list, and a couple of others. Jerry On 06/ 5/13 12:46 PM, Warren Kumari wrote: On Jun 5, 2013, at 11:43 AM, Narcis Garcia wrote: It's not the only mailing list where I'm subscribed. Could please the administrator setup a prefix for messages' subject? You have unwittingly walked into a religious argument. If, like me, you really like list prefixes, *and* you use procmial, you can add them yourself: # Add an [6MAN] to messages to the "IPv6 Maintenance Working Group \(6man\)" :0 fw * ^List-Id:[ ].*\ |/bin/sed -e 's/^Subject:[ ]*/Subject: [6MAN] /' Nice to meet another member of the Church of Prefixes. We meet on Saturdays, and wear tricorn hats. Sure, folk laugh at the hats, but at least it draws attention away from our list prefix kink. Warren For example: [bind-u] Thanks. ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users