Bobcares

PowerDNS docker-compose | Guide

by | Apr 30, 2022

PowerDNS docker-compose can be set up without any further ado with this handy guide Read to find out more. 

At Bobcares, we offer solutions for every query, big and small, as a part of our Docker Support.

Let’s take a look at how our Docker Support Team is ready to help customers run PowerDNS docker-compose successfully.

All About PowerDNS docker-compose

Power DNS is an Open Source DNS server that offers an alternative to traditional BIND DNS. It works with a variety of databases, including MariaDB, MySQL, SQLite3, and others.

Today, we are going to look at how we can use PowerDNS with a Docker container.

PowerDNS docker-compose

First, we have to download the correct Docker version as per our Operating System from this link. https://www.docker.com/get-started

Furthermore, for Linux Ubuntu:

  • engine
    https://docs.docker.com/engine/install/ubuntu/

  • compose
    https://docs.docker.com/compose/install/

After installation, we have to create a docker-compose.yml file. We can download the compose file from this link.

Next, we have to create SQLite database before running pdns:

mkdir /var/lib/powerdns
sqlite3 -init schema.sql /var/lib/powerdns/pdns.sqlite3

We can get schema.sql from this link.

After that, we will set the following environment variables:

export PDNS_RECURSOR_API_KEY=changeme
export PDNS_AUTH_API_KEY=changeme

At this point, we can easily start the container by running the following command where the docker-compose.yml file is:

docker-compose up -d

Finally, test if the containers are running successfully with this command:

docker-compose ps -a

Once the containers are up we can test the service as seen here:

curl -v -H 'X-API-Key: changeme' http://:8081/api/v1/servers/localhost/ | jq

Furthermore, we can add zones to the authoritative server with pdnsutil.

In this guide, we have used SQLite 3 rather than the default. If you run into trouble with any of the above steps, our technicians are available 24/7 to help you out.

[Need assistance with another query? We are just a click away.]

Conclusion

In a nutshell, our skilled Support Engineers at Bobcares demonstrated how to run PowerDNS docker-compose succesfully.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

2 Comments

  1. SQ

    The docker-compose.yaml is for MariaDB and not working with SQLite…

    Reply
    • Hiba Razak

      Hi,
      Please contact our support team through live chat (click on the icon at right-bottom).

      Reply

Submit a Comment

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

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF