There is an article on Run Multiple Websites on the Same Port and IP Address on IIS. So in my Windows Server 2012 R2, I installed DNS Server. However there is no zone by default.
But according to the link, I want to run multiple websites on the same port and IP address on IIS. After I edited site bindings on IIS. All I have to do is to add an alias for the server (A or CNAME) to DNS that specifies the IP address or the name of the web server.
Now I want to follow the example to add an entry to the zone. The below image is from the link. It has two zones. One is _msdcs and the other one is something I don't know.
However my DNS server doesn't have zone yet. I guess that I must create zones.then add the CNAME entry.
My question is which zone can I add the CNAME entry?
Or it doesn't matter in any primary zone?
It should definitely be your company IT DNS server. The CNAMEs can go in an existing zone on that server; they don't have to go into a new one. However, there needs to be at least one host a.k.a. A record that points to the webserver. The CNAMEs should all point to that as the target host.
For example, if you need to access a website from www.test.com.
Then you can create a forward lookup zone.
Then you need to create a A record to map your IP address to your server
Now you can right click blank place->create Alias(CNAME) to map your A record to CNAME
Finally, you only have to set IIS binding and access the website
Related
I had bought my domain name through namecheap. Recently I set up MS Azure and created a VM machine which runs apache and wordpress. The VM has an IP address which is pointing to my domain name. A few days ago I removed namecheap hosting and transferred everything to azure. BUT for some reason, my domain quantiv3.com keeps switching from the old namecheap IP address to the new azure IP address. This can be seen when doing a DNS look up on mxtoolbox.com... I can't figure out what i'm doing wrong. Could anyone help? Thanks
You have 8 Name Servers listed for your domain.
4 are reporting one IP address and the other 4 are reporting another IP address.
The solution is to first correctly configure the correct DNS servers at your Domain Registrar. Then correctly configure the correct DNS servers pointed to by the Name Servers.
Typically you only configure one set of Name Servers. For your domain you have two sets of Name Servers. The first is provided by Microsoft Online (Office 365) and the second is provided by Azure DNS. Pick one or the other and correctly configure your DNS Registrar. If you decide to keep both sets, then you must configure both sets to be identical except for the SOA record.
I have a domain name (somename.com) registered at godaddy and i am using godaddy DNS Manager. But i am hosting my website with hostinger.com. So i have created a subdomain (sub.somename.com) on hostinger which by default points to same IP as a domain.
Now i have entry on godaddy DNS for my domain and subdomain name which points to hostinger server address where my website hosted. But when i access my subdomain (sub.somename.com) it goes to my somename.com. I have to refresh it to load sub domain page correctly.
Godaddy DNS Entry
domainname -- somename.com -> IP address of hostinger.com
subdomain -- sub.somename.com --> IP address of hostinger.com (same as above)
Hostinger DNS Entry
subdomain -- sub.somename.com --> IP address of hostinger.com(same as above)
Is above entries is correct ?
Should we need to have entry for domain and subdomain both on godaddy DNS ?
Do we need to have a entry for subdomain in hostinger.com also ?
In order to create a subdomain correctly you have to go through 2 steps:
1. Update your DNS records, so they accept your subdomain (sub.somename.com).
You should have these records for your setup:
A: # -> IP of hostinger.com (this is to connect the domain with hostinger)
A: sub -> IP of hostinger.com (only put the subdomain name)
CNAME: * -> somename.com (so that everything before somename.com goes to somename.com)
CNAME: *.sub -> sub.somename.com (so that everything before sub.somename.com goes to somename.com)
There are different types of DNS Records, the one's you mentioned are all A Records, you have to use CNAME Records as well.
2. Creating a virtual host (on the hosting provider)
The previous step was so that the Domain Name Servers know to which ip to point when the subdomain is used. From this side we have to point the subdomain address (sub.somename.com) to a specific folder that contains the different website. Most host providers, when you create a subdomain automatically create a new folder you can put your content at and point at it.
So to answer your questions.
No you have to change your DNS Records so they match the information above. Let me remind you that changes in the DNS Records might take a while to take effect (1-2 hours).
Your DNS entries should be at one place. Usually they are provided by the hosting provider (hostinger in this case), but since they are also provided by GoDaddy as well feel free to update them there.
There is no need to have a DNS entry in hostinger if you update them in GoDaddy.
P.S. Since I haven't used hostinger before, feel free to update me if you have more info, like if you're using CPanel.
If you intend to host a subdomain at an IP different than your main site, the records should look like this.
Main Site (mysite.com)
Type: A
Name(Host): #
Value(Points To): 192.168.1.1
Blog Site (blog.mysite.com)
Type: A
Name(Host): blog
Value(Points To): 192.168.1.2
As a reference, you only need an A record to host a subdomain. CNAME record is an alias. www records are usually CNAME records to the root domain as they are the same page.
Hope this helps!
I have domain coupen.tk and a sub domain coupons.yadvi.com.I have web data in coupons.yadvi.com. i want so DNS configuration that if any one visit Coupen.tk they can see all information of coupon.yadvi.com but the link should be shown of coupen.tk not of coupons.yadvi.com
i have added the ip address of yadvi.com in coupoen.tk DNS A Record ,Ip Address of yadvi.com which will be same for coupons.yadvi.com.
coupen.tk needs to point to the same A record IP address as coupons.yadvi.com, so they both resolve to the same server. That server then needs to be configured to serve the same site for requests to both domains.
The usual way to do that would be to make coupen.tk the "master" A record and configure coupons.yadvi.com as CNAME coupen.tk, so it points to that master record. The web server still needs to be configured to serve the same site for either domain.
Failing that, you'll need to set up a reverse proxy server which literally forwards requests for one domain to the other.
My client have a dedicated server on liquedweb cloud service and we my web app is hosted on that server. We want our users to map their domain to our server. So they can enjoy our web app by using their domain name. What information I need to provide to my user so he can map domain and what information I need from them?
I don't know much(in fact anything) about domain mapping
thanks
It depends if the server has a dedicated IP address or is natted.
If the server has a dedicated IP address you can ask your clients to point their entire domain to you server by adding the following A records:
Host TTL Protocol Type IP Address
# 300 IN A 1.1.1.1
www 300 IN A 1.1.1.1
Not all domain hosts ask for TTL,if not dont worry about it.
If you want just their subdomain to point to your server (subdomain.website.com)
subdomain IN A 0.0.0.1
TTL is optional in some systems, in this case the default will be used.
Generally it is recommended that you use an IP for the Apex record and not a domain name. EG: example.com is the apex, www.example.com is the www subdomain.
A typical configuration would be below:
Host TTL Protocol Type Result
# 300 IN A 1.1.1.1
www 300 IN CNAME example.com
This is the same config as the top example but using CNAME example.com. It is the same as using A 1.1.1.1, it just means you only need to change one record.
If your server details are a hostname and not an IP address, most systems will not let you use the hostname for the apex so you will need to find out the IP address. (A simple method is to use the nslookup command or dig command).
TTL is how long in seconds a record last before it expires. If you are unsure what you are doing I recommend lowering this so you can correct mistakes more quickly.
Different methods for the different servers. For most of the servers, you have to change the nameservers of your domain.
This mostly needs when your domain registrar and hosting provider both are different.
First Login into your hosting account, navigate to the account details,
then copy the nameservers from there...which would be like :- dns1.hostingprovider.com
dns2.hostingprovider.com
After that, Go to control panel of your domain. Navigate to the nameservers
You will see the link:- dns1.domainregistrar.com
dns2.domainregistrar.com
Paste the above links at the place of below links.
They need the IP address (and possibly instructions on how to configure their DNS servers (which means a variety of different sets of instructions for different servers and control panels)).
You need the domain name.
I have a domain registered at godaddy [www.example.com]. And i have a free hosting at Binhoster.
I want to point my domain to Binhoster's FTP server where my pages are hosted.
I googled this and I was instructed to change my nameservers of godaddy to Binhoster's nameserver, then add the FTP IP in the A-Record.
But I, without changing the nameservers, Added the A-Record to point to Binhoster's and added a custom domain at Binhoster's [www.example.com to point to public_html] and its working. I'm currently using my original nameserver. Then why is it instructed to change nameservers everywhere. Is it mandatory ??
You may want to reach out directly to Binhoster to see why they suggest to change your NS. This may be because the IP address could change. If an IP address changes and you control the DNS, you will need to be notified and subsequently update the A record IP, whereas if you pointed your NS the IP may be updated automatically at the host.
Ultimately, as long as you point your A record to the host, you should be fine.