Problem Description
Good news: we still have internet.
Bad news is that my private domain CNAME to freedombox stopped working, and this is the one we use all the time.
Freedombox gets a FreedomBox Dynamic DNS name as xxx.fbx.one (A record)
My domain is set up with freedombox.yyyy.net CNAME xxx.fbx.one
xxx.fbx.one is working just fine, but freedombox.yyyy.net is no longer resolving as xxx.fbx.one address. My FreedomBox tells me that its FQDN address for freedombox.yyyy.net is 127.0.1.1
CORRECT EXTERNAL IP ADDRESS for xxx.fbx.one as A record
dig xxx.fbx.one: CORRECT EXTERNAL IP ADDRESS
host 127.0.1.1: 1.1.0.127.in-addr.arpa domain name pointer freedombox.yyyy.net
I’m not sure where to go with this - I’m guessing this is a wrinkle in the recent named changes. Any idea on how to address this would be appreciated.
Given that my “Domain (regular)” is a CNAME for the dynamic domain it feels like I should remove that from regular and put that in Dynamic Domain, but I’ll wait to do this because that’s not going to work with all the other Dynamic Domain plumbing.
I think I’m an edge case. My use case is something like this:
I have my own domain and I have an IP address that can change. I want to provide FreedomBox services through my own domain name, but cannot automatically configure a DNS A record for my FreedomBox because its external address changes over time and my DNS provider does not offer such a tool.
FreedomBox stores domains names provided as static domains (“Domains” in Names) in /etc/hosts file with a address map to 127.0.1.1. This was changed somewhat in a recent release. The end result is that all the static domains declared in the Names app will resolve to 127.0.1.1 within FreedomBox for all programs that include resolutions /etc/hosts.
Since the programs configured to use the static domains want to resolve to localhost ultimately, it is not incorrect to resolve it to 127.0.1.1. One advantage is that these domain resolutions work even when Internet connectivity is not available and those apps will continue to work.
Are you facing problems with any problems with this approach?
Correct, clients are on the internal network which is a shared connection. The other network interface is DHCP client to the ISP connected directly to the ISP modem.
Interestingly, I’m on the outside right now and nearly the reverse appears to be true. Coming in from internet to the primary connection (DHCP client to ISP):
I haven’t fully tested this situation. Sorry about this. It clearly looks like this approach needs to be changed. I will prepare a fix for this soon and it should be available in the next release.
I wonder why xxx.fbx.one was not reachable from outside. This needs separate investigation. Could you please check that DNS is pointing to same IP as your static domain name?
