Nameserver

Introduction

There is a single nameserver hostname ns1 on the Infra network. DNSmasq has been used to setup this DNS cache and local DNS server. It ahs been more useful than I first thought it would be as now I don't have to do much if another host is added to the network. Update NS1 has now been replaced by a container called ctns1

Add New Records

There is a few bash scripts that set new DNS / PTR records and print out a list of DNS entries. At present each host has two files to represent it's DNS name, one is for seaoffate.local and the other is for seaoffate.net. It made more sense to have a separate file for each host than to have one big one that has all entries. At the beginning the .net domain didn't exist so everything was at .local, now that seaoffate.net is running the .local could be removed but there will probably be times when it is needed again for testing so it will remain for the time being.

One thing that needs to be done at some point is to merge the two scripts that add new hosts so that it adds a single entry for both seaoffate.net and seaoffate.local to make sure that they don't get out of sync. Probably best to delete all of the file entries and start again so that there is a single file for both for each host with DNS & PTR records for .local and .net. ===Update=== The scripts have now been replace on ctns1 with new scripts that create a file with PTR and DNS records for hostname.seaoffate.local, hostname.seaoffate.net and hostname.seaoffate.uk

Co Location

The DNS name seaoffate.uk has also been bought but nothing has been done about it yet. It could be used as a separate set of webservers to co locate the existing. In this scenario there would be these webservers here with the .net TLD and another set with .uk as a TLD on a paid for hosting company. As an alternative we could have the remote host host similar websites but with a slightly different name and have Cloudflare point the alternate DNS names at the remote host, eg wiki.seaoffate.net and wiki.seaoffate.uk are both pointing at this webserver and wikir.seaoffate.net and wikir.seaoffate.uk are pointing at the remote host. Either system would work and both would be relatively simple to setup. The biggest problem that I see is that they would need several DBs and several Vhosts/webservers, these are not insurmountable obstacles but they would need a fair bit of storage especially if nextcloud and photo websites are to be co-located, nextcloud will probably be not located elsewhere as it would be cost prohibitive, it would be nice to have photo co-located but it will need at least 100gb storage so probably not, maybe if TimeVPS were used it could be done reasonably cheaply