by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 08:10
    GitLab | Daniel Salzman pushed to Knot DNS
  • 08:09
    GitLab | Daniel Salzman pushed to Knot DNS
  • 08:07
    GitLab | Daniel Salzman pushed 1 commits to Knot DNS
  • 08:05
    GitLab | Daniel Salzman pushed 2 commits to Knot DNS
  • 07:23
    GitLab | Daniel Salzman pushed to Knot DNS
  • 07:23
    GitLab | Daniel Salzman pushed 1 commits to Knot DNS
  • Aug 13 14:47
    GitLab | Daniel Salzman pushed 4 commits to Knot DNS
  • Aug 12 14:08
    GitLab | Daniel Salzman pushed 13 commits to Knot DNS
  • Aug 12 08:09
    GitLab | Daniel Salzman pushed 1 commits to Knot DNS
  • Aug 11 18:27
    GitLab | Daniel Salzman pushed 10 commits to Knot DNS
  • Aug 11 17:31
    GitLab | Daniel Salzman pushed 2 commits to Knot DNS
  • Aug 11 17:26
    GitLab | Daniel Salzman pushed 1 commits to Knot DNS
  • Aug 11 13:29
    GitLab | Daniel Salzman pushed 1 commits to Knot DNS
  • Aug 11 12:41
    GitLab | Daniel Salzman pushed 2 commits to Knot DNS
  • Aug 11 12:41
    GitLab | Libor Peltan pushed to Knot DNS
  • Aug 11 12:41
    Daniel Salzman merged merge request #1166 sem check: skip crypto if keytag mismatch in Knot DNS
  • Aug 11 12:41
    Daniel Salzman closed issue #688 kzonecheck performance penalty with passive keys in Knot DNS
  • Aug 11 12:35
    David Vasek commented on issue #689 use MX record in geoip in Knot DNS
  • Aug 11 12:29
    Libor Peltan opened merge request #1166 sem check: skip crypto if keytag mismatch in Knot DNS
  • Aug 11 12:28
    GitLab | Libor Peltan pushed 1 commits to Knot DNS
muellert
@muellert
In reality, I have a FQDN in both fields.
Daniel Salzman
@salzmdan
Do you have any example?
muellert
@muellert
Yes. Without revealing the real (and existing) domain name, I have
server:
    identity: "dns.example.com"
    nsid: "dns.example.com"
Trying this on the command line:
# knotc conf-set 'server[identity]: "dns.example.com"'
error: (unexpected token) : "dns.example.com"
# knotc conf-set 'server.identity: "dns.example.com"'
error: (invalid item) server.identity: "dns.example.com"
Daniel Salzman
@salzmdan
Ah, ok, you have to remove the colon
muellert
@muellert
I tried that as well:
# knotc conf-set 'server.identity "dns.example.com"'
error: (invalid item) server.identity "dns.example.com"
# knotc conf-set 'server[identity] "dns.example.com"'
error: (unexpected token)  "dns.example.com"
Daniel Salzman
@salzmdan
muellert
@muellert
Ok... my bad. :( I think I was too stressed when I tried.
But it doesn't solve any of the "ghost database" and config file ignore problems.
Daniel Salzman
@salzmdan
Let's try it again: stop/kill all running knotd instances, remove the configuration database, and start the server again.
Also check if the server was started with some parameters (-C, -c) ps | grep knotd
muellert
@muellert
# cat /etc/default/knot 
KNOTD_ARGS="-v"
Daniel Salzman
@salzmdan
This one is harmless
muellert
@muellert
# systemctl start knot
# ps auwwx|grep knot
knot      5945  0.0  1.9 567872 19944 ?        Ssl  21:28   0:00 /usr/sbin/knotd -v
Daniel Salzman
@salzmdan
ok, and the logs?
If there was no config DB during the server start, it should use the config file
muellert
@muellert
It says loaded configuration database '/var/lib/knot/confdb', which doesn't exist, also complains about the non-existing zone, and error: failed to load configuration file '/etc/knot/knot.conf' (invalid indentation) I'm trying to track this down, but can't see at the moment what should be wrong (it's a YAML file, isn't it?).
Before any of that, I ran knotc zone-check on all zones, and didn't get any errors.
Daniel Salzman
@salzmdan
Maybe, it checked the configuration database. Try knotc -c /etc/knot/knot.conf conf-check
Yes, it's "YAML". You could try some online checkers. http://www.yamllint.com/
muellert
@muellert
Ok, found it. Your command also says that the (wrong?) config is valid, but the problem was that most of the file has an indent of 2, while the server section had an indent of 4.
Making the server section also have an indent of 2 made knot import the file. But I'd say knotc should have complained already.
Because knotc is run as part of the systemd unit file during startup.
Daniel Salzman
@salzmdan
The indentation can be different across sections, but must be consistent within a section
muellert
@muellert
It was consistent within each section.
I also thought it could be different on a per-section basis, yet this was the change that made it work.
Daniel Salzman
@salzmdan
So, it works now?
muellert
@muellert
No. Something else is wrong. Suddenly, the server refuses all queries, despite having loaded the zones and the socket being open.
Oh.. my mistake: "No zones loaded"
Daniel Salzman
@salzmdan
Btw, could you share an anonymized snippet of the broken config file? I would investigate that.
muellert
@muellert
ok... it does need the zone: section
Daniel Salzman
@salzmdan
if you want to configure zones :-)
muellert
@muellert
It is really the thing I mentioned in the beginning.
I (mis-) understood you to mean that if I don't have a config database, it would load all zone files matching the template specs automatically.
Do you have a GPG key, besides the one for code signing?
Daniel Salzman
@salzmdan
Ah, no, the server loads explicitly configured zones only.
Yes, see https://www.knot-dns.cz/development/
muellert
@muellert
I'll then send you something via email.
Daniel Salzman
@salzmdan
Ok. It's to late here. Will continue tomorrow.
muellert
@muellert
No problem. This is "only" my standby nameserver. Thanks a bunch for your help so far!
Daniel Lublin
@quite
Hi! (this has probably been asked before) I seems like it would be useful to be able to reference a remote from an acl, to avoid duplicating addresses. Are you against that somehow? Should we generate our knot.conf's from templates anyway...?
Daniel Lublin
@quite
And another question, regarding knot's template. Does non-default templates inherit from the special default template?
Daniel Lublin
@quite
Regarding the default template, other templates does not seem to inherit it.
Daniel Salzman
@salzmdan
You are correct. Templates are exclusive. But you can override template settings in the zone section.
Daniel Salzman
@salzmdan
As for the remote from acl, I understand the idea but there are some slight differences between the items. Anyway, I will reconsider possible simplification.
Daniel Lublin
@quite
should i add an issue?
Daniel Salzman
@salzmdan
It's not necessary (I have my private TODO list :-) ). But if you wish
Daniel Lublin
@quite
ah just tid anyway :) heh there yes
Daniel Salzman
@salzmdan
:-)
Micah
@micah_gitlab
I'm at 2.9.1-1 and when I push out a zone file change, and I do /usr/sbin/knotc zone-reload, I'm told in the logs error: [myzone.] zone event 'load' failed (semantic check) but if I run knotc zone-check on the zone, I dont get any complaints