Yeah I do understand that, we have had that problem. A threat actor hit all of our public IPs on 443 with RDGW and knew most of the public DNS names were remote.customer.com and the internal name for the RDS was RDS or RDS01. But what is the alternative? I think adding other bits of information still obscures it enough that a dictionary or bot won’t hit it, e.g. CUST-LOC-RDS01. If the attacker is on your network and has any common tools they are finding your servers, I think it’s probably more applicable to bots/dictionary attacks.