News for hackers. Stuff that matters.
Re:Why might you run your own DNS server? by remram on Wednesday January 05, 2022 @02:56PM (#29814078)
How much difficulty is added by DNSSEC?
Re:Why might you run your own DNS server? by brian_cunnie on Wednesday January 05, 2022 @04:02PM (#29814893)
I don't know how difficult it is to set up DNSSEC, but I do know I had to disable it on my internal BIND DNS server because it wasn't resolving google.com ("query failed (broken trust chain) for www.google.com/IN/A at query.c"):

I had to modify my default BIND options to disable DNSSEC:

options {

  dnssec-enable no;

  dnssec-validation no;
Re:Why might you run your own DNS server? by m3047 on Wednesday January 05, 2022 @04:06PM (#29814941)
If you want DNSSEC to work, be sure you set up NTP and that it's working properly.
Re:Why might you run your own DNS server? by tadfisher on Wednesday January 05, 2022 @04:25PM (#29815155)
Also, NAT64 breaks DNSSEC (by design), so some exclusion rules are needed.
Re:Why might you run your own DNS server? by hsbauauvhabzb on Wednesday January 05, 2022 @05:39PM (#29816148)
In late 2019 I scanned Fortune 500 for DNSSEC on their top domain, exactly one entity was using it. At the time azures stance on dnssec support was that https certs should suffice.

I think it’s a dead tech.

Re:Why might you run your own DNS server? by bbarnett on Wednesday January 05, 2022 @08:41PM (#29818011)
You haven't lived, until you cannot update the time via ntp, because no dns, because dnssec records aren't valid, because the time is wrong....

This dnssec/ntp dependency loop is absurd, and it is incomprehensible that ntp/dns can break this way.

Re:Why might you run your own DNS server? by ianai on Wednesday January 05, 2022 @11:32PM (#29819417)
Could you fix that? I've had mixed results trying to resolve such NTP related issues.
Re:Why might you run your own DNS server? by bbarnett on Thursday January 06, 2022 @05:56PM (#29831748)
I think using IPs for NTP servers, or disabling dnssec are your only options.

Both show how silly it all is, IMO.

Re:Why might you run your own DNS server? by tptacek on Wednesday January 05, 2022 @10:04PM (#29818756)
Quick, easy project! I did it just now (finding a list of F500 domains was the hardest part), and 9% of the Fortune 500 is signed.
Re:Why might you run your own DNS server? by egberts1 on Wednesday January 05, 2022 @07:43PM (#29817524)
Not at all … nowadays.

In fact, I run my own private Internet complete with DNSSEC for my white lab.

I used Bind v9.16+ and wrote some bash tools to generate in a flexible manner the named configuration files.

Can generate private root servers, private TLD, split-horizon, bastion, and hidden-master.

Re:Why might you run your own DNS server? by egberts1 on Wednesday January 05, 2022 @07:45PM (#29817536)
link to generate named configuration files.

https://github.com/egberts/easy-admin/tree/main/500-dns

Re:Why might you run your own DNS server? by belorn on Thursday January 06, 2022 @05:22AM (#29821746)
adding DNSSEC validation isn't hard (a few options), but as others has commented one have to be a bit aware that dnssec validation might then fail from time to time. Validating other peoples security setup mean occasionally that people mess up and validation fails. I have been running with validation on 10-20 years, and maybe once a year I notice a service that is down because failing validation. It is a bit like expired certificates on https back in the days before most sites started to use automation for renewing.

Adding DNSSEC to a domain name is more work. You need a registrar that support it, and then depending on what DNS server program you are running you might need to install a signer, a key storage, monitoring and scripts that talks between the different parts of the chain. I have heard that the latest version of bind might now ship with all the required parts built in, but I have yet to test it. It a bit far yet from simply uncommenting an option, and the protocols for talking with registrars is being actively discussed and worked on during technical conferences.

Re:Why might you run your own DNS server? by petee on Wednesday January 05, 2022 @03:17PM (#29814343)
Not much but you should have a good grasp first, and the implications (easy to add, tougher to remove)

There are tools to automate resigning, but personally I just do it manually once a year for fun.

Re:Why might you run your own DNS server? by rhizome on Wednesday January 05, 2022 @03:19PM (#29814380)
Less than the amount of difficulty added to driving a car that can only be adjusted by poking at a TV mounted some place where you aren't looking at the road.

Sure, fixing that squeaky door is "easy," but have you ever heard the adage that every home project involves three trips to the hardware store? There may be technical aspects that few of us can implement from scratch and on the first try, but at the same time I also don't know how to build a good broom. These concerns are not insurmountable, especially with the network effects of people being in the same boat. How easy is it to find a good handyman without asking anybody? You don't have to.

Re:Why might you run your own DNS server? by remram on Wednesday January 05, 2022 @05:25PM (#29815967)
The question was about DNSSEC.
Re:Why might you run your own DNS server? by southerntofu on Thursday January 06, 2022 @08:53AM (#29823511)
It's work, but it's not difficult. Documentation is good and some daemons like BIND take care of key rollovers automatically.