Owning a website is challenging. To be recognized in the Internet’s ocean, to be really competitive, to keep the website bulletproof and running smoothly is…
Bob's Free Stuff
Like the normal world, the Internet also has its happy moments, scandals, and mysteries. Daily, computers on the whole planet use IPv4, IPv6 protocols to…
5 Dig command examples
Dig command (domain information groper) is a built-in command that you can find in any macOS computer and most Linux distros. You can use it to perform a quick check related to your DNS. See individual DNS records or check a name server from the Terminal app with a simple 1 line command.
It might not have a graphical interface, but you will get all you need in its output.
Here you have 5 dig command examples that will show you how to use it and how the answers look.
How many times per day, you hear clients or colleagues mentioning “the cloud”? And still, there’s no proper comprehension of the scale and scope of it.
There are diverse cloud choices for running your business: PaaS, IaaS, and SaaS. Do you know about them? Let’s give it a look at SaaS.
What is SaaS?
SaaS stands for Software as a Service, and it is a business model of software licensing. The software is supplied by providers through subscription. This means the software is held on external servers instead of being on client servers, employees’ computers, or hardware in general.
SaaS supplies plenty of different business apps: email, auditing, file sharing, human resources, management (contacts, clients info, sales, purchases, etc.), document collaboration, calendars, databases, and the list can go so long.
Servers have a way to communicate for informing about queries’ status. They do that through different HTTP response status codes, like the error 404.
Once servers receive a query, they start a process to answer the client with the required website. Using different codes, they indicate if it was successfully completed or not, if there was an error and its type, etc. There are five categories of responses.
- 1, informational responses.
- 2, successful responses.
- 3, redirects.
- 4, client errors.
- 5, server errors.
So you have set up your Forward DNS. You are happy that you added all the needed DNS records, and you think you are done.…
What is the MTR command?
MTR command is a type of traceroute command developed by Matt Kimball in 1997 that allows both traceroute and ping in the same software. Originally the name MTR was an abbreviation of Matt’s traceroute, but in 1998, his colleague Roger Wolff worked on it too and changed the name to My traceroute.
Why is the MTR command better than the traditional Traceroute or Tracert?
The MTR command is better because it combines the Ping and the Traceroute command and gives additional information (statistics about time, packet loss, and round-trip time, too) about each hop on the way from the computer to the host.
You probably came to this article because you want to improve your DNS’s reliability, and you heard about Secondary DNS. Yes, Secondary DNS definitely useful…