Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
I switched from Google Domains to Namecheap and found that they have a non-standard requirement for A records (they require an "@" A record) that messed up the transfer. Godaddy, dyndns, and Google Domains use regular zone transfer tables and I thought those entries were all I needed. Nope. I finally emailed support and they told me what was wrong within 24 hours. But meanwhile, my site was down for that time.
I suppose if you worked with one of the companies they partner with and use the automated templates to generate a new entry, it would work out fine. But I was transferring an existing domain. I know better now. But I put this out to warn others.
That's pretty weird, there's no reason to require any DNS record beyond those they have to provide (SOA and NS). You shouldn't have to add an A record if you don't need one.
Was this just a snafu during transfer or is the A record a permanent requirement?