Has anyone seen anything like this before? It caused my server to lockup. It shows the internal ip of a router to a different department in our office and the router shows that it was receiving an IP spoofing Attack.
Apr 1 18:44:07 core2 /usr/sbin/named[1521]: client 172.0.0.92#4526: no matching view in class 'CLASS15'
Apr 1 18:44:08 core2 /usr/sbin/named[1521]: client 172.0.0.92#4527: no matching view in class 'CLASS15'
Apr 1 18:44:08 core2 /usr/sbin/named[1521]: client 172.0.0.92#4528: no matching view in class 'CLASS15'
Apr 1 18:44:08 core2 /usr/sbin/named[1521]: client 172.0.0.92#4529: no matching view in class 'CLASS15'
Apr 1 18:44:08 core2 /usr/sbin/named[1521]: client 172.0.0.92#4530: no matching view in class 'CLASS15'
Apr 1 18:44:08 core2 /usr/sbin/named[1521]: client 172.0.0.92#4531: no matching view in class 'CLASS15'
Apr 1 18:44:08 core2 /usr/sbin/named[1521]: client 172.0.0.92#4533: no matching view in class 'CLASS15'
Apr 1 18:44:08 core2 /usr/sbin/named[1521]: client 172.0.0.92#4534: no matching view in class 'CLASS15'
Apr 1 18:44:33 core2 /usr/sbin/named[1521]: client 172.0.0.92#4598: no matching view in class 'CLASS15'
Apr 1 18:44:38 core2 /usr/sbin/named[1521]: client 172.0.0.92#4599: no matching view in class 'CLASS15'
Apr 1 18:44:38 core2 /usr/sbin/named[1521]: client 172.0.0.92#4600: no matching view in class 'CLASS15'
Apr 1 18:44:38 core2 /usr/sbin/named[1521]: client 172.0.0.92#4601: no matching view in class 'CLASS15'
Apr 1 18:44:39 core2 /usr/sbin/named[1521]: client 172.0.0.92#4604: no matching view in class 'CLASS15'
Apr 1 18:44:39 core2 /usr/sbin/named[1521]: client 172.0.0.92#4605: no matching view in class 'CLASS15'
Apr 1 18:44:39 core2 /usr/sbin/named[1521]: client 172.0.0.92#4607: no matching view in class 'CLASS15'
Apr 1 18:44:39 core2 /usr/sbin/named[1521]: client 172.0.0.92#4609: no matching view in class 'CLASS15'
Any ideas?
Thanks
0 Replies
945 Views