VM public IP and Subdomain bind but not accessible

Nitesh Ghadge 0 Reputation points
2024-11-11T10:35:53.1566667+00:00

Dear Team,

I am new in Azure Vm, creted new VM and ip binding with godaddy domain making as subdomain

but not accessible, port 80 https also shows open and IIS service running on VM.

please do the needful.

Regards,

Nitesh

Azure Virtual Network
Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
2,540 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Ganesh Patapati 1,975 Reputation points Microsoft Vendor
    2024-11-11T18:57:33.76+00:00

    Hi Nitesh Ghadge,Greetings,

    Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

    It sounds like you're having trouble accessing your new Azure VM, which is bound to a GoDaddy domain as a subdomain. You've confirmed that port 80 and HTTPS (likely port 443) are open, and IIS is running on the VM. Here are a few things you can check and steps you can take to resolve the issue:

    1. Ensure that you need to test Ping and tracert from that VM to the public IP whether the connection is established or not.
    2. Please check that it works without a domain name and is accessible from the public IP address from Internet.

    1.Ensure that the GoDaddy domain (subdomain) is properly pointing to the public IP address of your Azure VM. You should have an A record or CNAME set up on GoDaddy.

    • A Record: This should point to the external IP of the Azure VM.
    • CNAME Record: If you're pointing to another domain, ensure it's set correctly.

    You can check the DNS propagation using online tools like whatsmydns.net to verify the DNS is pointing to the correct IP.

    2.Ensure that your Azure VM's Network Security Group (NSG) allows inbound traffic on ports 80 (HTTP) and 443 (HTTPS).

    • Navigate to your VM in the Azure portal.
    • Under "Settings," go to Networking.
    • Ensure that your NSG allows traffic on these ports.
    • If necessary, create a rule allowing inbound traffic from any source (0.0.0.0/0) on ports 80 and 443.

    Azure by default denies and blocks all public inbound traffic to an Azure virtual machine, and also includes ICMP traffic. This is a good thing since it improves security by reducing the attack surfaces.nsg inbound

    However, if you need to access your application from a public IP address, you will need to allow the specific ports and protocols.


    Hope this clarifies,

    Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.

    Accepted answer

    Looking forward to your response and appreciate your time on this.

    Regards,

    Ganesh


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.