Missing MX record in the DNS zone

I simply overlooked to create one DNS record in my virtual lab. The good news is that I quickly resolved the problem and even better I prepared the new story on my blog. Here is the detailed (step-by-step) troubleshooting guide for the similar DNS problems.

Let’s begin!

How I whitelisted one improperly configured email server?

I explained in my other post the different techniques which can be used to protect your email server from spam and other attacks. In the same time, I explained why the proper email server configuration is very important for the successful communication.

Here’s the story how I used the mighty Jedi tricks and done other’s homework…

Starting our BIND server on Microcore Linux

During the previous phases, we succesfully installed our BIND server, created its main configuration file and added a few zone files for our DNS domains. Our DNS server is ready for the first test. We will try to run it and troubleshoot any potential problem in its configuration.

Let’s begin!

Microcore Linux and the BIND zone files

In my previous articles, I guided you through the process of installation and the basic configuration of the BIND DNS server on Microcore Linux. The last step to make an operational authoritative DNS server is to create the zone files.

The zone file is the structured text file used to describe all resource records associated with one Internet domain. Due its high flexibility, the DNS zone files are used even for other purposes, like with Windows AD to support the domain specific services.

Microcore Linux and the BIND named.conf file

If you followed instructions in my previous article, you have installed Microcore Linux with the BIND server on it. As I mentioned in the mentioned article, we need to create our own files. The first file is the main configuration file – named.conf.

In essence, this is the structured text file with multiple sections. I will show here the most basic version that will fit most of your needs.

Let’s begin!