DNS

4 Topics

DNS proxy for splunk cloud net rule still denied
I have set up my azure FW for DNS proxy and changed the v-nets dns to the private IP of the FW. I have the firewall pointing to custom dns servers. I created a FW rule to allow port 9997 to our splunk cloud instance from any IP. clients are still denied On a VM I can verify its using the FW IP, and I see dns queries in the logs. I'm not sure what I'm missing.
Capt_Caaaav3man
May 10, 2025 Place Azure
66Views
0likes
1Comment
How to connect Azure Function App to On-prem DNS Server?
I am creating a .NET application that validates domain from an on-prem DNS server. I would like to know how can I integrate my Azure function app to perform nslookup on the on-prem DNS server. Is there a way without using virtual networks or powershell script?
nabi04
Oct 15, 2023 Place Azure
898Views
0likes
2Comments
Can I use a subdomain for Azure
Example I already have a website which is hosted by https://www.ionos.co.uk/ and the DNS records are there default ones. I have created a subdomain example test.example.co.uk In Azure AD Manger to add a custom domain it says I need to edit the TXT DNS record on my host. I have tried to do this but it has not worked. Is it even possible to have two different hosts DNS records for one domain? Cheers Paul
ukmercenary
Jul 23, 2021 Place Azure
13KViews
0likes
3Comments
Azure DNS zone security
Hi there, I have been considering using Azure DNS. I created a test tenant to try it out and configured an unused domain on it (say example.com). It worked fine and I decided to start using it for my production/live domains. I created a new 'production' tenant, a DNS zone on that tenant and added domain example.com I realised that I was not asked to prove ownership of the domain (like you are asked when configuring a domain on O365). So I have 2 tenants with DNS zones with the same domain! However, the name servers on the 2nd tenant were different. So, when I changed it at my domain registrar, I was able to get the records managed on the new tenant. But that got me worried. Anyone can create a tenant on Azure and create a DNS zone for domain example.com Can anyone advise if there is a way to prevent this? Update: When I created the resource group on my production tenant, 1 selected a different region and I was thinking that this may be why the name servers are different. So I deleted everything on my production tenant. I created a new resource group and selected the same region as on the test tenant. When I created a zone for example.com, the name servers were different from those on the test tenant. So it does seem that there is some verification/control being done. I would be grateful if someone can confirm this.
Solved
nadsurf93
Mar 24, 2021 Place Azure
1.6KViews
0likes
2Comments