Questions[azure-dns](server)

We have a "traditional" dns service, where some outsourcing company manages our dns services. We host a lot of services in the cloud (mostly Azure) and then must submit tickets to the dns guys to create cname -registrations (and sometimes also txt records for domain ownership validation) pointing to the services.

E.g. a web service in Azure could be at the address ourapplication.azurewebsites.net and today we would create a cname such as ourapplication.ourcompany.com pointing to that.

A lot of these services could very well be hosted in a subdomain such as ourapplication.app.ourcompany.com.

In Azure there is service called Dns Zone, which to my understanding is a full dns service. Can we keep our current dns setup for the main ourcompany.com domain but have dns services for *.app.ourcompany.com in Azure?

I have created a cname record for my domain(login.auditman.sam-solutions.in) using Azure DNS. Cname record points to the azure front door.

When I'm doing DNS Lookup for the record, I can successfully get the result, but when I'm trying to open the domain on a web browser, I'm getting NXDOMAIN error.

Can anyone please help me to understand what can be the possible issue regarding this?

I'm trying to deploy WorkAdventure for test in an Azure Linux Virtual Machine with Linux, and access it from the internet.

For this I found here #794 (comment) a reference to a good documentation from insensitiveclod from technic.
I followed that guide, and did most of the steps in an Azure VM with Ubuntu 20.04.2 LTS, dynamic IP address and with a DNS name like mytestwa.northeurope.cloudapp.azure.com

I did:

• Create Azure VM with Linux
• Create Azure IP Address (public address and DNS name) and assigned to Azure VM
• Set up docker environment and network setup
• Set up Traefik (and coturn) seperately from jitsi/workadventure
• Set up WorkAdventure
• Set up Jitsi

Still, I can't test anything (Traefik, WorkAdventure, or JITSI) because I don't know how could I achieve this step from the guide: "Set a wildcard DNS-record for *.whatever.your.domain.is to the publicly reachable IP of the machine you want to host it on. Using a CNAME record works fine. It might be good to set TTL to 5mins at first. (create DNS wildcard or each DNS entry for every services xyz.whatever.your.domain.is)"

Hence, WorkAdventure will need to use subdomains (play.*, pusher.*, meet.*, etc.) and I can't access any of this (neither on mytestwa.northeurope.cloudapp.azure or somefreedomain.tk):

• admin.mytestwa.northeurope.cloudapp.azure
• play.mytestwa.northeurope.cloudapp.azure.com
• meet.mytestwa.northeurope.cloudapp.azure.com
• play.somefreedomain.tk
• ...somefreedomain.tk

Setting the wildcard DNS record for *.mytestwa.northeurope.cloudapp.azure.com to the publicly reachable IP or to the DNS name should be done from Azure Portal or from the Azure VM Linux shell?

I managed to create a free Custom domain in freenom.com somefreedomain.tk. This is what i have in freenom management panel as DNS settings.

Still don't know how to proceed, because when I try to add another record in DNS settings as * CNAME 3600 ...cloudapp.azure.com i receive the error: "Wild cards are not allowed!"

Does anyone have any idea and could help me, please?

I created an Azure resource IP Address and assigned to my Azure VM.
As can be seen in the attached picture, I also tried to Configure that Azure IP Address and Create an alias record in Azure DNS with an Azure resource DNS zone (named dns.zone somefreedomain.tk) but, still doesn't work, and my knowledge is limited regarding to DNS and subdomains stuff.

Any help or suggestions are more than welcomed!
Thank you very much!

I don't have enough reputation to put other links or images, so i'll leave the link of the initial SO question.

---EDITED TO REFLECT THE FACT I'M RUNNING MULTIPE COPIES OF THE APLCIATION ON THE ONE DOMAIN----

Having an issue that I can't quite work out, wondered if some fine person here had any experience!

I'm running multiple web based .NET applications on a Azure VM (Windows Server 2019) on various sub-domains of a single domain. lets say app.clientdomain.com, app-test.clientdomain.com, app-dev.clientdomain.com. I don't control the public DNS for this domain as the client owns the domain (they have a CNAME record in place that points app.clientdomain.com at the FQDN of the Azure Application gateway that sits in front of the VM).

The application requires a local DNS loopback for certain things to work correctly, and I've used an Azure Private DNS zone with clientdomain.com as the main domain, and an A records for app.clientdomain.com, app-test.clientdomain.com and app-dev.clientdomain.com all pointed to the Private IP address of the VM. This works quite nicely for the local DNS loopback.

I now also need to be able to access an FTP server on the same domain, say ftp.clientdomain.com. The particular sFTP server in question is external to my Azure subscription and not controlled by me.

However the issue I have is that the DNS resolves fine for ftp.clientdomain.com in the outside world, but wont resolve from within the VNet (NSLookup reports 'Non-existent domain').

I ideally don't want to put an A record for ftp.clientdomain.com in my private zone, as the IP address may be changed by the client without notice, which would break my applications ability to reach the sFTP server.

Am I unreasonable to expect that if a matching DNS record is not found in the private zone that it should reach outside to public DNS? Am I doing something wrong, or is something broken?

Thanks in advance for any input!

I'm trying to host a static website on Azure storage with a custom domain and HTTPS.

I have created a storage account, uploaded my files, and enabled static site hosting. The site works nicely from the <foo>.web.core.windows.net domain provided by Azure.

I have created a CDN endpoint for the site with the origin hostname set to the primary endpoint provided by Azure, added a custom domain for my www subdomain, provisioned a CDN-managed certificate for it, and added a rule to redirect non-HTTPS requests to https://www.<my-domain>.com. This also works well.

Now I want my apex domain to redirect to my www subdomain.

CNAMEs aren't an option, but I have added an alias A record for @ pointing to my CDN endpoint and added the apex domain as a custom domain to the CDN.

Requests to http://<my-domain>.com redirect nicely, but requests to https://<my-domain>.com understandably give a scary SSL_ERROR_BAD_CERT_DOMAIN error. Azure does not support CDN-managed certificate for apex domains:

CDN-managed certificates are not available for root or apex domains. If your Azure CDN custom domain is a root or apex domain, you must use the Bring your own certificate feature.

I don't want to actually host anything on my apex domain—I just want to redirect it to my www subdomain. Manually provisioning (and maintaining) a certificate seems like a lot of overhead.

The domain registrar, GoDaddy, has a "forwarding" feature that did what I want, but I prefer to keep my DNS hosted with Azure.

Is there a way to redirect apex domain HTTPS requests to my www subdomain without manually provisioning a certificate for my apex domain or moving my DNS out of Azure?