The first link in my previous comment is literally gmail returning an error because no ptr...
Edit: your page is about setting up dkim while using their workspaces. You don't control their ptrs.
Edit2: notice they don't talk about SPF or dmarc on that page either. SPF has been require for google as well for a while and dmarc is highly recommended though not strictly required.
That has it's own name... CG-NAT. Thus why people are responding to you as if you're wrong. As you wrote it you are wrong though. But there's still answers like argo tunnels (if you are okay with cloudflare) and other similar solutions.
Your local college might do networking courses/stuff. honestly though, there's enough youtube content out there by really respected people that you can likely just get away with that... Start with words/topics you see mentioned in this thread. Example, search youtube for DDNS... and if that video says something you don't understand search for that topic. Eventually you'll have a decent grasp on what's going on.
Then you have a SIP trunk provider that doesn't validate domain ownership... I'd like to know that companies name if you don't mind sharing. They're stupidly rare to the point that I view it as a unicorn situation.
Edit: To clarify, I've tried finding such providers and failed for several years... They all want PTR validation for "security"
PTR lookups has been a thing for email servers for a very long time... "used to work fine" would have been early 2000's as far as I can remember.
PTR is de facto requirement for over 20 years now. So unless you're talking about pre-turn of the century, not really... email servers haven't worked without PTRs for a very long time.
I had to look it up, but Yahoo and AOL implemented PTR checks in 2003-2004. Gmail had it out of the box in 2004.
Can you run a server without it? Yes... and it will work with any other server that doesn't mandate valid PTR records. But no major consumer email server has supported receiving mail from a PTR-less server for 20+ years now. So you're not going to be able to email basically anyone from your server.
Well yes... but if you're goal to self-host is to control your data, it's a bit counter productive to use those relays services that inject that problem right back into your setup again.
Edit: I'm not necessarily arguing... just putting the information out there that the services exist, but might not be a good fit.
Yeah that's another option as well... Services like dynu.com or smtp2go.com do exist... but you have to pay for them and there is a risk that the service can open/read your messages.
You can't assign a PTR record without a static address though. No ISP will do PTR that follows DHCP updates. I haven't had issues with my leased IPs from my ISP (Through Centurylink). Though a year back I moved and haven't been able to get a leased IP from my new provider... I have to relay my emails now through a service, that has been a pain in the ass. But now we head into anecdotal nonsense.
And yes, we're talking about hosting services. We're in Selfhosted... and the OP is talking about publishing their ghost website... a webserver.
But no, email is otherwise not an issue. I've been selfhosting a couple of personal domains for over a decade without issue. I also host several email services for work... no issues outside of some of our clients who want us to use their SMTP servers which apparently suck. But not my issue if their IT fails at managing it.
Edit: DHCP -> PTR auto follow is a thing that exists though... which just makes it sad that ISPs don't support it. I literally have hostname updates available and used inside of my own network. Just another sad day when pro-sumers are able to implement RFCs (RFC 2136, opnsense pushes updates to my internal DNS servers) better than ISPs.
No it does not. You need an active PTR record for email to work for most of the major carriers (Gmail, O365, etc...). Many providers will just outright block consumer IP ranges as well.
You cannot host an email server on dynamic addresses.
Edit: And you've edited in the VoIP part of your comment... Same thing there, you need PTR and such for those services to work well... Which generally can't be assigned to dynamic addresses.
You only need a static address for hosting email or VoIP.
You can do just about everything else with DDNS (dynamic DNS). However with DDNS, you will have downtime until the DDNS update takes effect and propagates to clients. This can be seconds... or hours. Depends on the DDNS service and TTLs that they set and how quickly your script/DDNS client works to push the update out.
You should check how often your address changes and check how quickly your DDNS solution pushed the update out. If it's 10 seconds every 10 months, you will likely find that perfectly acceptable. If it's an hour every other sunday... maybe not. But only you will know how much downtime you can tolerate.
I always will take static IP personally. But it's not technically required and you can work around it if you want to save the 10-15$/month.
Edit: You could also argo tunnel if you're okay using cloudflare. But I don't think that answer is particularly in scope of the question. But just in case it's useful to someone out there I'm adding this edit. Doesn't fix the PTR requirement for Email and VoIP stuff though.
Alexander Zwinck, Mesa County, Arizona, Sheriff’s Office
Only the "Transcript" does. So no... you can't say that's what he said. The transcript itself shows the indication of who's talking and stating that the officer is from Arizona is in the indicator... not the actual spoken words...
This is literally PBS feeding their shit through an LLM and not checking the results.
That makes the whole article suspect for me... Anyone writing news for their locale, will know at the very least what fucking counties belong to their state... For something like that to make it through the author and the copy editor is wild.
Notice: Transcripts are machine and human generated and lightly edited for accuracy. They may contain errors.
Ah... There it is... It's probably audio fed to an LLM... This whole transcript is likely an AI hallucination.
Edit: and this is from PBS? Come on... Don't give the right even more reason to cancel you. FFS.
I read this too... This post should be removed for bullshit. It may be the original articles headline... but the headline is complete and utter garbage.
The first link in my previous comment is literally gmail returning an error because no ptr...
Edit: your page is about setting up dkim while using their workspaces. You don't control their ptrs.
Edit2: notice they don't talk about SPF or dmarc on that page either. SPF has been require for google as well for a while and dmarc is highly recommended though not strictly required.