probably a millennial IT team...
The URL still won't resolve unless I place the DNS server's name in the lookup command. Then I get an IP. But, that still points me back to the NameCheap "parked" default webpage.
I also get 2 sets of DNS Name Servers when searching the URL. So, I think the people trying to figure out how to properly register their IP addresses are just confused.
I have 8 domains being served through CloudFlare. If you have your webserver set up properly, the reverse-proxy not only works flawlessly, but changes are super easy, and updating the CloudFlare settings can be automated. The domains on CloudFlare never expire. The service is free if you don't want all the bells and whistles.
If you ever looked at reverse-proxies and didn't look into CloudFlare, you should. I use the dynamic DNS service "DuckDNS.org" to access my one server IP, then use CloudFlare to reference that IP address for all my domains. My server then looks at the full URL to determine which virtual web server to process the request. Nice thing about CloudFlare is the free SSL certificate for each of my domains, so encryption and site identification are properly handled in the browser -- no Insecure Connection or Unable to Verify this Site messages.

I have 2 webservers: one at home for development and personal stuff, and one on a leased server that has a fixed IP address.
Since my home IP is set by the RoadRunner DHCP server, I use DuckDNS for that (dynamic IP). The CloudFlare records just point to my account name on duckdns.org.
The IP for the leased server doesn't change, so I have that IP in my CloudFlare records for those website URLs.
Amateurs .... the Left can't meme -- nor do IT.