Last step is to make necessary settings and deploy applications to our production server. In the section Setting Up the Dedicated WebSockets Server we went through several steps to configure the server, Microsoft IIS and various other things. Now we will repeat the same steps, but this time for our production server.
1
Remove test DNS redirection from hosts file
Before proceeding we must remove the DNS redirection that was added for the domain socket.fmsoft.net for test purposes. Open the hosts file (typically located at C:\Windows\System32\drivers\etc\hosts on Windows) and comment out the line which redirects the domain to a local IP address.
Example hosts content (the redirect line should be commented out):
# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
# 192.168.1.5 socket.fmsoft.net
2
Update DNS to point the domain to the dedicated global IP
Adjust the actual DNS settings at your domain service provider to redirect the domain to the dedicated global IP reserved for the WebSockets server.
In this example the production server owns three global IP addresses. Two are already used for websites; the unused one will be dedicated to the WebSockets server:
IPv4 Address: 82.113.145.84
IPv4 Address: 82.113.145.152
IPv4 Address: 82.113.145.191
Add a DNS entry that redirects socket.fmsoft.net to the dedicated IP (here: 82.113.145.152).
clip0314
3
Verify DNS propagation
DNS changes can take a while to propagate worldwide, though often they take effect in a few minutes. You can check that the sub-domain resolves to the expected IP using the ping command (or other DNS lookup tools). The ping output should show the dedicated IP address:
clip0315
If DNS changes do not appear to take effect immediately, try clearing the local DNS cache (for example: ipconfig /flushdns on Windows) or wait a short while and retry the lookup.
