Messages

I can now see where the required URL string is supposed to come from.  Looking at this page:

https://docs.cpanel.net/cpanel/domains/dynamic-dns/

The generation of the dynamic dns entry in cpanel creates the unique URl required to update the DNS record.  I think my problem is that my hosting provider (HostPapa) does not seem to have this feature enabled in cPanel.

So I guess that is that...   :(

Thanks for posting the image with your setup.  It helps enormously.  I'm hoping you are able to supply a little more detail.

I can see from the image, the string required for the server field needs more than a host name and port.  It seems to need a command of some sort encoded into the URL.  I've been searching for days for documentation on the cpanel command syntax without any joy.

Thanks for any further assistance you can provide.

I'm trying to migrate my current OPNsense gateway to new hardware.  Dell Wyse 5070 thin clients can be had pretty cheap at present and support expansion to a second ethernet port.  All up I landed the hardware for less than $100.

The problem I am having is routing traffic via the second ethernet port.

The second ethernet port is connected via an M.2 slot.  Both the onboard and the second ethernet port are Realtek 8111F chipsets. 

To confirm the second ethernet port works at a hardware level, I did a desktop Linux install (Fedora) and connected the second ethernet port.  A network connection was made, a DHCP lease obtained and the correct DNS settings discovered.  All working as expected.  This to me indicates there are no problems with the ethernet port, the M.2 card or the BIOS settings.

I next tried to install FreeBSD 13.2.  I configured the onboard ethernet port (re0) during the installation and again had no problems in getting a DHCP lease and discovering the DNS service.  This implies to me there is no problem with the driver BSD is using for the Realtek 8111 chipset.

If I repeat the install process for BSD and configure the second (M.2) ethernet port, it fails to obtain a DHCP lease.  The interface (re1) is reported as up, but it can't route traffic through it (?), or it cannot discover the router advertisement(?).  TBH, I have no idea what is going on. 

I think I've identified this is not an OPNsense issue but more an issue in the underlying FreeBSD operating system.  So maybe I'm posting in the wrong place, but I figure the people most likely to have tried to use a second M.2 NIC are more likely here than on a FreeBSD forum.

Thanks in advance for any assistance or direction to take with this problem!

You mean a SRV record? https://en.wikipedia.org/wiki/SRV_record

Thanks for the reply.  Looking at that wikipedia entry, I think so.  I found an old reddit thread which suggests srv records can be added to the "Custom Option" in Unbound DNS.  I'm not seeing that option any more in the general settings page of the Unbound DNS Service so things may have changed. 

At least though it gives me a search term to investigate further.  I find half the battle is working out what the thing you need is called.  I want to say I used to be able to create an alias in Sophos UTM...

I too wanted to be able to drop in the OPNSense gateway as a working replacement rather than a work in progress, so I understand where you are coming from. 

My solution was to configure offline.  It did mean I missed the benefits cookiemonster highlights with the auto sensing of inputs if booted up when plugged in.  I just manually assigned my interfaces in the console screen.

After that, I connected a device (in may case a raspberry pi) over ethernet to the gateway to create a stand alone network of 2 devices (gateway and pi) and used the browser to complete the config over a few days to point where no one else in the household would notice anything when it was switched in to replace the router.  I much preferred that to feeling time pressured because the internet was down and word with friend was unavailable!   ;)

I'd like to not have to remember all the port numbers for the various docker containers running on a single host.  Ideally I'd be able to type "service.server.domain" and have the DNS be able to resolve that to ip:port.

For example if my wiki is exposed as port 9082 on the server fred at hb.com at 192.168.1.100, it would be great to just type wiki.fred.hb.com and have that resolve to 192.168.1.100:9082 rather than having to remember which port the wiki uses.

Is there a way to achieve this or am I dreaming?