Also, I would argue that the ability to run ANAME at your own infrastructure
might drive less people to the “managed DNS” land or allow them to migrate
away without a significant loss of functionality.
One way or another, ANAME-like behaviour became defacto industry standard
and we need to have a
On 11/05/2019 15:54, Dave Lawrence wrote:
I have a related question ... is allowing only targets on their own
infrastructure currently a limitation most such providers have?
I don't know about "most", but certainly some. See e.g. the attached
message posted here 2018/06/25.
Ray
--- Beg
Brian Dickson writes:
> Have any "closed system" implementations of non-standard apex-CNAME
> hacks, committed publicly to neutral ANAME operations, presuming
> ANAME as currently envisioned? I.e. If each such provider will
> ONLY support ANAME with targets on their own infrastructure, I don't
> t
