Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You have to tell the dns servers where to "point" the name. So there is really no way you could totally do it yourself. You need to update your "dns record" attached to the registered name in order to have the name map to an IP and propagate to all the various DNS servers. </p> <p>If you registered the dns with someone like godaddy or similar, there are very easy to use tools on those sites to update the records for your name. In these records you can also map subdomains, email names, and various other things.</p> <p>But mostly there is nothing you can do with just the servers config by iteself. :)</p> <p>Edit:</p> <p>Well the DNS thing is more of an internet thing than something about your machine/server or the tools intsalled. There are really only 3 components:</p> <p>1) IP config of your machine (and your ISPs config), where you already have a working IP number and its serving pages, so thats fine.</p> <p>2) The specific webserver config, where from what you said you only have one site, so you dont need to add or configure any "vitual servers".</p> <p>3) And whats left is the DNS to IP mapping, which happens outside of your machine, as thats the resposibility of other servers in a sort of co-operative age old DNS server thing. A browser asks for the IP of your server using the DNS name form the DNS servers, and then and only then will send things to your machine.</p> <p>Having plesk in and of itself doesnt give you anyting but more software on your machine. Where did you buy the name from? You need to ask them to update the DNS record or ask where you can update the DNS record to point to your IP. And specifcally ask if installing plesk will somehow give you access to edit the DNS record. The DNS record is elsewhere and not on your machine, and is one of the only things, for the things that matter to you, that you dont control specifically from your machine and isnt on your machine itself.</p> <p>Sorry you are having trouble; hope this rather generic info helps. Its normally very very easy these days to map the DNS to the IP, they should be able to do it for you or give you extremely specific instructions. :)</p> <p>A simple test that should work from any kind of machine, windows, unix or otherwise, is to use "ping" or "tracert" or "traceroute" to get a free lookup and indication of where the dns name is currently pointing to. Like: <code>ping my.name.com</code> <code>tracert my.name.com</code></p> <p>Then you should see the IP number that the record currently points to in the wild. With tracert or traceroute you can also get an idea of where that server its pointing to lives, despite whatever you may be being told right or wrong.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload