added 144 characters in body
Source Link
Simon Hayter
  • 32.4k
  • 7
  • 54
  • 112

You need to tell Enjin Guild Hosting the domain that you have registered then you can [follow there online tutorial][1][follow there online tutorial][1]. Basically you don't need to worry about the folder part at your domain registrar because of the way hosting works. All you should concern yourself with is the IP address of the server at Enjin. At the Enjin, there server will have what we call a virtual host file. It'll look something like:

<VirtualHost *:80>
    DocumentRoot /home/enjin-username/public_html
    ServerName www.example.com
</VirtualHost>

If you take a look at the DocumentRoot your notice this is the local path of your hosting package, the virtual host file will use www.example.com in local path of /home/enjin-username/public_html.

You're hosting root directory is /home/enjin-username/public_html. If you make a sub folder with something like a WordPress e.g /home/enjin-username/public_html/wordpress then this would be accessible via www.example.com/wordpress/ if you don't want a sub folder then you move the contents of WordPress into /home/enjin-username/public_html and then delete the WordPress folder.

Basically your DNS at the domain registrar translate the domain to ip address, then at the server it will take a look at what 'domain' was requested and then path the local path seamlessly all in the background.

Please note that /public_html and username in the path is purely speculation, some hosts use /www, /httpdocs, /public_html and so on.

To confuse things even further there's actually two ways you can set this up. If you plan to use email and other servers then simply change your name servers at your domain registrar to the name servers that Enjin has setup,

The name servers at Enjin are:

ns1.enjin.com
ns2.enjin.com
ns3.enjin.com
ns4.enjin.com

If you plan to use your domain with a third party such as external emails then the more preferable route would be to use the A records method.

Enjin's A records and Cnames are:

Root A Record (@): 199.83.134.131
CNAME record (www): app.enjin.com.

I recommend for ease simply just change the name servers. [1]: https://support.enjin.com/hc/en-us/articles/200375754-Using-custom-domains-Tutorial

You need to tell Enjin Guild Hosting the domain that you have registered then you can [follow there online tutorial][1]. Basically you don't need to worry about the folder part at your domain registrar because of the way hosting works. All you should concern yourself with is the IP address of the server at Enjin. At the Enjin, there server will have what we call a virtual host file. It'll look something like:

<VirtualHost *:80>
    DocumentRoot /home/enjin-username/public_html
    ServerName www.example.com
</VirtualHost>

If you take a look at the DocumentRoot your notice this is the local path of your hosting package, the virtual host file will use www.example.com in local path of /home/enjin-username/public_html.

You're hosting root directory is /home/enjin-username/public_html. If you make a sub folder with something like a WordPress e.g /home/enjin-username/public_html/wordpress then this would be accessible via www.example.com/wordpress/ if you don't want a sub folder then you move the contents of WordPress into /home/enjin-username/public_html and then delete the WordPress folder.

Basically your DNS at the domain registrar translate the domain to ip address, then at the server it will take a look at what 'domain' was requested and then path the local path seamlessly all in the background.

Please note that /public_html and username in the path is purely speculation, some hosts use /www, /httpdocs, /public_html and so on.

To confuse things even further there's actually two ways you can set this up. If you plan to use email and other servers then simply change your name servers at your domain registrar to the name servers that Enjin has setup,

The name servers at Enjin are:

ns1.enjin.com
ns2.enjin.com
ns3.enjin.com
ns4.enjin.com

If you plan to use your domain with a third party such as external emails then the more preferable route would be to use the A records method.

Enjin's A records and Cnames are:

Root A Record (@): 199.83.134.131
CNAME record (www): app.enjin.com.

I recommend for ease simply just change the name servers. [1]: https://support.enjin.com/hc/en-us/articles/200375754-Using-custom-domains-Tutorial

You need to tell Enjin Guild Hosting the domain that you have registered then you can [follow there online tutorial][1]. Basically you don't need to worry about the folder part at your domain registrar because of the way hosting works. All you should concern yourself with is the IP address of the server at Enjin. At the Enjin, there server will have what we call a virtual host file. It'll look something like:

<VirtualHost *:80>
    DocumentRoot /home/enjin-username/public_html
    ServerName www.example.com
</VirtualHost>

If you take a look at the DocumentRoot your notice this is the local path of your hosting package, the virtual host file will use www.example.com in local path of /home/enjin-username/public_html.

You're hosting root directory is /home/enjin-username/public_html. If you make a sub folder with something like a WordPress e.g /home/enjin-username/public_html/wordpress then this would be accessible via www.example.com/wordpress/ if you don't want a sub folder then you move the contents of WordPress into /home/enjin-username/public_html and then delete the WordPress folder.

Basically your DNS at the domain registrar translate the domain to ip address, then at the server it will take a look at what 'domain' was requested and then path the local path seamlessly all in the background.

Please note that /public_html and username in the path is purely speculation, some hosts use /www, /httpdocs, /public_html and so on.

To confuse things even further there's actually two ways you can set this up. If you plan to use email and other servers then simply change your name servers at your domain registrar to the name servers that Enjin has setup,

The name servers at Enjin are:

ns1.enjin.com
ns2.enjin.com
ns3.enjin.com
ns4.enjin.com

If you plan to use your domain with a third party such as external emails then the more preferable route would be to use the A records method.

Enjin's A records and Cnames are:

Root A Record (@): 199.83.134.131
CNAME record (www): app.enjin.com.

I recommend for ease simply just change the name servers. [1]: https://support.enjin.com/hc/en-us/articles/200375754-Using-custom-domains-Tutorial

added 144 characters in body
Source Link
Simon Hayter
  • 32.4k
  • 7
  • 54
  • 112

