#bind9

Read the full report on -

In previous tutorials, we explained how to set up authoritative DNS servers and edit DNS records from the command line. However, some folks prefer to use a web GUI to edit DNS records. This tutorial is going to show you how to set up authoritative DNS servers with Webmin, which is a free open-source web-based…

This tutorial will be showing you how to set up a local DNS resolver on CentOS 8/RHEL 8, with the widely-used BIND9 DNS software. There are many synonyms for DNS resolver, some of which are listed below. They all refer to the same thing. full resolver (in contrast to stub resolver) DNS recursor recursive DNS…

This tutorial will be showing you how to set up a local DNS resolver on Debian 10 Buster, with the widely-used BIND9 DNS software. There are many synonyms for DNS resolver, some of which are listed below. They all refer to the same thing. full resolver (in contrast to stub resolver) DNS recursor recursive DNS+ Read More

Aujourd’hui, nous allons voir comment héberger un nouveau domaine sur le serveur, en simplifiant au maximum les procédures. Le nom de domaine sera réservé chez OVH et le site hébergé sur notre serveur Debian. Nous allons servir le site avec NginX en HTTPS grâce à un certificat SSL fourni gratuitement par Let’s Encrypt. Enfin, on utilisera le serveur email existant et on ajoutera la configuration…

[TUTO] Serveur dédié : ajouter l'authentification DMARC à Postfix et BIND #server #sysadmin #postfix #email #dmarc

Notre serveur de mail possède une identification SPF, Sender-ID et DKIM et est sécurisé par un certificat TLS. Nous allons aujourd’hui voir comment lui adjoindre l’authentification DMARC.

Aux origines de l’authentification des emails

Les technologies d’authentification des emails SPF et DKIM ont été développées afin de fournir une plus grande assurance sur l’identité de l’expéditeur d’un…

After my Raspberry Pi SD card got fried, I was left without a DNS server on my home network. So I wanted to reconfigure my other existing server box running Debian to serve as a DNS server.

But I was tired of using the same old Bind9. It’s configuration was somewhat cryptic, to say the least. As always, it was Google to the rescue, and PowerDNS was one of the listed alternatives that really caught my eye.

There were some quick tutorials here and there, that came in handy. But in short, it all boils down to the following core operations on my setup which I believe is way simpler than stated in either sites: 

Run the command:

apt-get install pdns-server pdns-backend-mysql pdns-recursor

Edit the file /etc/powerdns/pdns.conf, uncomment or add the following lines:

launch=gmysql

allow-recursion=127.0.0.1,192.168.0.0/24 #depending on your IP and netmask

allow-recursion-override=on # This is the most important step if you want to serve your fake domains on your home network.

recursor=192.168.0.9:5300 # Again this would point to the actual recursor which we will configure later.

local-address=0.0.0.0

local-port=53 # This is the default DNS port

Edit the file /etc/powerdns/recursor.conf:

local-address=192.168.0.9

local-port=5300

Edit the file /etc/powerdns/pdns.d/pdns.local:

gmysql-host=127.0.0.1 gmysql-user=power_admin gmysql-password=power_admin_password gmysql-dbname=powerdns

Run the following SQL script on MySQL:

CREATE DATABASE powerdns;

GRANT ALL ON powerdns.* TO 'power_admin'@'localhost' IDENTIFIED BY 'power_admin_password'; GRANT ALL ON powerdns.* TO 'power_admin'@'localhost.localdomain' IDENTIFIED BY 'power_admin_password';

FLUSH PRIVILEGES;

USE powerdns; CREATE TABLE domains ( id INT auto_increment, name VARCHAR(255) NOT NULL, master VARCHAR(128) DEFAULT NULL, last_check INT DEFAULT NULL, type VARCHAR(6) NOT NULL, notified_serial INT DEFAULT NULL, account VARCHAR(40) DEFAULT NULL, primary key (id) );

CREATE UNIQUE INDEX name_index ON domains(name);

CREATE TABLE records ( id INT auto_increment, domain_id INT DEFAULT NULL, name VARCHAR(255) DEFAULT NULL, type VARCHAR(6) DEFAULT NULL, content VARCHAR(255) DEFAULT NULL, ttl INT DEFAULT NULL, prio INT DEFAULT NULL, change_date INT DEFAULT NULL, primary key(id) );

CREATE INDEX rec_name_index ON records(name); CREATE INDEX nametype_index ON records(name,type); CREATE INDEX domain_id ON records(domain_id); CREATE TABLE supermasters ( ip VARCHAR(25) NOT NULL, nameserver VARCHAR(255) NOT NULL, account VARCHAR(40) DEFAULT NULL );

INSERT INTO domains (name, type) values ('example.com', 'NATIVE'); INSERT INTO records (domain_id, name, content, type,ttl,prio) VALUES (1,'example.com','localhost [email protected] 1','SOA',86400,NULL); INSERT INTO records (domain_id, name, content, type,ttl,prio) VALUES (1,'example.com','dns-us1.powerdns.net','NS',86400,NULL); INSERT INTO records (domain_id, name, content, type,ttl,prio) VALUES (1,'example.com','dns-eu1.powerdns.net','NS',86400,NULL); INSERT INTO records (domain_id, name, content, type,ttl,prio) VALUES (1,'www.example.com','192.168.5.9','A',120,NULL); INSERT INTO records (domain_id, name, content, type,ttl,prio) VALUES (1,'mail.example.com','192.168.5.9','A',120,NULL); INSERT INTO records (domain_id, name, content, type,ttl,prio) VALUES (1,'localhost.example.com','127.0.0.1','A',120,NULL); INSERT INTO records (domain_id, name, content, type,ttl,prio) VALUES (1,'example.com','mail.example.com','MX',120,25);

Then startup the processes:

/etc/init.d/pdns-recursor start

/etc/init.d/pdns monitor

Then do some digging and have fun: