| |
| ▲ | ffsm8 6 hours ago | parent [-] | | Because mine didn't I instead used a generic ddns and set a cname on my own domain to that. Works like a charm too. Kinda breaks MX records so don't so it if you wanna receive emails on that domain, too | | |
| ▲ | rovr138 5 hours ago | parent [-] | | > Kinda breaks MX records so don't so it if you wanna receive emails on that domain, too Is the CNAME on the root of the domain, @? | | |
| ▲ | ffsm8 2 hours ago | parent [-] | | In my case yes, because I did not care about breaking email delivery to that domain (it's a novelty domain pointing to my residential IP address, (surname-home.tld) which I use exclusively for my selfhosted
Services | | |
| ▲ | rovr138 an hour ago | parent [-] | | Oh perfect Just wanted to ask since I’ve been bitten by that. I do something similar, but I have them all under <service>.home.<example.com> But that’s because I do have resources outside. Just helps my mental model to name space them. |
|
|
|
|
