I've a webapp hosted in azure cloud service.
We would like to put the WAF infront of web app per setup below:
We have created a bladomain.com.au
The DNS record points to IMPERVA IP address
IMPERVA then points to bla.azurewebsites.net
If I access the site directly using bla.azurewebsites.net, it works with no issue.
However when I try to access bla.zurewebsites.net, it shows below:
I tried adding bladomain.com.au to azure web app custom domain but it shows the error message below:
Error:DNS record for 'bladomain.com.au' that points to
'bla.azurewebsites.net' could not be located. If you want to configure
A record you must first create CNAME record with your DNS provider..."
Bit confused with error message above, as CNAME for bladomain.com.au should point to Imperva....
Appreciate any help.
This usually happens when you move your site regions, for example you had your site on Europe DC and you moved to US DC
It takes some time for the DNS to switch the IP address of your new Website and point it to the right DataCenter
It usually takes from 10 min to 2 hour for the changes to sync across the glob
We have similar problem, we are getting 404 error after more than 48 hours. It works after only, we run ipconfig /flushdns on client machine. It works smoothly after that, but it virtually impossible to tell every client to do flushdns.
To resolve this issue you simply need to do one of below:
1. Create awverify.yourdomain and point it's CNAME to azure web apps. OR
2. Update your domain CNAME to point to azure Web Apps.
Related
Good Afternoon,
after 2-3 Days trying to move my Domain from a Webhoster to Azure, i need your Help.
My actual Webhoster has Plesk. Over Plesk i can access and change all the DNS Entrys.
https://learn.microsoft.com/en-us/azure/dns/dns-delegate-domain-azure-dns
Based on this Walkthrough i'll have created 4 Entrys at my actual WebHoster and the Verification of the Domain is allright. When i run the command
nslookup -type=SOA #mydomain# i see a azure dns.
https://learn.microsoft.com/en-us/azure/app-service/manage-custom-dns-migrate-domain
After that i wanted to create a Test App in Azure. Based on the above Walkthroughs i managed to set my Custom Domain for my App Service. I made this Settings at my old WebHoster and in my newly created DNS-Zone in Azure.
So far so good. So I have deactivated the local DNS Service in Plesk in order to move on to Azure that should manage my DNS now. So i'll have deleted the Custom Domain in my App Service and created it again but this time it should point to my Azure DNS. But in the Creation Dialog of Creating a Custom Domain it tells me that im not the owner of the Domain.
Im confused and floating somwhere in the Dark. Could some guys point to the right direction. Do i have to do additional Entrys in the Azure DNS?
I hope someone can understand my bad Descriptions :).
Thanks for every help
After you host your domain in Azure DNS, you only need to manage your DNS entry in the Azure DNS zone.
Thus, in the step of migrating an active DNS name to Azure App Service, you can create domain verification records in the Azure DNS zone.
Then you also need to add the custom domain to the web app and remap the active DNS records via A or CNAME record following that steps in the document.
Thanks Nancy for the answer.
i could solve the Problem. I found this ?-Button in Plesk that let you test the DNS-Zone on the Nameserver. There was an ip poping up that does not belong to an A-Reccord. But the weird thing is thtat this Ip-Adress also did not belong to the App-Service IP.
But as soon as i added this Ip everything went fine and is working now.
Thanks
Sent from my Windows 10 phone
I have a problem in seeing up a custom finding to reach the website which is running on Azure VM.
Recently I have set up a new VM on Azure Virtual Network and let it run an php application as IIS. I have successfully configured custom DNS label so I can reach to the website with "http://hogehoge.japaneast.cloudapp.azure.com".
However, I can't well get a way to set up a custom domain, for example, "http://hogehoge.net". I made some search and managed to create a new DNS Zone, and then I also added a CNAME record, which is shown in the attached image, to it.
But I can't reach to the site. I know it is probably matter of course since I didn't configure DNS registrar. Also I haven't yet purchased the domain.
I think I made some mistake in my procedure. Could anyone point out what is wrong?
The problem is that your machine is not using the Azure DNS nameservers by default. You should add the CNAME/A records in your domain registrar's records, not in Azure DNS.
I set up a simple asp.net web forms test site for learning Azure, with a simple DB. Works fine locally. I deployed it to Azure. Then went through learning curve on the need to separately deploy the DB, link the resource, check connection strings and so on.
There's an issue, where the program on the site gets an error. I'm going through many paths to try to diagnose it. This question is about one specific path.
Several articles say that for the website to use the DB, I have to add the IP address of the website to the allowed IP addresses of the DB server.
https://azure.microsoft.com/en-us/documentation/articles/sql-database-create-configure/
However, I can't find the IP address for my FREE Azure website. When I researched this, it looks like there is no available fixed IP address for free websites.
So either:
1) I need to know where to get the IP address for the free website, or
2) there is some way to use Azure SQL in free websites without having to
designate an allowed IP address, or
3) something completely different.
Any help with this would be appreciated.
Thanks!
UPDATE: Below is all I see on the database configuration page, i.e. no firewall rules. However, I became convinced that the "Allowed IP Address" requirement must be finessed automagically in Azure, and so that was likely NOT the problem, which made me look more closely at the connection string, which WAS the problem. Basically one day of newbie learning curve, which I'll have to sleep on and try to understand more tomorrow.
There's an option to allow Azure services when you configure the database firewall. Check if that's checked. Also, posting the actual error message will help.
You don't need to do that for things that are hosted within the Azure platform.
Under the Azure SQL Server Firewall (Preview Portal) settings, ensure that the Allow access to Azure services is turned on:
Alternatively, via the Old Portal, the setting is found via:
Databases -> Servers -> Configure
I am using a Reserved (as of today called 'Standard') instance in Azure to host my website.
I have also set up my CNAME record from my domain provider to forward from www.{0}.com to the {0}.azurewebsites.net record, which works just fine.
The trouble I am having is with the A record. Currently
{0}.com gets a 404.
Under 'Manage Domains' in the Azure Management portal, it recommends setting up an A record to the supplied IP address (i assume the VIP of my deployment).
The problem is that IP returns a 404 when it is hit, so of course {0}.com gets one too.
Is there something I need to do on the Azure side to get the IP provided to direct to my website?
Along with the A name record did you add a CNAME for verification purpose as well, to point from awverify.www.{0}.com to awverify.{0}.azurewebsites.net ?
I setup my VM in windows Azure, and I didn't fully understand how it would all work together at the time, so I gave my cloud service a weird DNS name, and now I want to change it. Is there a way to change my .cloudapp.net DNS name? I really don't wanna have to delete my whole cloud service and all my VMs just to change the cloud service DNS. I know I can use a custom domain with CNAME or A Records, but that only affects production and forwarding etc... I want my cloudapp.net DNS to have a different name. Is that possible? Or do I have to delete everything and start over from the beginning?
It's currently impossible to change the name without deleting and recreating the service. I think this is because they have to reserve expensive (DNS) resources dynamically and they try to minimize the strain on these systems, but this is pure speculation.
It's an old post but I can help someone else.
When you created the VM (Cloud Service), it was automatically created a separated Storage. So you can create another Cloud Service - with the new name you want - using this Storage and delete the old one. I've already made it successfully.
Also, you can target an IP with a name from any domain name registration service.
For example, if on Azure you created a site called weirdclowndonkey.cloudapp.net and you would rather it be trustbank.com, you can do the following:
1) register a name anywhere (here's a search all ready for you: https://www.google.com/search?q=domain+name+registration )
2) find the ip address of your server on azure
3) enter that ip address as the target on the website of the domain name registration site.