@Tom I understand that you have questions regarding the Azure FQDN i.e., when you create the VM and add a DNS name in the Portal as shown below:
However, you do not see the same name once you login to the Server/VM in Azure. Is this what you are concerned about? Please correct me otherwise.
The FQDN that is provided here is for the Public IP of the VM. Once you login to the server/VM and do a nslookup for the hostname, you will see the hostname of the private IP of the VM.
In this case, what you are seeing(servername.acad.ac.uk) seems like a private DNS name. Can you confirm what DNS server you are using for this VM/Vnet? Usually it shows up in the NSLOOKUP output.
Thank you!
Answer from SaiKishor-MSFT on learn.microsoft.com@Tom I understand that you have questions regarding the Azure FQDN i.e., when you create the VM and add a DNS name in the Portal as shown below:
However, you do not see the same name once you login to the Server/VM in Azure. Is this what you are concerned about? Please correct me otherwise.
The FQDN that is provided here is for the Public IP of the VM. Once you login to the server/VM and do a nslookup for the hostname, you will see the hostname of the private IP of the VM.
In this case, what you are seeing(servername.acad.ac.uk) seems like a private DNS name. Can you confirm what DNS server you are using for this VM/Vnet? Usually it shows up in the NSLOOKUP output.
Thank you!
Please go through it.
https://learn.microsoft.com/en-us/azure/virtual-machines/create-fqdn
Also Check
https://stackoverflow.com/questions/15289835/fqdn-on-azure-virtual-machine
I found this https://learn.microsoft.com/en-us/azure/cloud-services/cloud-services-custom-domain-name-portal#add-a-cname-record-for-your-custom-domain
So I deleted my App Service in Azure, as that's not what I needed and followed the above instructions to configure the DNS for cloudapp.
You have to map your custom domain name to the web app. Below is the Microsoft doc with the steps.
Custom Domain
You can use CNames to link Azure domains to your existing domain. Just créate a CName that point to your Azure DNS Name. Example:
you need vm.company.com to point to your vm called myvm in Azure. créate CNAME vm that point to myvm.location.cloudapp.azure.com
As for the cert, copy it to the vm and import like you normally would.
A DNS zone is used to host the DNS records for a particular domain. To start hosting your domain in Azure DNS, you need to create a DNS zone for that domain name. Each DNS record for your domain is then created inside this DNS zone. Finally, to publish your DNS zone to the Internet, you need to configure the name servers for the domain.
Each of these steps is described in the following steps:
Step1: First create the Azure Virtual Machines.
Step2: To get DNS addresses, you need create DNS zones with your domain name.
Go to Azure Portal => New => search DNS zones => Create DNS zones
Name= azurewala.com, Subscription, Resource Group, and Location
Step3: Once Azure DNS zones created you can see four Name Servers.
Step4: Go to GoDaddy control panel and click on the DNS.
Step5: Change the Nameservers by choose your new nameserver type as: Custom
Note: Copy and paste the Name Servers from Azure DNS to GoDaddy
And make sure you have to remove the extra dot before you save.
Step6: Open Created DNS Zones and add a record set
Name: www Type: A TTL: 1 Hours
IP ADDRESS: 52.176.102.178
Note: Give IP Address of the VM.
You may refer detailed workaround steps here: https://stackoverflow.com/questions/45449401/configuring-a-custom-domain-name-for-an-azure-vm-and-godaddy/45453110#45453110
Hello,
I'm seeing *loads* of cloudapp domains being blocked, I can't discernably notice anything that I care about not working but there is a constant stream of them being blocked and I can't tell what they're for.
I can't see the source IP because of the way I use pihole (I have bind > pihole > cloudflared) in a stack, so I just see the loopback of bind making the query.
Just not sure what they are - I've seen some other state they're MS based sites/domains.