Create a subdomain from GoDaddy and point to GCP instance - dns

I have a domain registered under the Godaddy and now I want to create a subdomain which points to GCP instance (static address).
So when did a R&D, few are saying that we need to create a zone and then points the provided Namespace address to the Godaddy ?
or
Just go to Manage DNS in Godaddy -->add -->A type (ipv4) and then points to subdomain -->with destiny IP address
Which way is the appropriate way ? can anybody help in this ?

There is no point of creating a new zone to point a subdomain.
New Zone is like a new Domain. There could be 2 cases where you want to have a new zone -
Purchasing a new Domain
Using a subdomain of a domain which is purchased on some other DNS Provider.
In your case, Just add A Record -
Go to GoDaddy.
Select your Domain.
Add a new Record.
In Name (Host) Enter name of subdomain.
Select Record Type A.
In Value add IPv4 Address of GCP instance.
Leave everything else default and save.
It will reflect it's changes within next 48hrs (Usually takes few minutes)

Related

Why Azure DNS Zone create afdverify subdomain automatically and how to stop?

I create a CNAME record in DNS ZONE (e.g: site1.example.com). And then, afdverify.site1.example.com and site1.example.com will be created.
I just want to create site1.example.com only.
• #Kyakya, from your query and the screenshot, I can understand that you are trying to create a CNAME record for the ‘site1.example.com’ URL. But when creating a CNAME DNS record in a DNS zone, you will have to mention its alias FQDN URL, i.e., that original URL which you are trying to mask or associate with by creating this CNAME record. Thus, I can understand from the screenshot that you are trying to create a CNANE record for the Azure front door URL in DNS zone in Azure.
As a result, when you create a CNAME record with a custom domain name for an already hosted URL, you need to ensure that the original hosted URL is reachable and available as the CNAME record created will only redirect the DNS requests to the original hosted URL only.
• Since, in your case, you don’t want to create a subdomain regarding ‘site1.example.com’ in your DNS zone, i.e., ‘afdverify.site1.example.com’ so in that scenario, you will have to create an ‘A’ host record for the ‘site1.example.com’ in your public DNS server where your basic custom domain ‘example.com’ is registered. Once done, then create a CNAME record for the inbuilt Azure generated FQDN of that resource in your public DNS zone in that DNS server with ‘site1.example.com’ that you want.
And if you don’t want that too, then you will have to verify your custom domain in Azure, and then create resources in Azure based on the records created in DNS zone provisioned.

Add CNAME entry in which zone?

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

Assign domain name to azure VM

Im trying to assign my domain name to my azure virtual machine, been reading https://learn.microsoft.com/en-in/azure/virtual-network/virtual-networks-reserved-public-ip but I dont have a static IP. So I should be using CNAME?
At my domain name register I have added:
DNS ENTRY TYPE PRIORITY TTL DESTINATION/TARGET
www CNAME mydomain.ukwest.cloudapp.azure.com
I want it to work as mydomain.com (without www) - but not resolving. Thanks
First of all you can change you public IP to a static one without disruption your VM at all (so it continues to opérate). That solves one part of the problem.
The other way of doing this is exactly what you specified. CName link your Azure DNS to your real dns.

Connect Domain to Host

I think I have just successfully connected my domain to my web host and have done so by following an article. There seems to be 2 different ways of doing so and I wonder if there is a difference between the two.
method 1
Go to your domain provider. Create an A record that points to your web host's ip address.
method 2
Go to your domain provider and edit the nameservers according to what your web host indicated. Go back to your web host and add a DNS record indicating the domain.
I have followed method 1 and it works. Is it any different from the second method? In addition, when typing out a record at the domain provider, what does #, www, and * mean?
The A record maps a name to one or more IP addresses, when the IP are known and stable.
# * are same as known as domain name (e.g. yourdomain.com) some domain registrar using # instead of entire domain and some uses *. In hosting control panel under DNS records there domainname is mentioned instead of # OR *
If you work with method 1 and changing A record then you will have to change A record to WWW as well to work your domain with www else your domain with www will ended up with no result. You will also have to change all required records such as CNAME (if you have any subdomain), mail (if it is working through hosting provider).
So best practice is to use namererver so you don't need to change every record under Domain Control Panel.

How to add subdomain entry

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!

Resources