It is possible to have to access to a subdomain and not the doamin itself. For eg you have access to rope.example.com but if you try example.com, then you connection time out. Any explanations, thanks
For such topics you may want to lurk on ServerFault [1] and SuperUser [2] to get more detailed information. If you gave an example of your intended end goal it might help answer the question as this could be interpreted as a DNS, cloud or web server question.<p>The title of your post should probably be something along the lines of "Ask HN: Subdomain limitations and capabilities?". If you click edit you can change it.<p>[1] - <a href="https://serverfault.com/" rel="nofollow">https://serverfault.com/</a><p>[2] - <a href="https://superuser.com/" rel="nofollow">https://superuser.com/</a>
yes very possible, and very common.<p>you are asking for something akin to root/elevated privilege
access. do you own, or control rope.example.com, or example.com ? because that would help access a lot.