DNS, the Domain Name Service, is the Internet service that translates IP addresses into hostnames, and visa versa. It enables you to type www.exoprise.com in a browser, or send an email to someone at that domain, and have your request actually go to 35.172.52.247. As a vital part of the Internet infrastructure, DNS attacks can have a serious impact on your online operations, including access to your website and email.
Crashed websites and slow loading pages can be devastating for any site owner. But there’s another type of threat that often goes undetected. A report published by FireEye on Thursday details a particular type of DNS hijacking that allows hackers to easily steal information. These attacks have been going on for approximately two years and involve three different methods that compromise websites without alarming users.
Ever since the launch of our DNS scan, we’ve had the warning about mismatched NS records. Many users choose to ignore this, but there’s a pretty good reason we give a big warning whenever those records don’t line up. In this blogpost, we’ll show what can happen with misconfigured NS records.
Since the inception of Falco, we’ve seen users write custom rules covering a number of different use cases. Because Falco is behavioral monitoring with a syntax that leverages system calls, you can write a rule for just about anything: opening a file, becoming root, or making a network connection.
It’s been a bit quiet on the DNS Spy front lately, hasn’t it? Well, today is about to change that. We’ve launched a big update to DNS Spy. Mostly behind the scenes improvement, but certainly a few things everyone can enjoy!
When we think of DNS (Domain Name System), there are two thoughts that we all assume to be true and that become natural justifications for the development of a DNS Monitoring scheme.Simple and forceful, in fact since the rise of the Internet, DNS systems are a fundamental part of our communications.
Back in 2016, we added support for monitoring wildcard DNS records. Wildcard DNS records are used to serve requests for otherwise non-existent domain names. Today we’re pleased to announce that we’ve extended our support for using wildcards in DNS records monitoring. DNS Check now allows you to specify a wildcard (*) in place of some DNS record values, such as an A record’s IP address to indicate that any value is acceptable, but the record must exist.
The Domain Name System (DNS) is brilliantly designed as a hierarchical structure, ensuring that any single point can fail with the system remaining relatively intact. There are some nuances to this statement, like caching issues that arise from outages, but the overall focus is on uptime. This is why the DNS check is a critical part of your IT uptime monitoring process.
The Domain Name System (DNS) catalog maps text-based URLs to their specifically-numbered host systems. As the phone book or Yellow Pages of the internet, DNS governs the speed with which websites and online resources may be located, so the speed and robustness of your DNS service can have a profound impact on your internet performance overall.
