Scribd
Upload
0 views

azure basic 34

The document outlines the use of public and private IP addresses in Azure for communication between Azure Virtual Networks and on-premises networks, as well as for internet connectivity. It also explains User-Defined Routes (UDRs) for customizing network traffic routing and provides an overview of DNS, including its hierarchical structure and the concept of public and private zones. Additionally, it addresses FAQs regarding Azure's role in domain registration and VM configuration for DNS resolution.

Uploaded by

Mahmud Rayhan Shajib
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0 views

azure basic 34

The document outlines the use of public and private IP addresses in Azure for communication between Azure Virtual Networks and on-premises networks, as well as for internet connectivity. It also explains User-Defined Routes (UDRs) for customizing network traffic routing and provides an overview of DNS, including its hierarchical structure and the concept of public and private zones. Additionally, it addresses FAQs regarding Azure's role in domain registration and VM configuration for DNS resolution.

Uploaded by

Mahmud Rayhan Shajib
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Gateways and on-premises connectivity Architecture

--Back to Index-- 103


Public and Private IP Addresses
Private IP addresses Enable communication between Azure Virtual Network and
your
on-premises network. When you use a VPN gateway or Azure ExpressRoute circuit
to extend
your network to Azure you create a private IP address for your resource.
Public IP addresses Allow your resource to communicate with the Internet. You
can create a
public IP address to connect to Azure public facing services.
You can create a public IP address for your resource in the Azure portal.
User-Defined Routes (UDR)
You can create custom or user-defined (static) routes in Azure to override Azure's
default system
routes or add more routes to the subnet route table.
Azure handles all network traffic routing automatically, but in some cases, a custom
configuration
is preferable. In these situations, you can configure user-defined routes (UDRs) and
next-hop
destinations.
--Back to Index-- 104
UDR Characteristics
● The next hop can be one of the following targets:
Virtual network gateway, Vnet, Internet, Network virtual appliance (NVA)
● Similar to system routes, UDRs also access route tables.
● Each route table can be associated with multiple subnets.
● Each subnet can be associated to one route table only.
● There are no charges for creating route tables in Microsoft Azure.
Configuring Azure DNS
What is DNS?
Think of the phone directory that is used at home. It is difficult to remember a string of
numbers
and hence the phone directory will list the phone numbers with names of persons/businesses.
● Coming back to the IT world, computers communicate with IP addresses. The DNS
(Domain naming system) is a friendly name given to the computer.
● For example, a web server has an IP address of 53.102.94.86. Instead of using the IP
Address, we assign a host name as web1. In a domain, the FQDN (Fully qualified
domain
name) will be web1.whizlabs.com.
● This is facilitated by DNS Servers which are setup in a hierarchy. At the top most level, we
have the ROOT and under the root, we have the top level domains (TLD) examples of
which are .ORG, .COM, .NET, .IN etc.,
--Back to Index-- 105
● In addition to this, we have domain registrars where we purchase a domain name.
● Examples are Godaddy, Namecheap and Amazon too via Route53. When
a user tries to
connect to a server whizlabs.com, the DNS resolves this to the IP address by going to the
ROOT and then to the .COM server.DNS works with a concept of Zones. We can set up
Private or Public zones. Public zones are used when we want the internet to be able to
resolve our names.
● However when we want to enable internal communication, we create private zones.
● Please note that zones can also be configured with a “Split-horizon” view which allows
a
private and public DNS zone to share a name.
FAQ
1) What is IP 168.63.129.16?
This is actually called a Wire Server and has an IP address of 168.63.129.16. and it
facilitates communication between Azure resources. It also serves as a DNS and DHCP
server by default. Please ensure that this IP is not blocked.
--Back to Index-- 106
2) Can I buy my domain from Azure?
No, Azure is not a domain registrar. You need to buy from a domain registrar and you can
create a zone in azure and add the records for DNS resolution.
3) How do we configure VMs to use private zones?
We can configure auto registration and for Vnet that we link with the Virtual Network
Link on the DNS Zone, the DNS registration will be done automatically when the VM is
created

You might also like