What I Learnt

Starting from fresh instal of Linux Mint Cinnamon with Wine and Bottles installed. Updated to latest install and all packages up to date.

HTML Servers

Subsequently learnt that would have run a Python html server.

Installed and configured Apache2 as server. This gave a test page which appeared to be working. This would not work as https. Identidfied as Insecure.

To install TLS certs for SSL needed to install sequel server and php, get certs and put them in correct locations.

Installed “LAMP” Linux, Apache2, MySQL, (php)

Domain

Got Domain from Names.co. Did not need wild card domain as damain and www.domain covered by simple domain name. Started of with Private IP address and did not add www Domain (corrected later). Worked as http but not https but this was only on my local network (my wifi).

Got certs for SSL (Secure Sockets Layer creates a safe, encrypted link between a web browser and a server) from ZeroSSL. 2 certs and a key. Took ager to get working as there where directry layere called certs (ssl\certs\certs\) duh.

Tried everything to no avail. Spent hrs sorting port forwarding and IP address.

Routers, Host Controllers and Domain Name Servers

Are all different (I know – duhhh).

Obviousely needed fixed IP for lap top. DHCP changes IP every time(ish). Tried fixing on the lap top but this created loads of problems as router DHCP still did its own thing. Lappy was saying Fixed IP 192.168.1.249, but Deco was showing 192.168.1.99. Could not get deco to update to fixed \iP address. Finally realied that EE router was the DHCP. Fixwed IP in router set lap top to Automatic. Everything came back into line at 192.168.1.249.

DCHP assigns IP address with first 3 digs as router. Last dig is 1-100 for automatic IP. Use higher number for assigning static IP address. Does not appear to be true on our router.

Took a while to differntiate DNS and DHCP in my head. Found out that DNS can be quite flakey so don’t specify secondy and tershry from same source. Found :

208.67.222.222 – Cisco

1.1.1.1 – Cloudflare

8.8.8.8 – Gougle

IP Address

Lappy (Server) will have both a public and private IP address.

To access lappy web server, you have to tell your router to forward all requests received on the public IP address to your private server IP address.

From “What is my IP address

Public IP Address

IPV4 95.147.231.123

IPV6 2a00:23c8:e613:c801:f2d5:505f:900f:b46a

Update \|||adress in \Names.\Co to Public IP address.

EE do not allocate static public IP addresses. Set up a free or low-cost DDNS (Dynamic DNS) service. This links your changing public IP address to a permanent web domain name so you can always access your home network remotely.

Installed Technitium

Created zone for Domain. Set records as instructed.

Created DNSSEC records and CAA Policys.

Slow to update internet so not sure at what point it started working but now working.

Need to give it a few days to make sure it stays working. Then

Things Still Left to Sort Out.

Names.co still has (varriable) public IP address.

Technitium records are not yet published. DNLookUp.io showing DNSSEC and CAA problems.

Can ping laptop and domain on Wifi. Can’t ping from the internet.

Where am I? - I think :

192.168.1.99 is an internal IP address allocated by EE Hub. This laptop is set to 192.168.1.249 (fixed IP address) in EE hub then everything set to automatic in LM.

The internet only deals with external IP address. External IP is 95.147.231.123. Changed IP address in names.co to this. Nothing seems to have changed.

Although internal IP is static, EE will not allow static external IPs for domestic customers although external IP seldom changes. To overcome this need to use a dynamic DNS (DDNS). Installed Technitution. I think this replaces Apache2 as the http server.

using

DNSChecker there appears tobe a security problem (DNSSEC) within Technitium. Followed instructions on how to configure DNSSEC.