nsd: hannover.freifunk.net zonefile missing

freifunkh / ansible

Here we store all Ansible roles and configs used for Freifunk Hannover.

MIT License

7 stars 3 forks source link

nsd: hannover.freifunk.net zonefile missing #202

Closed 1977er closed 1 year ago

1977er commented 3 years ago

Since - I don't know when - the hannover.freifunk.net zonefile is not generated (anymore). Currently a copy from zones_old directory fills the gap.

@Manawyrm Help. ;-)

Manawyrm commented 3 years ago

Yeah, that's an interesting problem :) It probably only surfaced when I renamed "zones" to "zones_old" (to make sure everything was cleared), but nsd seems to have cached everything until your restart recently.

Here's the interesting part: There's no zonefile/configuration for hannover.freifunk.net anywhere in the Ansible :smile: There is a configuration to use zonefile: "hannover.freifunk.net.zone", this specific zonefile in the nsd-config, but the file is nowhere to be found.

Should we just convert the hannover.freifunk.net.zone file to some ansible/yaml lines?

1977er commented 3 years ago

Yes, please. I failed trying to do so. ;-)

Manawyrm commented 3 years ago

I've created a pull request (and I've deployed it on ns1).

1977er commented 3 years ago

Ah, when I tried to do so, I missed to purge hannover from dns_authoritative_external.

1977er commented 3 years ago

@Manawyrm

@ IN MX 10 mail should be @ IN MX 10 mail.ffh.zone. Currently mail delivery is broken.

Why do these end up in hannover.freifunk.net?

; Statische Hosts (aus der Ansible-Konfiguration)
pve-ffnw.hannover.freifunk.net. IN  AAAA 2001:678:978:ff01::1
sn01.s.hannover.freifunk.net. IN  AAAA 2001:678:978:ff01::2
rdns.hannover.freifunk.net. IN  AAAA 2001:678:978:ff01::3

1977er commented 1 year ago

Nothing to do here (anymore). Closing.