“Do not go gentle into that good night.”
Flying in registration and resolution planes since 1997.
@RareBird15 @selfhost @selfhosting @selfhosted @mastoblind @main “but how can I do that when my domain doesn’t exist yet?” I am not sure to understand your specific context, but do note that you can configure any nameserver to be authoritative on any fictional name you want, and make sure it replies properly. It doesn’t matter (won’t be used by anyone) until the *delegation* (from parent) is being set, which happens at the registrar where you define nameservers for the domain.
@jpl @RareBird15 @selfhost @selfhosting @selfhosted @mastoblind @main But technically you can totally register a domain without nameservers. Or later remove nameservers totally from a registered domain. Registration and resolution are separate things, even if they intersect, at least at the registrar when setting nameservers (sent to the registry which in turn publish them)
@ocean @RareBird15 Might want to read the fine prints. Cloudflare will require you to use their nameservers. You can’t choose the DNS provider you wish. Maybe fine, maybe not, but has to be taken into account, I was too often in threads where people complain to late that their domain is now tied to Cloudflare nameservers.
@RareBird15 @virtuous_sloth @selfhost @selfhosting @selfhosted @mastoblind @main There is nothing “weird” in having 2 separate companies, one for registration, one for hosting/DNS provider. IF your nameservers are Vultr.com ones currently, this is where you should edit your zone. You can only edit records at your DNS provider, where the domain is registered has no influence on how it gets resolved.
@ocean I am not judging myself if this is a problem or not, as it is subjective and depends on a whole context, so it will differ for each case. Just saying “be aware of that, and the consequences of it, make sure that don’t get against the goals you have set”. Basically, “buyers beware”.