From f4eecfe0821baabbbfcdee8b3c507a6985637aec Mon Sep 17 00:00:00 2001 From: forestcat-admin Date: Sat, 23 May 2026 22:40:09 +0200 Subject: [PATCH 1/7] fix setup instructions to use uv run --- docs/guides/writing-documentation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/writing-documentation.md b/docs/guides/writing-documentation.md index fd2681f..15fe254 100644 --- a/docs/guides/writing-documentation.md +++ b/docs/guides/writing-documentation.md @@ -38,7 +38,7 @@ Once you have cloned the repository, you can just edit a file in the [`docs/`](h ```shell uv venv uv pip install -r docs_requirements.txt - mkdocs serve + uv run mkdocs serve ``` When adding new content, you can use one of the templates below to get started: From 4574dbf4ba9ec144253625f67eeffdd86659ac51 Mon Sep 17 00:00:00 2001 From: June Date: Sat, 23 May 2026 22:40:17 +0200 Subject: [PATCH 2/7] secrets(role): introduce secrets role for storing secrets Allows storage of secrets to then be referenced in other places. The motivation was storing WireGuard secrets for systemd-networkd. --- inventories/chaosknoten/hosts.yaml | 2 + inventories/external/hosts.yaml | 2 + inventories/z9/hosts.yaml | 2 + playbooks/deploy.yaml | 7 ++++ roles/secrets/README.md | 24 ++++++++++++ roles/secrets/defaults/main.yaml | 1 + roles/secrets/meta/argument_specs.yaml | 6 +++ roles/secrets/tasks/main.yaml | 53 ++++++++++++++++++++++++++ 8 files changed, 97 insertions(+) create mode 100644 roles/secrets/README.md create mode 100644 roles/secrets/defaults/main.yaml create mode 100644 roles/secrets/meta/argument_specs.yaml create mode 100644 roles/secrets/tasks/main.yaml diff --git a/inventories/chaosknoten/hosts.yaml b/inventories/chaosknoten/hosts.yaml index c737f34..1c3f84e 100644 --- a/inventories/chaosknoten/hosts.yaml +++ b/inventories/chaosknoten/hosts.yaml @@ -291,3 +291,5 @@ msmtp_hosts: renovate_hosts: hosts: renovate: +secrets_hosts: + hosts: diff --git a/inventories/external/hosts.yaml b/inventories/external/hosts.yaml index 435a9bf..5d0f9d4 100644 --- a/inventories/external/hosts.yaml +++ b/inventories/external/hosts.yaml @@ -22,3 +22,5 @@ infrastructure_authorized_keys_hosts: ansible_pull_hosts: hosts: status: +secrets_hosts: + hosts: diff --git a/inventories/z9/hosts.yaml b/inventories/z9/hosts.yaml index 1b37c59..eab3880 100644 --- a/inventories/z9/hosts.yaml +++ b/inventories/z9/hosts.yaml @@ -57,3 +57,5 @@ ansible_pull_hosts: light: waybackproxy: yate: +secrets_hosts: + hosts: diff --git a/playbooks/deploy.yaml b/playbooks/deploy.yaml index ad866cc..b7ce104 100644 --- a/playbooks/deploy.yaml +++ b/playbooks/deploy.yaml @@ -6,6 +6,13 @@ tags: - base_config +- name: Ensure secrets deployment on secrets_hosts + hosts: secrets_hosts + roles: + - secrets + tags: + - secrets + - name: Ensure systemd-networkd config deployment on systemd_networkd_hosts hosts: systemd_networkd_hosts roles: diff --git a/roles/secrets/README.md b/roles/secrets/README.md new file mode 100644 index 0000000..ec04665 --- /dev/null +++ b/roles/secrets/README.md @@ -0,0 +1,24 @@ +# Role `secrets` + +Allows storing the given secret contents in the configured files. + +## Supported Distributions + +Should work on Debian-based distributions. + +## Required Arguments + +None. + +## Optional Arguments + +- `secrets__secrets`: List of secrets. + Defaults to the empty list (`[ ]`). +- `secrets__secrets.*.name`: (File)name for the secret (in the `/etc/ansible_secrets` directory). +- `secrets__secrets.*.content`: The secret content to store. +- `secrets__secrets.*.owner`: The owner of the secret file. + Defaults to `root`. +- `secrets__secrets.*.group`: The group of the secret file. + Defaults to `root`. +- `secrets__secrets.*.mode`: The mode of the secret file. + Defaults to `0640`. diff --git a/roles/secrets/defaults/main.yaml b/roles/secrets/defaults/main.yaml new file mode 100644 index 0000000..882d77b --- /dev/null +++ b/roles/secrets/defaults/main.yaml @@ -0,0 +1 @@ +secrets__secrets: [ ] diff --git a/roles/secrets/meta/argument_specs.yaml b/roles/secrets/meta/argument_specs.yaml new file mode 100644 index 0000000..2562138 --- /dev/null +++ b/roles/secrets/meta/argument_specs.yaml @@ -0,0 +1,6 @@ +argument_specs: + main: + options: + secrets__secrets: + type: list + required: false diff --git a/roles/secrets/tasks/main.yaml b/roles/secrets/tasks/main.yaml new file mode 100644 index 0000000..8923397 --- /dev/null +++ b/roles/secrets/tasks/main.yaml @@ -0,0 +1,53 @@ +- name: validate secret configs + ansible.builtin.validate_argument_spec: + argument_spec: "{{ required_data }}" + provided_arguments: + config: "{{ item }}" + loop: "{{ secrets__secrets }}" + loop_control: + label: "{{ item.name }}" + vars: + required_data: + config: + type: dict + required: true + options: + name: + type: str + required: true + content: + type: str + required: true + owner: + type: str + required: false + default: root + group: + type: str + required: false + default: root + mode: + type: str + required: false + default: "0640" + +- name: ensure secrets directory exists + ansible.builtin.file: + path: "/etc/ansible_secrets" + state: directory + owner: root + group: root + mode: "0750" + become: true + +- name: ensure secrets are present + ansible.builtin.copy: + content: "{{ item.content }}" + dest: "/etc/ansible_secrets/{{ item.name }}" + mode: "{{ item.mode | default('0640') }}" + owner: "{{ item.owner | default('root') }}" + group: "{{ item.group | default('root') }}" + become: true + loop: "{{ secrets__secrets }}" + loop_control: + label: "{{ item.name }}" From 603d3fb6f4436d7e4a67532c1c37ae8be6c60248 Mon Sep 17 00:00:00 2001 From: Stefan Bethke Date: Sun, 24 May 2026 00:12:50 +0200 Subject: [PATCH 3/7] Update machine SMTP mail sending config --- inventories/z9/group_vars/all.sops.yaml | 8 ++++---- inventories/z9/group_vars/all.yaml | 4 ++-- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/inventories/z9/group_vars/all.sops.yaml b/inventories/z9/group_vars/all.sops.yaml index 81f6ce7..bc4c3f1 100644 --- a/inventories/z9/group_vars/all.sops.yaml +++ b/inventories/z9/group_vars/all.sops.yaml @@ -1,5 +1,5 @@ metrics__chaos_password: ENC[AES256_GCM,data:seOU504dZ9K21+NK1MBf9isee2L2rueP6Bl0F66R,iv:ZtQ516gzJQSSgvOOAzPF9MuarXqHSLXy37/9z85KoQ8=,tag:dIal6OxPLli+7DbzhjNFsA==,type:str] -msmtp__smtp_password: ENC[AES256_GCM,data:NlA0aN2SeP4Tl3G1Qg0v/SAicY8p6ZMdQPihGfFTohAmajNvteFJ19ELPezwTz7hia0oU7lwo3DfKuu92WMIKA==,iv:s44piFZZrF6ZYmkGqsBFjTUNiHc4IhBXJATRPETsAI8=,tag:Sj0Q/Y4hT4Hs1JxVOO/8xQ==,type:str] +msmtp__smtp_password: ENC[AES256_GCM,data:FAih8FghRYDx3QGFCjKoJ8Zq0TkeCIx4n1jTx4/sASgECqvucg==,iv:8NDn3wj/bXsbHbuce3ycJTBVWde6XAVxv4NuMUkMbIM=,tag:jeE2b0i/8JPtguLYQvdV1w==,type:str] sops: age: - recipient: age1j0876shgsn7f2thxh9kx9x5uwnh45z6sy2jlk2qz5jhgedm26g5srn9kax @@ -38,8 +38,8 @@ sops: cnlBL29XQVlsL1ZCenBIYTQ3S3JxQjQKq09vbn1XOC1jIXDpv+ThFMk9k7SyYknr MBJRBp/0PrKBo/Xk+RCSWSLjgali5Cc8KTjDTJyBG8rFzzvLIazBRg== -----END AGE ENCRYPTED FILE----- - lastmodified: "2026-03-30T19:28:25Z" - mac: ENC[AES256_GCM,data:IGai2CmOI46XHekSSpLgQxEGw9zIf7Z10K8eQyi0rJGha5ZOjz9jP1VIhC9m6LjRxOKJuEPV2NvBACC5tBUCGwW1Ym31spcROjjtCzyqRF8E7R02oNMIQ32Byb9ij56/Trl5UOBOML+WOdeaq8r74kEfIyZBCx/tfGENuTlBqd4=,iv:Gjzb/IW6WcRL3c4ShOH46cVed4duTs1BFygYnGd4d4Y=,tag:DZAH6tA92mFP5Yo9b4kmkg==,type:str] + lastmodified: "2026-05-23T22:10:20Z" + mac: ENC[AES256_GCM,data:JbnKG1qyAkvFDXr2iHu+gk7nRjedmm+dEK8vBFW5YzndWE4QKoYWeaqRHBk7wdWO9kpZgU2rFiu4Be+ikotoMS8jKAcd5wWSrWtSreaZxxiD2TWMWX8HwPtETnYe0rjrEZ3kPcUj4QPyNTphfbH3ARLjthedRXNF70NDc+DIpAY=,iv:4LN3oslWUWqoY3rQNVDSmlJn1o0c8JQELzsWd5btn7Y=,tag:c8X1q9XMMUkXed93j9C6ww==,type:str] pgp: - created_at: "2026-05-20T02:08:49Z" enc: |- @@ -212,4 +212,4 @@ sops: -----END PGP MESSAGE----- fp: 41FFAF3D519CF5C039FBD8414BCC213729AF0E49 unencrypted_suffix: _unencrypted - version: 3.12.1 + version: 3.12.2 diff --git a/inventories/z9/group_vars/all.yaml b/inventories/z9/group_vars/all.yaml index 4f2b313..20a4e7f 100644 --- a/inventories/z9/group_vars/all.yaml +++ b/inventories/z9/group_vars/all.yaml @@ -12,8 +12,8 @@ ansible_pull__timer_randomized_delay_sec: 30min msmtp__smtp_host: cow.hamburg.ccc.de msmtp__smtp_port: 465 msmtp__smtp_tls_method: smtps -msmtp__smtp_user: any@hosts.z9.ccchh.net -msmtp__smtp_from: "{{ inventory_hostname }}@hosts.z9.ccchh.net" +msmtp__smtp_user: machine@ccchh.net +msmtp__smtp_from: "{{ inventory_hostname }}@cchh.net" alloy_config_default: | prometheus.remote_write "default" { From dd48a9d519a0855b0ff27b6656e4bb56c0d8b88f Mon Sep 17 00:00:00 2001 From: lilly Date: Sun, 24 May 2026 00:26:51 +0200 Subject: [PATCH 4/7] bring guide about new chaosknoten VMs into doc structure --- ...m.md => create-a-new-vm-on-chaosknoten.md} | 32 +++++++++++++------ 1 file changed, 22 insertions(+), 10 deletions(-) rename docs/guides/{new-chaosknoten-vm.md => create-a-new-vm-on-chaosknoten.md} (86%) diff --git a/docs/guides/new-chaosknoten-vm.md b/docs/guides/create-a-new-vm-on-chaosknoten.md similarity index 86% rename from docs/guides/new-chaosknoten-vm.md rename to docs/guides/create-a-new-vm-on-chaosknoten.md index ad10af3..79195d8 100644 --- a/docs/guides/new-chaosknoten-vm.md +++ b/docs/guides/create-a-new-vm-on-chaosknoten.md @@ -1,18 +1,22 @@ --- -title: New Chaosknoten VM -summary: How to Create a New VM on Chaosknoten +title: Create a new VM on Chaosknoten --- -# New Chaosknoten VM +!!! success "Goal" -This guide outlines the steps to take for creating a new VM (`myservice`) on Chaosknoten. It might also act as a useful reference for other environments however. + Create a new VM on our Chaosknoten Server with DNS Name, Firewalling and network config. -## IP and DNS +## 1. Reserve an IP Address -Decide on what kind of network configuration the VM needs. In this guide we assume a public v6 and a non-public v4 in the v4-NAT network. If you have special requirements, refer to TODO for more information on the different kinds of networks available on Chaosknoten. +Decide on what kind of network configuration the VM needs. +In this guide we assume a public v6 and a non-public v4 in the v4-NAT network. +If you have special requirements, refer to TODO for more information on the different kinds of networks available on Chaosknoten. 1. Allocate a fresh [v6 in NetBox in the v4-NAT v6-network](https://netbox.hamburg.ccc.de/ipam/prefixes/47/ip-addresses/). - The _hostname_ should be the full FQDN, like: `myservice.hosts.hamburg.ccc.de` + +## 2. Configure DNS + 2. Add a new `AAAA` record pointing to the chosen v6 to the [`hamburg.ccc.de` zone](https://git.hamburg.ccc.de/CCCHH/ansible-infra/src/branch/main/resources/chaosknoten/auth-dns/zones/hamburg.ccc.de.zone). It should look something like this: ``` @@ -23,7 +27,7 @@ Decide on what kind of network configuration the VM needs. In this guide we assu ansible-playbook -i inventories/chaosknoten playbooks/deploy.yaml -l auth-dns -t knot ``` -## VM Creation +## 3. Create A VM in Proxmox Now that we have a v6, let's create a new VM on Chaosknoten. @@ -49,6 +53,9 @@ Now that we have a v6, let's create a new VM on Chaosknoten. ``` ssh -J chaos@router.hamburg.ccc.de chaos@myservice.hosts.hamburg.ccc.de ``` + +## 4. Enter VM into NetBox + 4. Finally add the VM to NetBox 1. First [add the VM itself](https://netbox.hamburg.ccc.de/virtualization/virtual-machines/). - The _Name_ should be the hostname of the VM, so e.g. `myservice`. @@ -63,7 +70,7 @@ Now that we have a v6, let's create a new VM on Chaosknoten. 4. Finally assign the IP address created earlier in NetBox to the just created interface by going into the _Assignment_ section of the IP address configuration. - Also check _Make this the primary IP for the device/VM_ while doing so. -## Ansible +## 5. Enroll the VM in ansible Next up the VM should be added to the Ansible configuration management. While Ansible can and should be used to configure various services and configuration options, this section focuses on the basic setup to be done. @@ -88,7 +95,7 @@ Next up the VM should be added to the Ansible configuration management. While An Feel free to commit at this point before continuing with further configuration. -## Further Setup +## 6. Configure the VM further for your needs With the basic configuration now done, the VM can be set up further. Here are some helpful pointers: @@ -96,4 +103,9 @@ With the basic configuration now done, the VM can be set up further. Here are so - Secrets should be stored using SOPS, see: [SOPS: Storing Secrets](./sops-storing-secrets.md) - Guidance on setting up a web service can be found in the [Web Service](./web-service.md) guide. -Afterward you should also take care of setting up monitoring for the newly configured service, see: [Monitoring: Gatus](./monitoring-gatus.md) +Afterward you should also take care of setting up monitoring for the newly configured service, see: [Monitor a new service with Gatus](./monitor-a-new-service-with-gatus.md). + +## Closing Up + +This section is optional but if there's any way for the reader to verify their goal has been achieved, you should mention it here. + From b287b367e40b08fd45e37a55f711b7128d745148 Mon Sep 17 00:00:00 2001 From: forestcat-admin Date: Sun, 24 May 2026 02:29:55 +0200 Subject: [PATCH 5/7] add documentation-structure --- .../documentation-structure.md | 84 +++++++++++++++++-- 1 file changed, 78 insertions(+), 6 deletions(-) diff --git a/docs/concepts-and-configurations/documentation-structure.md b/docs/concepts-and-configurations/documentation-structure.md index 0ca89d3..dc4919f 100644 --- a/docs/concepts-and-configurations/documentation-structure.md +++ b/docs/concepts-and-configurations/documentation-structure.md @@ -5,12 +5,84 @@ summary: >- How our documentation is organized and what we do to balance ease of writing and understanding. --- -!!! info "ToDo" +!!! info "Info" - This section needs updating + If youre looking for a hands-on approach on how documentation is to be written you can find a [guide](../guides/writing-documentation.md) explaining the process. If youre unsure how to start you can find [templates](../guides/writing-documentation.md#3-addedit-your-markdown-file) there aswell. -- Docs should be english -- Guides are for step-by-step things - - Guides always have a "Goal" explicitly formulated -- Concepts and Configuration aim to make readers understand something in detail +## General Rules +Rules are formatting and writing decisions that apply to every document. Their goal is to provide a concise style across the whole documentation to keep the text easy to follow. +- All documents written in this project should be written in **english** to maximize the compatability across readers. +- The documentation structure is intended to be followed, while not being **enforced** to keep a low entry barier for documentation authors. +- Use features like _Admonitions_ given by markdown and the theme whenever they can help by increasing the readability and outlining important parts. For instructions on how to use these theme specific features please refer down to the _MkDocs shadcn_ documentation in the References section. + +## Document Scope +The scope for a concept document should be set to define responsibility and set boundaries to where that document applies. Especially lining out which services are affected by it. + +!!! note "Example" + + The scope for this document is aiming to convey the base concepts on how to structure concepts and configurations in this documentation. To provide high readability and a project wide concise structure that authors and readers can rely on. + +## Structuring Concepts + +!!! note "Goal" + + The goal for a concept is to provide the reader with a structured detailed explanation about an abstract concept, conveying why this concept was choosen and how it is intended to be used. + +### Describing the Concept +This section is a summary to give the reader a quick overview about the concept answering following questions: + +- What is this concept about? +- Why is this concept needed? +- What does this concept do? + +### Explaining the Concept +This section should be an in depth explanation about the concept, explaining the concept as detailed as needed for the reader to be able to transfer it into an implementation. The usage of graphs and diagrams is advised when they can help the reader to understand the concept better. + +### Referencing additional Sources +This section should include sources to other documentations, concepts and hand-on guides which the reader can look up to futher explore the defined concept. + + +## Structuring Configurations + +!!! note "Goal" + + A configuration document is intended to provide the reader with examples and best practices for configuring a specific item. It focuses on the technical implementation rather than an abstract concept. + +### Describing the Configuration +This section should give the reader a quick overview which configuration files are being described. + +### Providing the Configuration +Here should the author provide configuration sections or full templates. The configurations don't have to be fully complete, theyre rather a more structured view on which options are important and what to watch out for. + +### Discussing Authors Thoughts +A discussion why the author choose which configuration options and what to watch out for. Best practices should be taught here. This section can also link to outside sources. + +### Referencing Documentation +Here the author should provide upstream documentation which includes configuration options and further explanations why and how they are used. + + +## Structuring Guide + +!!! note "Goal" + + A guide intends to provide a hands-on approach to the reader which they can follow step-by-step to archive the guides defined goal. A good example for a guide can be found at [Writing Documentation](../guides/writing-documentation.md). + +### Defining the Goal +A guide should always have a goal defined in the beginning, using the _Admonition_ for a success box is highly advised. An example for a goal box is shown below: + +```markdown +!!! success "Goal" + How to setup, write its baseline documentation in ansible and deploy a service. +``` +### Instructing the Reader +A guide should always have numbered instruction steps which are easy to follow. Important notices and information should written in _Admonitions_ as direct notices from the author to the reader. Dangerous steps or options should use a `danger` Admonition. + +### Closing Up +A guide should be finished with steps and facts that can be checked by the reader to ensure that the guide worked as intended and all steps are completed correctly. + +## References +Here you can find useful documentation regarding writing documentation: + +- [MkDocs](https://www.mkdocs.org/user-guide/): This is the official mkdocs documentation, although it mostly explains configuring the mkdocs instance rather than explaining the usage. +- [MkDocs shadcn](https://asiffer.github.io/mkdocs-shadcn/): This is our theme for MkDocs which has its own syntax and quircks which can help writing more readable documentation From 8892f9e3bbe8f59e1d68694ef0a3dbf4c909eeac Mon Sep 17 00:00:00 2001 From: forestcat-admin Date: Sun, 24 May 2026 02:55:58 +0200 Subject: [PATCH 6/7] clarify the usage of the document scope and the differences between concept, configuration and guide --- .../documentation-structure.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/docs/concepts-and-configurations/documentation-structure.md b/docs/concepts-and-configurations/documentation-structure.md index dc4919f..30d2ebe 100644 --- a/docs/concepts-and-configurations/documentation-structure.md +++ b/docs/concepts-and-configurations/documentation-structure.md @@ -16,13 +16,20 @@ Rules are formatting and writing decisions that apply to every document. Their g - The documentation structure is intended to be followed, while not being **enforced** to keep a low entry barier for documentation authors. - Use features like _Admonitions_ given by markdown and the theme whenever they can help by increasing the readability and outlining important parts. For instructions on how to use these theme specific features please refer down to the _MkDocs shadcn_ documentation in the References section. -## Document Scope -The scope for a concept document should be set to define responsibility and set boundaries to where that document applies. Especially lining out which services are affected by it. +## Defining a Document Scope +The scope for a document should be set to define responsibility and set boundaries to where that document applies. Especially lining out which services are affected by it. It **does not** need to be defined explicitly in the text, but should be kept in mind while writing. !!! note "Example" The scope for this document is aiming to convey the base concepts on how to structure concepts and configurations in this documentation. To provide high readability and a project wide concise structure that authors and readers can rely on. +We decide in this documentation between concepts, configurations and guides. Their separation should be clearified with folowing list: + +- **Concept:** A concept includes an abstract definition about a specific structure while not going into implementation details. +- **Configuration:** A configuration can be a follow up of a concept, explaining the specific implementation in a given environment. +- **Guide:** A guide is a step-by-step hands-on instruction for the reader to follow along. It can reference concepts and configurations. + + ## Structuring Concepts !!! note "Goal" From 7832978ff732208f2f29f04ef446c7c51076c6d1 Mon Sep 17 00:00:00 2001 From: lilly Date: Sun, 24 May 2026 11:55:31 +0200 Subject: [PATCH 7/7] update ccchh.net dns zone after club proxmox migration --- .../chaosknoten/auth-dns/zones/ccchh.net.zone | 135 ++++++++---------- 1 file changed, 63 insertions(+), 72 deletions(-) diff --git a/resources/chaosknoten/auth-dns/zones/ccchh.net.zone b/resources/chaosknoten/auth-dns/zones/ccchh.net.zone index bb5c16f..0360f81 100644 --- a/resources/chaosknoten/auth-dns/zones/ccchh.net.zone +++ b/resources/chaosknoten/auth-dns/zones/ccchh.net.zone @@ -1,73 +1,64 @@ -$ORIGIN . -$TTL 900 ; 15 minutes -ccchh.net IN SOA auth-dns.hamburg.ccc.de. noc.hamburg.ccc.de. ( - 2026042801 ; serial - 86400 ; refresh (1 day) - 7200 ; retry (2 hours) - 3600000 ; expire (5 weeks 6 days 16 hours) - 7200 ; minimum (2 hours) - ) - NS auth-dns.hamburg.ccc.de. - NS ns.vie.ccc.de. +$TTL 60 ; 1 minutes +@ SOA auth-dns.hamburg.ccc.de. noc.hamburg.ccc.de. ( + 1 ; serial (overwritten by knot automatically) + 86400 ; refresh (1 day) + 7200 ; retry (2 hours) + 3600000 ; expire (5 weeks 6 days 16 hours) + 60 ; minimum/negative ttl (1 minute) + ) -$ORIGIN ccchh.net. -aes A 212.12.48.125 -club-assistant AAAA 2a07:c481:1:d0::a -;_acme-challenge.club-assistant CNAME d50ad73a-f82d-4244-87f0-6f5195b37d21.auth.acmedns.hamburg.ccc.de -club-assistant.z9 AAAA 2a07:c481:1:d0::a -;_acme-challenge.club-assistant.z9 CNAME 0efa74d1-7dcd-478b-bdc5-5b76d0f07642.auth.acmedns.hamburg.ccc.de -esphome AAAA 2a07:c481:1:d0::66 -esphome.z9 AAAA 2a07:c481:1:d0::66 -zigbee2mqtt A 185.161.129.132 -light AAAA 2a07:c481:1:d0::16 -_acme-challenge.light CNAME e59f55ee-9013-469d-a146-a159721b6fea.auth.acmedns.hamburg.ccc.de. -light.z9 AAAA 2a07:c481:1:d0::16 -_acme-challenge.light.z9 CNAME 3bc9e7ce-03dd-4533-a059-b5d38407eaa5.auth.acmedns.hamburg.ccc.de. -light-werkstatt AAAA 2a07:c481:1:d0::16 -_acme-challenge.light-werkstatt CNAME f408acc0-d9f5-4525-bb01-28938e3bb7d0.auth.acmedns.hamburg.ccc.de. -mailserver-endpoint A 82.165.121.46 -ns1 A 185.161.129.133 -send-only-mail MX 10 send-only-mailserver - TXT "v=spf1 mx -all" -send-only-mailserver A 82.165.121.46 -send-only-mailserver-access A 185.161.129.132 -thinkcccore0 AAAA 2a07:c481:1:f2::3 -thinkcccore0.z9 AAAA 2a07:c481:1:f2::3 -thinkcccore1 AAAA 2a07:c481:1:f2::4 -thinkcccore1.z9 AAAA 2a07:c481:1:f2::4 -opnsense AAAA 2a07:c481:1:f2::1 -opnsense.z9 AAAA 2a07:c481:1:f2::1 -pbs AAAA 2a07:c481:1:f2::4 -thinkcccore2 AAAA 2a07:c481:1:f2::5 -thinkcccore2.z9 AAAA 2a07:c481:1:f2::5 -thinkcccore3 AAAA 2a07:c481:1:f2::6 -thinkcccore3.z9 AAAA 2a07:c481:1:f2::6 -miniscccore0 AAAA 2a07:c481:1:f2::9 -miniscccore0.z9 AAAA 2a07:c481:1:f2::9 -uptime-kuma A 185.161.129.132 -status AAAA 2a07:c481:1:ce::a -status.z9 AAAA 2a07:c481:1:ce::a -wiki A 212.12.48.125 -hmdooris-ccu A 10.31.208.202 -buba A 10.31.211.137 -buba.z9 A 10.31.211.137 -dooris AAAA 2a07:c481:1:d0::1c -_acme-challenge.dooris CNAME 37caae1f-b77f-4eb1-aa71-dc3f7ed24360.auth.acmedns.hamburg.ccc.de. -waybackproxy A 10.31.208.99 -yate A 10.31.208.12 -staubiv2 A 10.31.210.233 -staubiv2.z9 A 10.31.210.233 -; Mail: hosts.z9.ccchh.net -hosts.z9 MX 10 cow.hamburg.ccc.de - TXT "v=spf1 mx -all" -dkim._domainkey.hosts.z9 TXT ("v=DKIM1;k=rsa;t=s;s=email;" - "p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvsdypQ/tlrzto5KVP" - "5o7tEblXK/hOVRFB683uODzo26XTFMSRGjumMuo/tej59GMePdUu0uIsdq8hfj8" - "ot0R2OQNazdyp4NW4TUWfFGJ4S2f6LR3lE3I5Lw7fHiYHz0GnCGTqZIItkHK+xQ" - "i5Fdhwd1YbFJtO0XiZ0jY5w6pvny6pEH8WaKX85rEmz2zqCtpiYPRPmoK/Tn+rV" - "2e8fVioMRm9W8E4PU42WLds66qOkFR0KjKIavE6y7JahESEoVGcVnSPdtMOX0Ln" - "KbSMQNrTvNbBoPdLYvNaXOw7TmVPKjDV+FRCIIdK+m0fL82/vm5jPBvDr5+WlM1" - "xV/P/KlSnQIDAQAB") -$ORIGIN send-only-mail.ccchh.net. -_dmarc TXT "v=DMARC1;p=quarantine;" -key._domainkey TXT "v=DKIM1;k=rsa;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDqduM4+SQ+IQ2uAxbjFkd+0hAjohTgT3nM76jyrWGHJ8TizNU2PGkta0NjCq+m9VLBZUjIJphW2vrnlJsnN0JkGAdoLBL3Qs0kShT6V+xsxslZG2KHApihnJUp34tPSMES+aTnD+jEPGyxFLeoiK+3gywNhCGalHSQ+G88Z2n59wIDAQAB" +@ NS auth-dns.hamburg.ccc.de. +@ NS ns.vie.ccc.de. + + +; +; Network-Infrastructure +; +rt-wan A 185.161.129.134 + AAAA 2a07:c481::1:2 +sw-rack-1 A 10.89.213.2 + AAAA 2a07:c481:1:36::2 +sw-rack-2-poe A 10.89.213.3 + AAAA 2a07:c481:1:36::3 +sw-main-1 A 10.89.213.4 + AAAA 2a07:c481:1:36::4 +sw-main-2 A 10.89.213.5 + AAAA 2a07:c481:1:36::5 +sw-shop-1 A 10.89.213.6 + AAAA 2a07:c481:1:36::6 +sw-shop-2-poe A 10.89.213.7 + AAAA 2a07:c481:1:36::7 +sw-shop-3-poe A 10.89.213.8 + AAAA 2a07:c481:1:36::8 +pve01 A 10.89.213.11 + AAAA 2a07:c481:1:36::11 +pve02 A 10.89.213.12 + AAAA 2a07:c481:1:36::12 +pve03 A 10.89.213.13 + AAAA 2a07:c481:1:36::13 +pve04 A 10.89.213.14 + AAAA 2a07:c481:1:36::14 +pbs A 10.89.213.15 + AAAA 2a07:c481:1:36::15 +unifi A 10.89.213.21 + + +; +; Club-Services +; +xr18 A 172.31.200.21 + +;club-assistant AAAA 2a07:c481:1:d0::a +;;_acme-challenge.club-assistant CNAME d50ad73a-f82d-4244-87f0-6f5195b37d21.auth.acmedns.hamburg.ccc.de +;esphome AAAA 2a07:c481:1:d0::66 +;zigbee2mqtt A 185.161.129.132 +;light AAAA 2a07:c481:1:d0::16 +;_acme-challenge.light CNAME e59f55ee-9013-469d-a146-a159721b6fea.auth.acmedns.hamburg.ccc.de. +;light-werkstatt AAAA 2a07:c481:1:d0::16 +;_acme-challenge.light-werkstatt CNAME f408acc0-d9f5-4525-bb01-28938e3bb7d0.auth.acmedns.hamburg.ccc.de. +;hmdooris-ccu A 10.31.208.202 +;buba A 10.31.211.137 +;dooris AAAA 2a07:c481:1:d0::1c +;_acme-challenge.dooris CNAME 37caae1f-b77f-4eb1-aa71-dc3f7ed24360.auth.acmedns.hamburg.ccc.de. +;yate A 10.31.208.12 +;staubiv2 A 10.31.210.233