Weird the way we find solutions: Story of CloudFlare, CSF, DAAP, Nagios and Myself

Strange the way I was continuously blocked by my server for port scanning. Never realized that a tiny little extension of attached to Google Chrome could be this much heart throbbing. Little did I realize that the settings to check for updates set to 1 mins could kick me off from the shell permanently. that keeps a check on intruders found the owner himself to catch this time.

It was really crazy day-by-day and started recreating the issue by hopping into logs, figuring that the request coming back to a specific port on my desktop has been the route cause.

Hey listen, I don’t download things with torrent so often. Then what else that could be bothering so much? The google search points to a harmless creative entertainer on my desktop ‘banshee’s plugin and there I go, disabled and even removed the extensions connecting to external world.

No go at all! Here it blocks again. Lets block the incoming port on my desktop. -uff yeah , never used to turn it on before but no go. Put a red signal and say – never come back again. It was just about to scream out louder. Realized that the name that I use to connect no more pings back to my server. It goes on to the and lives for ever on . – Yes, the tiny little change that was made to my domain. has taken over my DNS and I no more control the way my names work.

All that I had to do is to provide the ip instead of random dns name to get off the hook of CSF and continue browsing.

– Finding it funny and not clear – I was in the same condition when I started fixing this issue. You might figure it out little later. Keep reading.

Tags: , , , , , ,

Published by

Omshivaprakash

Gnu/Linux Enthusiast, Kannadiga, Wikipedian, Amateur photographer, trekker and more

Leave a Reply

Your email address will not be published. Required fields are marked *