• https://blog.thelifeofkenneth.com/2019/09/using-catalog-zones-in-bind-to.html
• https://bind9.readthedocs.io/en/latest/chapter6.html#namedconf-statement-catalog-zones
• Since you probably will have multiple servers/ catalog zones, read about how collisions can be handled: https://bind9.readthedocs.io/en/latest/chapter6.html#change-of-ownership-coo (TODO: add support for change of owner ship to script, can be as simple as adding the entries to the end of the output for the catalog file on h2 by including another file)

I want to share this idea as a thank you to the Froxlor community, maybe it helps someone in the future.

Notes:

1. On a Froxlor server ("primary") (called h2) that already has DNS setup:

1.1. Create script that makes the catalog zone.

touch /etc/example-bind/serial
chmod 600 /etc/example-bind/serial
chown root:root /etc/example-bind/serial
nano -w /etc/example-bind/serial

0

touch /etc/example-bind/on_reload_bind9.sh
chmod 700 /etc/example-bind/on_reload_bind9.sh
chown root:root /etc/example-bind/on_reload_bind9.sh
nano -w /etc/example-bind/on_reload_bind9.sh

#!/bin/bash

catalog_name="h2"

####

catalog_file="/etc/bind/catalog.${catalog_name}.example.db"

touch $catalog_file
chown bind:0 $catalog_file
chmod 0644 $catalog_file

serial=$(($(cat /etc/example-bind/serial) + 1))
echo $serial > /etc/example-bind/serial

echo "catalog.${catalog_name}.example.    IN SOA . . $serial 172800 960 3600000 300
catalog.${catalog_name}.example.    IN NS invalid.
version.catalog.${catalog_name}.example.    IN TXT \"2\"
" > $catalog_file

named-checkconf -l /etc/bind/froxlor_bind.conf | awk "{ printf \"%s.zones.catalog.%s.example. PTR %s.\n\",makeZoneEntry(\$1),\"$catalog_name\",\$1 }
function makeZoneEntry( id,  cmd, output ) {
        cmd = \"echo \\047\" id \"\\047 | sha1sum\"
        if ( (cmd | getline output) > 0 ) {
                sub(/ .*/,\"\",output)
        }
        else {
                print \"failed to hash \" id | \"cat>&2\"
                output = id
        }
        close( cmd )
        return output
}" >> $catalog_file

#
systemctl reload bind9

# TODO: hash catalog zone and update serial only when it changes

1.2. Run the script once

/etc/example-bind/on_reload_serial.sh

1.3. Create a TSIG key:

tsig-keygen -a hmac-sha256 catalog.h2.example

This shoud look similar to:

key "catalog.h2.example" {
    algorithm hmac-sha256;
    secret "<YOUR SECRET HERE>";
};

1.4. Create zone file for catalog zone:

touch /etc/bind/example_bind.conf
chmod 760 /etc/bind/example_bind.conf
chown root:bind /etc/bind/example_bind.conf
nano -w /etc/bind/example_bind.conf

key "catalog.h2.example." {
        algorithm hmac-sha256;
        secret "<YOUR SECRET HERE>";
};

zone "catalog.h2.example" {
        type master;
        file "/etc/bind/catalog.h2.example.db";
        allow-transfer   { key "catalog.h2.example."; };
        also-notify { <A SECONADRY IP HERE>; }; # put IPS of your DNS secondaries here
};

1.5. edit /etc/bind/named.conf.local

Add

# ...

include "/etc/bind/example_bind.conf";

bellow the froxlor one

1.6. Test config on primary:

named-checkconf -p
ONLY PROCEED if it doesn't complain about errors, otherwise fix or roll-back changes.

2. On a secondary DNS (could be made with Froxlor or at least Froxlor configs with DNS setup already) (called h3):

2.1

touch /etc/bind/example_bind.conf
chmod 760 /etc/bind/example_bind.conf
chown root:bind /etc/bind/example_bind.conf
nano -w /etc/bind/example_bind.conf

key "catalog.h2.example." {
        algorithm "hmac-sha256";
        secret "<YOUR SECRET HERE>";
};
server <PRIMARY IP HERE> {
        keys { "catalog.h2.example."; };
};

zone "catalog.h2.example" {
        type slave;
        file "catalog.h2.example.db";
        allow-transfer { none; }; # important
        masters { <PRIMARY IP HERE>; };
};

2.2 Modify /etc/bind/named.conf.options

# ...
        allow-transfer { none; }; # important
        
        catalog-zones {
                zone "catalog.h2.example" default-masters { <YOUR PRIMARY IP HERE>; };
        };
};

