Azure/Networking - Revision history

Pio2pio: /* Private DNS zones */

2019-01-17T10:23:55Z

Private DNS zones

← Older revision		Revision as of 12:23, 17 January 2019
Line 107:		Line 107:
	<source lang=bash>		<source lang=bash>
	# Created VM named switch-1		# Created VM named switch-1

			piotr@switch-1:~$ cat /etc/resolv.conf
			nameserver 127.0.0.53
			search aaaa4akypjlederrplo5zraaaa.bx.internal.cloudapp.net

	piotr@switch-1:~$ cat /etc/hosts		piotr@switch-1:~$ cat /etc/hosts
	127.0.0.1 localhost		127.0.0.1 localhost

Pio2pio: /* Private DNS zones */

2019-01-17T10:22:42Z

Private DNS zones

← Older revision		Revision as of 12:22, 17 January 2019
Line 103:		Line 103:
	</source>		</source>


			Verify
	<source lang=bash>		<source lang=bash>
	# Created VM named switch-1		# Created VM named switch-1
Line 111:		Line 113:
	::1 ip6-localhost ip6-loopback		::1 ip6-localhost ip6-loopback
	fe00::0 ip6-localnet		fe00::0 ip6-localnet
	~~ff00::0 ip6-mcastprefix~~		<omitted>
	~~ff02::1 ip6-allnodes~~
	~~ff02::2 ip6-allrouters~~
	ff02::3 ip6-allhosts		ff02::3 ip6-allhosts

	piotr@switch-1:~$ nslookup switch-1		piotr@switch-1:~$ nslookup switch-1
	~~Server: 127.0.0.53~~		<omitted>
	~~Address: 127.0.0.53#53~~

	Non-authoritative answer:		Non-authoritative answer:
	Name: switch-1.aaaa4akypjlederrplo5zraaaa.bx.internal.cloudapp.net		Name: switch-1.aaaa4akypjlederrplo5zraaaa.bx.internal.cloudapp.net

Pio2pio: /* Private DNS zones */

2019-01-17T10:19:26Z

Private DNS zones

@@ Line 86: / Line 86: @@
 az network dns zone create -g MyAzureResourceGroup \
-    -n contoso.local \
+    -n us.sandbox.local \
    --zone-type Private \
    --registration-vnets myAzureVNet
@@ Line 94: / Line 94: @@
 az network dns record-set a add-record \
    -g MyAzureResourceGroup \
-   -z contoso.local \
+   -z us.sandbox.local \
    -n db \
    -a 10.2.0.4
@@ Line 100: / Line 100: @@
 az network dns record-set list \
    -g MyAzureResourceGroup \
-   -z contoso.local
+   -z us.contoso.local
 </source>
 If you wanted to create a zone just for name resolution (no automatic hostname creation), you could use the <code>resolution-vnets</code> parameter instead of the <code>registration-vnets</code> parameter.

Pio2pio: /* Private DNS zones */

2019-01-15T09:21:57Z

Private DNS zones

