Host your own DNS or use a DNS specialist company?
- Thread starter Wambo
- Start date
GM2015
New Member
I'm all for self-hosting services, but for the life of me can't figure out powerdns. I've tried it a few times on VM-s and the server never answered to dig.
I use cloudflare for everything for now.
Indeed, domainbop's comment of failure.
Imagine they drop, lock and purge all free accounts in 30 minutes.
I use cloudflare for everything for now.
Indeed, domainbop's comment of failure.
Imagine they drop, lock and purge all free accounts in 30 minutes.
Last edited by a moderator:
drmike
100% Tier-1 Gogent
Been years since I had PowerDNS going here... Was never simple.
Perhaps someone can share their install notes or point to working tutorial?
This is a simple single instance install with MariaDB:
https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-powerdns-with-a-mariadb-backend-on-ubuntu-14-04
Simple single server Raspberry Pi install:
http://workshop.botter.ventures/2013/10/01/how-to-setup-a-dns-server-with-powerdns-on-raspberry-pi/
Single server CentOS install:
http://www.tecmint.com/install-powerdns-poweradmin-mariadb-in-centos-rhel/
Last edited by a moderator:
GM2015
New Member
That's what I've followed on Debian 8(mostly ubuntu 14.04 tutorials work, sometimes you have to modify file path and package names) and there was no response coming from bind when queried with dig. I've set bind to accept queries from 10.0.0.0/8 and localhost. It never answered despite reboots/service restarts.
drmike
100% Tier-1 Gogent
Weird situation, always something overlooked.
How about binding it in config file to 127.0.0.1 and querying directly against that. Be sure the process is indeed running. I forget if it gracefully fails / notifies you when things go wrong.
Let me see if another clean tutorial out there that is maybe a tad better.
How about binding it in config file to 127.0.0.1 and querying directly against that. Be sure the process is indeed running. I forget if it gracefully fails / notifies you when things go wrong.
Let me see if another clean tutorial out there that is maybe a tad better.
drmike
100% Tier-1 Gogent
Little better tutorial with this one.. using plain old MySQL... Some debugging towards the end of it:
http://www.unixmen.com/how-to-install-powerdns-on-ubuntu-14-04/
http://www.unixmen.com/how-to-install-powerdns-on-ubuntu-14-04/
DomainBop
Dormant VPSB Pathogen
GM2015
New Member
It was surely something in the config directory in the default config files that stopped pdns from replying. Now it's working, except for the resolver's returning nothing! But I'll look into it.
Thanks for the link and ideas.
We do host our own DNS, setup in different locations and different nodes, very easy and uptime is great compare to just one server.
No penalty or find for violating RFCsJust more expected downtime with the SPOF (Single Point of Failure).
No penalty for violating anything.
You want 2+ nameservers because route is the most frequent point of failure.
BTW a server may be "down" for a cache nameserver and "up" for a client application running elsewhere.
Last edited by a moderator:
Off course Cloudflare and Route53 are good providers but I was amazed that DnSimple did not get quoted. It is a rather effective service and like the name suggest simple and with nice documentation.
Bottom line, my answer is use a provider, self hosting DNS can bite very hard if you do not know exactly what you are doing. DNS failures are one of the most common sources of outages.
Bottom line, my answer is use a provider, self hosting DNS can bite very hard if you do not know exactly what you are doing. DNS failures are one of the most common sources of outages.
WiredBlade
New Member
Do you have a blog or website where you share your experience of hosting your DNS using PowerDNS? I made some efforts but was not able to get it to work properly.
Walnuthost
New Member
Better use dns like cloudfare for it speeds up your website.
Nogics Technologies
New Member
I am using Cloudflare and quite happy with it. No more "PAGE NOT FOUND" errors for static pages during very small downtime such as reboots etc.
That depends on what you are trying to do and what you are trying to achieve.
Your DNS:
Complete control over your DNS, you can make your changes, have multiple failover setups and won't cost you additional to set up a private DNS
Using Premium DNS:
Depends on which one you are choosing but can take of things like DDoS protection, Anycast DNS, CDN, etc. all integrated, so you go through less hassle.
It depends on what you are trying to achieve and based on that you can make a decision.
Your DNS:
Complete control over your DNS, you can make your changes, have multiple failover setups and won't cost you additional to set up a private DNS
Using Premium DNS:
Depends on which one you are choosing but can take of things like DDoS protection, Anycast DNS, CDN, etc. all integrated, so you go through less hassle.
It depends on what you are trying to achieve and based on that you can make a decision.