You need to tell Enjin Guild Hosting the domain that you have registered then you can follow there online tutorial[follow there online tutorial][1]. Basically you don't need to worry about the folder part at your domain registrar because of the way hosting works. All you should concern yourself with is the IP address of the server at Enjin. At the Enjin, there server will have what we call a virtual host file. It'll look something like:

<VirtualHost *:80>
    DocumentRoot /home/enjin-username/public_html
    ServerName www.example.com
</VirtualHost>

If you take a look at the DocumentRoot your notice this is the local path of your hosting package, the virtual host file will use www.example.com in local path of /home/enjin-username/public_html.

You're hostinghosting root directory is /home/enjin-username/public_html. If you make a sub folder with something like a WordPress e.g /home/enjin-username/public_html/wordpress then this would be accessible via www.example.com/wordpress/ if you don't want a sub folder then you move the contents of WordPress into /home/enjin-username/public_html and then delete the WordPress folder.

Basically your DNS at the domain registrar translate the domain to ip address, then at the server it will take a look at what 'domain' was requested and then path the local path seamlessly all in the background.

Please note that /public_html and username in the path is purely speculation, some hosts use /www, /httpdocs, /public_html and so on.

To confuse things even further there's actually two ways you can set this up. If you plan to use email and other servers then simply change your name servers at your domain registrar to the name servers that Enjin has setup,

The name servers at Enjin are:

ns1.enjin.com
ns2.enjin.com
ns3.enjin.com
ns4.enjin.com

If you plan to use your domain with a third party such as external emails then the more preferable route would be to use the A records method.

Enjin's A records and Cnames are:

Root A Record (@): 199.83.134.131
CNAME record (www): app.enjin.com.

I recommend for ease simply just change the name servers. [1]: https://support.enjin.com/hc/en-us/articles/200375754-Using-custom-domains-Tutorial

You need to tell Enjin Guild Hosting the domain that you have registered then you can follow there online tutorial. Basically you don't need to worry about the folder part at your domain registrar because of the way hosting works. All you should concern yourself with is the IP address of the server at Enjin. At the Enjin, there server will have what we call a virtual host file. It'll look something like:

<VirtualHost *:80>
    DocumentRoot /home/enjin-username/public_html
    ServerName www.example.com
</VirtualHost>

If you take a look at the DocumentRoot your notice this is the local path of your hosting package, the virtual host file will use www.example.com in local path of /home/enjin-username/public_html.

You're hosting root directory is /home/enjin-username/public_html. If you make a sub folder with something like a WordPress e.g /home/enjin-username/public_html/wordpress then this would be accessible via www.example.com/wordpress/ if you don't want a sub folder then you move the contents of WordPress into /home/enjin-username/public_html and then delete the WordPress folder.

Basically your DNS at the domain registrar translate the domain to ip address, then at the server it will take a look at what 'domain' was requested and then path the local path seamlessly all in the background.

You need to tell Enjin Guild Hosting the domain that you have registered then you can [follow there online tutorial][1]. Basically you don't need to worry about the folder part at your domain registrar because of the way hosting works. All you should concern yourself with is the IP address of the server at Enjin. At the Enjin, there server will have what we call a virtual host file. It'll look something like:

<VirtualHost *:80>
    DocumentRoot /home/enjin-username/public_html
    ServerName www.example.com
</VirtualHost>

If you take a look at the DocumentRoot your notice this is the local path of your hosting package, the virtual host file will use www.example.com in local path of /home/enjin-username/public_html.

You're hosting root directory is /home/enjin-username/public_html. If you make a sub folder with something like a WordPress e.g /home/enjin-username/public_html/wordpress then this would be accessible via www.example.com/wordpress/ if you don't want a sub folder then you move the contents of WordPress into /home/enjin-username/public_html and then delete the WordPress folder.

Basically your DNS at the domain registrar translate the domain to ip address, then at the server it will take a look at what 'domain' was requested and then path the local path seamlessly all in the background.

Please note that /public_html and username in the path is purely speculation, some hosts use /www, /httpdocs, /public_html and so on.

To confuse things even further there's actually two ways you can set this up. If you plan to use email and other servers then simply change your name servers at your domain registrar to the name servers that Enjin has setup,

The name servers at Enjin are:

ns1.enjin.com
ns2.enjin.com
ns3.enjin.com
ns4.enjin.com

If you plan to use your domain with a third party such as external emails then the more preferable route would be to use the A records method.

Enjin's A records and Cnames are:

Root A Record (@): 199.83.134.131
CNAME record (www): app.enjin.com.

I recommend for ease simply just change the name servers. [1]: https://support.enjin.com/hc/en-us/articles/200375754-Using-custom-domains-Tutorial

Source Link
Simon Hayter
  • 32.4k
  • 7
  • 54
  • 112

You need to tell Enjin Guild Hosting the domain that you have registered then you can follow there online tutorial. Basically you don't need to worry about the folder part at your domain registrar because of the way hosting works. All you should concern yourself with is the IP address of the server at Enjin. At the Enjin, there server will have what we call a virtual host file. It'll look something like:

<VirtualHost *:80>
    DocumentRoot /home/enjin-username/public_html
    ServerName www.example.com
</VirtualHost>

If you take a look at the DocumentRoot your notice this is the local path of your hosting package, the virtual host file will use www.example.com in local path of /home/enjin-username/public_html.

You're hosting root directory is /home/enjin-username/public_html. If you make a sub folder with something like a WordPress e.g /home/enjin-username/public_html/wordpress then this would be accessible via www.example.com/wordpress/ if you don't want a sub folder then you move the contents of WordPress into /home/enjin-username/public_html and then delete the WordPress folder.

Basically your DNS at the domain registrar translate the domain to ip address, then at the server it will take a look at what 'domain' was requested and then path the local path seamlessly all in the background.