I built my clients website on a subfolder on my own server.
Example: www.site.com/myclient
I want to add a new record on my clients domain in order to load the site from my server.
I can't change his DNS because he want's to keep his email accounts and everything on his current server.
Should I just add a new A record on his domain zone pointing to my server IP?
One hostname can be mapped to multiple IP addresses.
Also, one hostname can be mapped to another hostname using 'CNAME' record. (Alias name record)
Mapping one IP address to multiple hostnames will cause errors.
I believe that the best solution in this scenario is to create a unique virtual (loopback) IP address in your server and map that IP to the client hostname.
Related
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
I came into a struggle the last few days.
Using WAMP Server and following this Tutorial I set up a local email environment, and I wanted to make the emails reach accounts outside of the local host.
I heard you need to make some changes in the DNS zone, so here is my DNS Zone at Freenom.
Is is possible to make emails sent from a computer using hMailServer reach the outside world through a domain?
Thank you for your time.
It is possible but it depends on your Scenario.
If you are behind a Router or a NAT or a Dynamic IP-Address it's almost not possible
to run a real World sending SMTP-Server and you shouldn't
If you have a Hosting plan (your own Windows V-Server or Root server) with Remote Desktop
access and a static ip address it's and access to the DNS-Configuration of your Internet Domain, it is possible and recommended.
1) First you need to setup a DNS A Record which points to your static IP in DNS
2) You need to create DNS MX Record which points to your A Record
Now you can add a new hMailServer Domain and add accounts and sent Emails
out. But you should setup a DNS A Record for IMAP or POP3 as well so you can
Receive Emails and not only sending.
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 am unsure Whether both DNS server and Host file are the same or different.
I Hosted an application in IIS and created A host name as website1.domain.com and tried to browse it and it didn't work.
When searching on net i found that we need to make entry in DNS server or Host file.
As in most of the sites that I saw mentioned DNS server or host file. I am unsure Whether the both are same or they both are different.
A hosts file is used by Operating Systems to manually specify the IP addresses for specific domains/subdomains - think of it as an override.
DNS however is a server - think of it as a registry - that keeps track of records pertaining to domains, such as A records, MX records etc.
For the purposes of a local test site, an entry in your hosts file would be sufficient, however for a live site, a DNS entry relating to the domain you wish to have your site hosted on would be required.
Choosing which to use comes down to a few things. Does the server upon which your hosting the site use its own DNS server, i.e. a DNS server on the same network, which the connections to the server will be using as well? Does the domain name the site uses have its nameserver set to one that is externally available (i.e. 123-reg.co.uk). If either of these cases are true, you could probably use a DNS server.
If not, is the server hosting the site running on the same machine as the client that will be viewing the site? If so, you can probably use a hosts file, pointing your domains to the localhost IP of 127.0.0.1, ensuring the domains match the bindings in IIS.
Dns server is a server that will help to resolve dns names. ie when you type google.com in your browser , the name will be passed to the dns server provided by your isp. then it will be resolved to ip address by the dns server and your request will be routed to the google ip address by isp network. host file is different one. if you add www.mydomian.com entry in your host file and map it to an ip address 192.168.0.1 then your computer will check ion your host file when you type www.mydomain.com, whether there is any entry for mydomain.com in your host file, and if exists it will be routed to that ip address. in case if there is dns server and you set that server ip in your hnetwork configuration in your pc, then all the domain name request will be sent to that dns server(if there is no host entry exists)