Binding to agency domain name - Revision history

I shaletin at 12:31, 28 November 2020

2020-11-28T12:31:00Z

I shaletin at 12:17, 28 November 2020

2020-11-28T12:17:37Z

I shaletin: Created page with "To associate the domain name of an agency or company with the Websky system, add a "CNAME" type record in the settings on the DNS server and specify the base name of the Websk..."

2020-11-28T12:16:40Z

Created page with "To associate the domain name of an agency or company with the Websky system, add a "CNAME" type record in the settings on the DNS server and specify the base name of the Websk..."

New page

To associate the domain name of an agency or company with the Websky system, add a "CNAME" type record in the settings on the DNS server and specify the base name of the Websky server for it.

First, select which domain name will be the main one for the booking website.

* If you own a domain site.ru and already have a working website on it which should not be affected and which should not be bound to the booking system, you can create a subdomain (third level domain), for example, booking.site.ru, and link this subdomain to the Websky server free of charge.

* If you own site.ru domain and want to tie Websky booking system to it, we recommend you to use www.site.ru as the main domain name and set redirect (order redirect service) from site.ru domain to www.site.ru.

This scheme will look like this:

[[File:CNAME_shema.png| Recommended connection scheme for the agency domain]].

Create a "CNAME" record using the target server name "sys.nemo.travel." (point at the end is mandatory). Fill in the fields Hostname/Nickname and Value/Destination (field names may be different for hosts).

{| class="wikitable" style="width: 500px".
|-
| colspan="3" | Example 1 - subdomain binding www.example.com.
|-
| www
| CNAME
| sys.nemo.travel.
|-
| colspan="3" | Example 2 - domain binding example.com
|-
| @
| CNAME
| sys.nemo.travel.
|}

Now the "CNAME" record points to the Websky server. Remember that it may take up to 24 hours to distribute information on changes in DNS settings over the Internet.

Now, when you go to (www.)example.com user will be served by Websky server.

Do not forget to specify the selected primary domain name in the "Site Management" → "Domains and protocols" in the "Domain name to download settings" field. If the domain name is in Cyrillic form, it should be written to [http://ru.wikipedia.org/wiki/Punycode Punycode].

'''Attention!''' Websky employees do not make changes to the file ''.htaccess'.<br>.
Nemo does not provide information about the server OS and similar information through a technical support request.
Access requisites to the hosting account are not issued. Nemo appeals to his own system administrators.<br>
.htaccess is also not available.

== Setting up redirect on the example of Ru-center registration service ==

After entering your personal account on the website [http://www.nic.ru http://www.nic.ru], select "Order new services" → "Redirection" in the menu. [https://www.nic.ru/manager/add_redirection.cgi https://www.nic.ru/manager/add_redirection.cgi] On the page, type the domain from which requests will be redirected to the main domain. In this case requests from site.ru will be redirected to www.site.ru.



On the next page do not check the box for automatic change of DNS servers.

Then specify the redirection rule as in the screenshot below.



Confirm the service order.



If it is required that secure connection requests are also redirected, then after creating a rule for the protocol ''http://'', you must also create a similar rule for the protocol ''https://'''.

After ordering the service, make sure that you have enough money on your account to write off its cost. Then you should wait 6 hours for the changes to take effect.

Also for the redirect service you should add the following entry to the domain zone site.ru

{| class="wikitable" style="width: 500px".
|-
| site.ru.
| A
| 37.200.71.162
|}

And also make sure that the domain is delegated to servers:
* ns3-l2.nic.ru
* ns4-l2.nic.ru
* ns8-l2.nic.ru
* ns4-cloud.nic.ru
* ns8-cloud.nic.ru * ns8-cloud.nic.ru

@@ Line 9: / Line 9: @@
 This scheme will look like this:
-[[File:CNAME_shema.png| Recommended connection scheme for the agency domain]].
+[[File:CNAME_schema.png| Recommended connection scheme for the agency domain]].
 Create a "CNAME" record using the target server name "sys.nemo.travel." (point at the end is mandatory). Fill in the fields Hostname/Nickname and Value/Destination (field names may be different for hosts).

@@ Line 34: / Line 34: @@
 Do not forget to specify the selected primary domain name in the "Site Management" → "Domains and protocols" in the "Domain name to download settings" field. If the domain name is in Cyrillic form, it should be written to [http://ru.wikipedia.org/wiki/Punycode Punycode].
-'''Attention!''' Websky employees do not make changes to the file ''.htaccess'.<br>.
+'''Attention!''' Websky employees do not make changes to the file ''.htaccess'.<br>
 Nemo does not provide information about the server OS and similar information through a technical support request.
 Access requisites to the hosting account are not issued. Nemo appeals to his own system administrators.<br>