← Older revision		Revision as of 11:21, 15 January 2019
Line 72:		Line 72:

	== Private DNS zones ==		== Private DNS zones ==
			A DNS zone is used to host the DNS records for a particular domain. To start hosting your domain in Azure DNS, you need to create a DNS zone for that domain name. Each DNS record for your domain is then created inside this DNS zone. To publish a private DNS zone to your virtual network, you specify the list of virtual networks that are allowed to resolve records within the zone. These are called <code>resolution virtual networks</code>. You may also specify a virtual network for which Azure DNS maintains hostname records whenever a VM is created, changes IP, or is deleted. This is called a <code>registration virtual network</code>.

			Create DNS private zone
			<source lang=bash>
			# Private zone can be only created in empty Vnet
			az network vnet create \
			--name myAzureVNet \
			--resource-group MyAzureResourceGroup \
			--location eastus \
			--address-prefix 10.2.0.0/16 \
			--subnet-name backendSubnet \
			--subnet-prefix 10.2.0.0/24

			az network dns zone create -g MyAzureResourceGroup \
			-n contoso.local \
			--zone-type Private \
			--registration-vnets myAzureVNet

			az network dns zone list --resource-group MyAzureResourceGroup

			az network dns record-set a add-record \
			-g MyAzureResourceGroup \
			-z contoso.local \
			-n db \
			-a 10.2.0.4

			az network dns record-set list \
			-g MyAzureResourceGroup \
			-z contoso.local
			</source>
			If you wanted to create a zone just for name resolution (no automatic hostname creation), you could use the <code>resolution-vnets</code> parameter instead of the <code>registration-vnets</code> parameter.


	[https://docs.microsoft.com/en-gb/azure/dns/private-dns-overview?toc=%2fazure%2fvirtual-network%2ftoc.json Azure DNS Private Zone] is in [https://azure.microsoft.com/en-gb/updates/?product=dns Public Preview] since 22 March 2018		[https://docs.microsoft.com/en-gb/azure/dns/private-dns-overview?toc=%2fazure%2fvirtual-network%2ftoc.json Azure DNS Private Zone] is in [https://azure.microsoft.com/en-gb/updates/?product=dns Public Preview] since 22 March 2018

Pio2pio: /* Private DNS zones */

2019-01-09T15:17:11Z

Private DNS zones

← Older revision		Revision as of 17:17, 9 January 2019
Line 72:		Line 72:

	== Private DNS zones ==		== Private DNS zones ==
	[https://docs.microsoft.com/en-gb/azure/dns/private-dns-overview?toc=%2fazure%2fvirtual-network%2ftoc.json Azure DNS Private Zone] is in [https://azure.microsoft.com/en-gb/updates/?product=dns Public Preview]		[https://docs.microsoft.com/en-gb/azure/dns/private-dns-overview?toc=%2fazure%2fvirtual-network%2ftoc.json Azure DNS Private Zone] is in [https://azure.microsoft.com/en-gb/updates/?product=dns Public Preview] since 22 March 2018

	Docs:		Docs:

Pio2pio: /* Private DNS zones */

2019-01-09T15:16:21Z

Private DNS zones

← Older revision		Revision as of 17:16, 9 January 2019
Line 72:		Line 72:

	== Private DNS zones ==		== Private DNS zones ==
	[https://docs.microsoft.com/en-gb/azure/dns/private-dns-overview?toc=%2fazure%2fvirtual-network%2ftoc.json Azure DNS Private Zone] is in Public Preview.		[https://docs.microsoft.com/en-gb/azure/dns/private-dns-overview?toc=%2fazure%2fvirtual-network%2ftoc.json Azure DNS Private Zone] is in [https://azure.microsoft.com/en-gb/updates/?product=dns Public Preview]

	Docs:		Docs:

Pio2pio: /* DNS Name Resolution */

2019-01-09T15:14:14Z

DNS Name Resolution

← Older revision		Revision as of 17:14, 9 January 2019
Line 67:		Line 67:
	* own DNS server		* own DNS server
	* Azure DNS private domains		* Azure DNS private domains

	Resolving names between Vnet and on-premises networks requires		Resolving names between Vnet and on-premises networks requires
	* own DNS server		* own DNS server

			== Private DNS zones ==
			[https://docs.microsoft.com/en-gb/azure/dns/private-dns-overview?toc=%2fazure%2fvirtual-network%2ftoc.json Azure DNS Private Zone] is in Public Preview.

			Docs:
			* [https://docs.microsoft.com/en-us/azure/dns/private-dns-scenarios#scenario-name-resolution-across-virtual-networks Private DNS name resolution across VNets]

	~~[https://docs.microsoft.com/en-gb/azure/dns/private-dns-overview?toc=%2fazure%2fvirtual-network%2ftoc.json Azure DNS Private Zone] is in Public Preview.~~
	= [https://blogs.msdn.microsoft.com/igorpag/2017/10/08/why-azure-availability-zones Availability Zones] =		= [https://blogs.msdn.microsoft.com/igorpag/2017/10/08/why-azure-availability-zones Availability Zones] =
	Azure Virtual Networks (VNETs) and Subnets, are and will remain "regional" entities. Once you will define in a region, they will be visible and usable across all the AZ since Network Resource Manager in Azure is region-wide. There is no AZ specification for these objects, '''VNETs and Subnets can cross AZ'''.		Azure Virtual Networks (VNETs) and Subnets, are and will remain "regional" entities. Once you will define in a region, they will be visible and usable across all the AZ since Network Resource Manager in Azure is region-wide. There is no AZ specification for these objects, '''VNETs and Subnets can cross AZ'''.

Pio2pio: /* Availability Zones */

2019-01-05T20:32:01Z

Availability Zones

← Older revision		Revision as of 22:32, 5 January 2019
Line 74:		Line 74:
	= [https://blogs.msdn.microsoft.com/igorpag/2017/10/08/why-azure-availability-zones Availability Zones] =		= [https://blogs.msdn.microsoft.com/igorpag/2017/10/08/why-azure-availability-zones Availability Zones] =
	Azure Virtual Networks (VNETs) and Subnets, are and will remain "regional" entities. Once you will define in a region, they will be visible and usable across all the AZ since Network Resource Manager in Azure is region-wide. There is no AZ specification for these objects, '''VNETs and Subnets can cross AZ'''.		Azure Virtual Networks (VNETs) and Subnets, are and will remain "regional" entities. Once you will define in a region, they will be visible and usable across all the AZ since Network Resource Manager in Azure is region-wide. There is no AZ specification for these objects, '''VNETs and Subnets can cross AZ'''.

			Availability Zones and Availability Sets cannot be used together: when creating a Virtual Machine (VM), you will have to specify an AS, or AZ assignment, you cannot do both.
	== Services that support Availability Zones ==		== Services that support Availability Zones ==
	The Azure services that support Availability Zones are:		The Azure services that support Availability Zones are:

Pio2pio: /* Services that support Availability Zones */

2019-01-05T20:27:03Z

Services that support Availability Zones

← Older revision		Revision as of 22:27, 5 January 2019
Line 72:		Line 72:

	[https://docs.microsoft.com/en-gb/azure/dns/private-dns-overview?toc=%2fazure%2fvirtual-network%2ftoc.json Azure DNS Private Zone] is in Public Preview.		[https://docs.microsoft.com/en-gb/azure/dns/private-dns-overview?toc=%2fazure%2fvirtual-network%2ftoc.json Azure DNS Private Zone] is in Public Preview.
	= Services that support Availability Zones =		= [https://blogs.msdn.microsoft.com/igorpag/2017/10/08/why-azure-availability-zones Availability Zones] =
			Azure Virtual Networks (VNETs) and Subnets, are and will remain "regional" entities. Once you will define in a region, they will be visible and usable across all the AZ since Network Resource Manager in Azure is region-wide. There is no AZ specification for these objects, '''VNETs and Subnets can cross AZ'''.
			== Services that support Availability Zones ==
	The Azure services that support Availability Zones are:		The Azure services that support Availability Zones are:
	* Linux Virtual Machines		* Linux Virtual Machines
Line 89:		Line 91:

	== Resources ==		== Resources ==
			*[https://blogs.msdn.microsoft.com/igorpag/2017/10/08/why-azure-availability-zones/ Azure Availability Zones] 5+
	*[https://docs.microsoft.com/en-gb/azure/virtual-network/virtual-network-service-endpoints-overview Virtual Network Service Endpoints]		*[https://docs.microsoft.com/en-gb/azure/virtual-network/virtual-network-service-endpoints-overview Virtual Network Service Endpoints]
	*[https://azure.microsoft.com/en-gb/updates/?product=virtual-network Virtual Network] Azure updates		*[https://azure.microsoft.com/en-gb/updates/?product=virtual-network Virtual Network] Azure updates

Pio2pio: /* VPN Gateway transit to and from peered networks */

2018-12-31T12:13:29Z

VPN Gateway transit to and from peered networks

← Older revision		Revision as of 14:13, 31 December 2018
Line 34:		Line 34:

	= Routing =		= Routing =
	== VPN Gateway transit to and from peered networks ==		== VPN Gateway transit to and from peered networks ==
			[[Azure/Point-to-Site VPN]]

	== Resources ==		== Resources ==