I've successfully installed VCAP on my ubuntu 12.04 on azure . Now I plan to access it on public .
Information about it is :
DNS :
meruvian354.cloudapp.net
HOST NAME :
meruvian354
PUBLIC VIRTUAL IP ADDRESS (VIP) : 168.62.193.163
INTERNAL IP ADDRESS : 10.76.198.28
My target is generate automaticaly domain "myapp".meruvian354.cloudapp.net and vcap on make it online.
How do I have to set it on cloud_controller.yml ?
and Do I have to set configuration on
You need a wildcard domain pointing at the public IP address, I can see you have meruvian354.cloudapp.net registered as the api url for the cloud controller as I was able to register an account!
If you registered mydomain.com you would have to create a wildcarded "A" domain record for that domain and point it to the public IP address. You would then need to either create a new deployment using the -D option to specify the new domain or adjust the configuration of the current deployment using a tool like sed, see this question for another example;
cloudfoundry - vmc register error with external uri
Related
i created VM behide Azure Load Balancer. i want to use custom domain to Load Balance Public IP. for example i want to access url like 'xx.mvg.com' instead Load Balance Public IP from internet. how i can do it?
i tried to did followed reference link 'https://learn.microsoft.com/en-us/azure/dns/dns-custom-domain' but still not working.
Please recommend how to register my domain name i wish, i want map my domain name to my application running on VM behide Azure Load Balancer.
and Azure have service about internet domain registrar?
about your last question - no, Azure have only Azure DNS, which is not a domain registrar, but a DNS as a service.
Easiest way to achieve what you want - assign a dns name to a public ip (called dns label here) and create a CNAME record in your DNS for that DNS name. or just straight up create a A record in your DNS and point it to your public ip.
I did a research a few days about this. But still do not find any solution yet.
I have vm that host a website. The IP address for this website able to access from outside. But now i want to have custom domain for this vm.
Anyone know where I should refer to? Please share any link etc.
just create a A DNS record with your domain name registar, or use Azure DNS (you would need to delegate your domain to Azure DNS), or use Azure built-in DNS for your VM. If you dont have a domain - you need to buy it first.
https://serverfault.com/questions/143411/godaddy-linking-domain-name-to-ip-address
After you deployed an Azure VM, you also could configure an FQDN for this VM so that you can access the VM via Azure Provided DNS resolution which is mapped to the public IP address of Azure VM. Read how to create a FQDN. If so, you could directly access the VM via this FQDN.
Otherwise, you need to purchase a domain then use a CNAME to redirect your custom domain like www.example.com to this FQDN or use a A record mapping to the public IP address in your domain provider.
I'm setting up my website on Azure service. My DNS zone is 'xxx.io' (for example). I can create address such as 'main.xxx.io' or 'web.xxx.io' using Alias record sets and they work well. But I can't access the website directly using 'xxx.io' as address. How do I achieve this?
PS: my colleague says it used to work but now it doesn't, and he doesn't know how either.
you can create a A record called # with the value being IP address of your website. you cant have CNAME for # (root domain). Well you can, but its against the rules (afaik).
If your website is hosting on Azure service like virtual machines. You could just add an A record named # to point to the public IP address of Azure VM.
If your website is hosting on Azure web app service, you have to add an A and TXT type records in the DNS zone for using root domain. The app service plan(non-ASE) is multiple-tenant, you have to use TXT record to validate which website will be using the domain hostname.
The TXT record named #, the value is mywebapp.azurewebsites.net; The A record named #, the value is your website public IP.
You could refer to this picture and get more details here.
I have resource group on azure containing virtual machine and kubernetes and load balancer and public ip address and etc.
I can access to my kubernetes app with direct public ip or public ip dns name. But problem is that i can't get azure custom dns (dns zone) working for my public ip. e.g. myapp.com
I have tried to assign public ip address in dns zone but not getting custom dns name working for my app.
2 options:
1. A record that points to public ip address explicitly
2. CNAME record that points to azure "internal" dns name
From the description it looks like you haven't updated the name server settings of your domain (e.g. myapp.com) to use Azure DNS's name servers (where you have created a zone for that domain name) for query resolutions.
The article linked below has instructions on how to do it. Please let us know if this answers your question.
https://learn.microsoft.com/en-us/azure/dns/dns-delegate-domain-azure-dns
Suppose I have a VM with following property
FQDN :trialinstance.westus.cloudapp.azure.com
Public IP : XXX.XXX.XXX.XXX
Private IP : YYY.YYY.YYY.YYY
as it is an linux VM, output of 'hostname -f' command is
trialinstance.somerandomguid.dx.internal.cloudapp.net
now I need some help in understanding these :
what will be the value for Target field in BackendPool ?
What will be the hostname ?
How setting 127.0.0.1 works as hostname ??
Azure documentation and explanation is very very inadequate :(
what will be the value for Target field in BackendPool ?
If your Linux VM and application gateway are in a same Vnet, you could use your VM's private IP.
If your VM and application gateway are not in a VNet, you should use VM's public IP or FQDN trialinstance.westus.cloudapp.azure.com.
More information about this please refer to this link.
What will be the hostname ?
You should know how heath probe works, custom probe is indeed not used for any DNS name resolution or for any network routing. Instead, the probe "knows" which backend server pool to hit through the custom probe’s association with specific Backend HTTP Settings, which are in turn associated with one or many Backend Pools through one or many Routing Rules.
If multi-site is not configure, you could set it 127.0.0.1. See this link.