2.3. Append to /etc/bind/named.conf.local after froxlor one:

# ...

include "/etc/bind/example_bind.conf";

2.4. Test config on secondary:
named-checkconf -p
ONLY PROCEED if it doesn't complain about errors, otherwise fix or rollback changes.

2.5 Restart bind9 on secondary:

systemctl restart bind9

3. Update Settings  » Nameserver settings on primary:

• DNS Server reload command: /etc/example-bind/on_reload_bind9.sh
• IMPORTANT: Either the secondaries must be listed in Nameservers, or their IP must be in AXFR servers (Froxlor has no option for TSIG keys)

We need to create emails from within another php-service on the same machine

For those interested I will share the current scripts we use since a while now as attachment, since it was lots of work and research to get them to that stage for me at least. (I think I even found some pointers for them earlier in the Froxlor forum, not sure though, don't remember).
I know the files are not good and have many flaws and not good practices, but maybe it will help someone for something good.
Please read the rclone and duplicity manual before asking questions (not sure if I have much time to answer them) and don't forget to install the python dependencies (I know on one server it's Python 2 and the other 3, but that's the way it is atm)!

I want to switch us to BorgBackup ( https://www.borgbackup.org/ ) [it supports append-only destinations] and thought about developing a small module for Froxlor.
But I would not want to do that if someone already is working on something like that and close to the finish line (but I currently can't guarantee I will actually do i).
I am not sure what the best way is to start coding a Froxlor module (maybe there's s.th. in the Wiki or Forum I didn't find yet) and to be honest I haven't worked with the Froxlor API at all yet. If someone has pointers regarding these would be appreciated.
Maybe someone else needs something similar and we can work together a bit somehow?

I wanted the GUI (I mean the froxlor admin backend) to support:

• Multiple Backup locations (local, remote), including append only, and with the borg retention control options (though those are quite complicated, maybe I will just allow some commands to be added)
• Backup groups, that are assigned to one or multiple backup locations and have different schedules for content, mail, DB
• Customers can be assigned to a backup group and there can be a default backup group (not sure how to go about global backup atm)

Not sure if I forgot s.th. we need for ourselves but I don't plan to go much beyond that to be honest.

I do not plan to support reverse backups though ("pull mode", where a server connects to the server to backup) and also not backups on squashfs etc, I don't need it and don't consider it reliable.

backup_ssh_remote.py backup.py exclude.txt global_include.txt rclone.py vgs_backup_cron_d_daily

ich habe eine allgemeine Frage zu Froxlor. Ist es erweiterbar, z.B. durch Plugins, Module etc. Und wenn ja, wie funktioniert das? Gibt's irgendwo Beispiele, Doku, etc.? 

Danke und viele Grüße

Debbie

Froxlor ist wirklich eine gut durchdachte und umgesetzte Lösung, aber es gibt auch durchaus häufiger die Situation das man für verschiedene Dienste im Internet einfach mehrere Server braucht. DNS z.b. sollten bei den meißten Domainendungen mindestens 2 verschiedene angegeben werden. Wir haben im Moment das Problem das unser Anbieter (OVH) auf einigen Blacklisten geführt wird, wodurch ich jetzt z.b. zum auslagern der Mailserver so ein feature in Froxlor sehr gut finden würde. Eine API für reinen Webserver, eine für reinen Mailserver.

einen Webservices für die Erstellung von Kunden wäre eine Super Feature 

Kundendaten, Domain  werden über Post übergegeben, Ws gibt Json als Rückgabe.

Ich würde gerne für so eine Feature Maximal 1 Man Tag sponsoren . 

Hat jemand Bock und Zeit dafür ? 

Vg 

Can I create a module which would do this is the answer is no? I have PHP / programming knowledge.

it has been quite some time ago that DynDNS cut off their free offering. I was in need of another solution. Since I'm already using Froxlor for a hosting server it seemed like a natural addition to implement dynamic DNS in Froxlor. Today I want to present this modification to you after it's been in use for several months.

It basically works like this: A user calls http://your-froxlor.com/updateip.php toset a new IP for one of his domains. As soon as the bind configuration is updated the new IP is in DNS and will be returned when resolving the domain.

As with the number of domains and other resources it can be configured how many dynamic domains (domains for which the IP can be updated by calling updateip.php) a user can have. The user can enable the dynamic DNS feature for any of his domains. The IP can also be set through the administrative interface.

Calling the updateip.php script is fairly simple. It supports HTTP authentication and authentication using request parameters. A domain must be set for which the IP will be updated and either an IPv4 or IPv6 address must be provided or the auto-detection feature is used. An example: http://your-froxlor.com/updateip.php?domain=home.my-domain.com&ipv4=1.2.3.4

The dynamically changed IP (either set through the admin interface or by using updateip.php) will be set as the domain's IP instead of the server IP.

When dynamic DNS is enabled for a domain its TTL is set to 1 to ensure changes to the IP propagate quickly.

You can have a look at the code at https://github.com/ServiusHack/Froxlor/tree/dynamic-dns. I've made this post in the hope for any feedback on the feature or the code. If there is some interest in merging this I'm more than happy to fix any issue and make a pull request.

Best Regards

Severin Leonhardt

And i  will plan started in short time.

But i look Yet on froxlor. Maybe better start to make something based on hook system this will be better for many reasons 

• Easiest implementation
• Faster development
• Plug-in system
• All existest futures make be ported to this system

Benefits smallest files and core will be separated not every time all will be parsed if not enabled.

All sorce should be more readable

We can do something based on open source or make something simple to realise this element

What's Your's opinion about this

It only does the one thing at the moment but it should be easily expandable to do more as and when I need to.

- Autologin in Roundcube
- Ticketmeldung bei Prio ?ber SMS

Entsprechende Plugins lassen sich einfach durch einkopieren in ein Verzeichnis aktivieren.

Einzuf?gen sind:

- 1 Datei
- 1 Ordner
- 2 Zeilen Code

Ich suche dazu noch Tester. Wenn jemand Lust hat, m?ge er sich doch gerne hier im Thread melden.

Viele Gr??e,
Lukas

after finished update to the latest version of Froxlor, my system starts up with the following errors.

There was no SysCP before - thats it what google mean about the problem -

System works fine with 0.9.33-rc2. 

Any ideas ?

New to Froxlor but so far I like what I see. So I cloned the repo and made some minor changes to fit what I think would be a more universal need. Basically whenever you create a new user there is a a new git bare repo created in /var/customers/repos/[username].git. It also creates a post-receive hook that checkouts the revision to the working tree (users web root) and chowns it all to www-data. If anyone thinks this may be valuable or interesting let me know and I'll create a patch or however it should be managed.

Thanks!

For who may interest this subject. I've published a rough version of a ruby gem called capistrano-froxlor. It adds Froxlor cli functions to Capistrano 3. This gem does not deploy Froxlor itself. It can be useful if you like to deploy applications to a froxlor machine. We use it for deploying TYPO3 sites, but of it could be used for any application that van run inside a Froxlor domain.

For now it can create or update subdomains and can create databases for a customer. Perhaps more functionality will follow. I'm open for feature- or merge requests. 

Kind regards,

Pim

https://rubygems.org/gems/capistrano-froxlor

https://github.com/mipmip/capistrano-froxlor

nXri_pub.tar.gz