Before creating a website, you first need to choose a domain name and then choose a hosting. Your website won't work without these two things working together. This is why you need to make sure that domain name points to your hosting platform. After registering the domain, set up name servers for your domain at the registrars. Since you want to use: ns0.mysite.com and ns1.mysite.com, you need to set up glue records. Check your registrar's documentation for how to set them up. This is often done automatically, but you need to check. Run whois mysite.com to check if your nameservers are configured.
When you buy a hosting plan, your hosting provider emails nameserver addresses that start with NS1 and NS2. If you are unsure what to enter here, check your junk mail folders or contact your hosting provider. After entering this address in the corresponding field, click Save and you're done. As you can see above, this will take you to a page where you can manage that specific domain name. On this page, you can also view information related to your domain name, that is, when it will be automatically renewed.
You can also edit an existing domain binding. To do this, select an item and click Edit. You can change the port, IP address, hostname and certificate.
Using web forwarding
The easiest way to get your domain name or subdomain like www.mysite.com to direct visitors to an existing site is by using a web forwarding. This is useful when you want to redirect visitors to an existing site. You can find out more on page about web redirects. Adding domain validation IDs to your custom domain can prevent dangling DNS records and help avoid sub-domain hijacking. For custom domains that you previously configured without a verification ID, you should protect them from the same risk by adding a verification ID to your DNS record.
DNS Record Updates and Timeouts
System tells slave name server the interval to wait before issuing another update request if a master name server does not respond. If master does not respond to the update request before expiration date, slave will become unresponsive to requests for that namespace. At this point, any names that are used in resource records that do not end with an endpoint (.) Will be appended with this domain name ... In other words, when a zone record is read by a name server, the first line below will be interpreted as the second line.
There are a few changes to default /etc/named.conf file for the initial configuration of caching nameserver, so edit this file with your editor. First add the IP address of your local test host to the Listening port 53 line. This allows named to listen on your host's external IP address so that other computers can also use it as a nameserver. Although you can add hostnames and their corresponding IP addresses , this is not optimal solution for named services, especially when traveling. If there are other entries in hosts file, you may need to comment them out for duration of project if they interfere with naming or IP addresses.
Can I host different sites with their own SSL certificate on the same IP address?
Prior to IIS 8, it was possible to host multiple sites that require SSL on the same IP address if these sites were using the same SSL certificate or using a wildcard SSL certificate. The wildcard certificate was only useful if you need SSL at subdomain level of current site or domain. But what if you had sites with different names? Well, you can get an SSL certificate with Subject Alternative Names - SAN. This SSL certificate will allow you to secure multiple sites with a single SSL certificate.
The last option available prior to IIS 8 required each additional SSL site to be configured to the same IP address but with a different SSL port number. This will allow each site or domain to use SSL on the same IP address as other site. By default, SSL certificates use port 443 for secure communications. This port does not need to be specified in URL as it is a standard port. If you are using a different port number for SSL, you will need to add non-standard SSL port number to the URL for it to work. As you can imagine, this is not way you want to launch a public site. How user knows to enter port number is not a common step that users are familiar with when browsing the site.
Adding an additional IP address to host another site that needs SSL is a common method that is used. With introduction of IIS 8, Windows Server 2012 added a new feature called Server Name Identification - SNI. This feature offers a simpler solution to host multiple sites with different or individual SSLs on the same IP address. This feature is included by default in IIS 8 and does not require any additional features to be installed to start using it.
It should be noted that SNI implementation for SSL solution will not work for users using Internet Explorer on Windows XP. If your server has multiple IP addresses, you can implement SNI for some sites in addition to assigning a single IP address for SSL to individual sites. Both methods will work together seamlessly on different IP addresses.
The first thing to do is import SSL certificates for each site on a server, if you haven't already. Then open IIS 8 Manager and add the first site that requires SSL. If the first site already exists, proceed to a next step. After adding a site, select site and click Bindings ... in Actions menu bar on the right. Click Add. Select https for Type b. You can leave the IP address All unassigned, or choose IP address you want to use, if you have multiple IP addresses on the server, you will want to specify one you want to use for SNI. Enter site or domain name in Hostname field. Select Require server name check box. Select SSL certificate for site from the drop-down list. Click OK. Create a second site and add SSL binding by following the steps below. Select Bindings and click Add. Select https for Type. You can leave IP address All unassigned or choose IP address you want to use. Enter your site or domain name in a Hostname field. Select Require server name check box. Select SSL certificate for site from the drop-down list. Click OK to complete the configuration. This is all that needs to be done. Test the SSL for site to make sure each site is working correctly. If you have additional sites that need to add SSL, you can continue with the steps above to add an SSL binding for each new site.
Domain reverse zone
The reverse zone for your domain will provide the ability to perform reverse lookups. Many organizations do not do this internally, but reverse lookups can be helpful in identifying problems. Many anti-spam configurations, such as SpamAssassin, look for reverse lookups to check for valid email servers.
Note that FQDN is required for these commands, except for the nslookup command if domain and mysite.com lookup entries are specified in the /etc/resolv.conf file. In this case, it probably isn't, so use FQDNs for all testing in your project.
After that, you should choose the hosting platform on which you will build your house. You can check out popular hosting solutions including hosting, business hosting, and managed WordPress to choose what best suits your needs.
Zone files containing information about a specific namespace are stored in a named working directory. By default, this is /var/named. Each zone file is named according to the file parameter information in a zone statement, usually in a way that is specific to the domain in question and identifies the file as containing zone data, such as mysite.com.zone.
If the domain and application are in different subscriptions, you map App Service domain to the application in the same way you map an externally purchased domain. In this case, DNS is the provider of external domain and you need to add required DNS records manually.