mediaaustin
Member
Deliverability Nerd
- Joined:
- Jul 2024
- Posts:
- 276
- From:
- Austin, US
That cable photo gave me physical pain. For what it's worth, I've seen worse in email infrastructure closets, but those usually hide behind locked doors.
Your SPF record for the domain in your signature is misconfigured, by the way. V=spf1 with no mechanism after the IP range. You're going to hit blocklists if you send from that server.
Congratulations on the table though. Full routes from a basement is a genuine achievement.
SPF, DKIM, DMARC — holy trinity ✉️
SamAlvi
Member
Self-Host Everything
- Joined:
- Jun 2024
- Posts:
- 188
- From:
- Portland, US
Next: actual upstream instead of tunnel. Baby steps.
You've got BIRD running already. Add a docker compose for your looking glass, maybe a reverse proxy for secure access. I run my entire stack — DNS, mail, monitoring — from two Time4VPS VMs and a closet server just like yours.
The cable mess is temporary motivation. You'll fix it when you add the second upstream and actually need to trace which fiber goes where. Ask me how I know.
my cloud. my rules. my 3AM alerts.
SamAlvi
Member
Self-Host Everything
- Joined:
- Jun 2024
- Posts:
- 188
- From:
- Portland, US
Without SR-IOV I was losing packets
This is why I run Proxmox on my closet box and pass the whole NIC through to the BIRD VM. No hypervisor scheduling games. My compose stack lives on a separate VM with a cheap Realtek for management.
Your 0.8ms to Cloudflare is impressive for a tunnel. What provider are you using for the endpoint?
my cloud. my rules. my 3AM alerts.