Quantcast
Channel: Azure Networking (DNS, Traffic Manager, VPN, VNET) forum
Viewing all 6513 articles
Browse latest View live

Azure DNS does not allow valid underscore in TXT record name

$
0
0

To configure DKIM domain keys, you have to create TXT records of the name "_domainkey.example.com", for example. However, New-AzureDnsRecordSet -Name "_domainkey" -RecordType TXT... fails with the error "BadRequest: The domain name '_domainkey.example.com' is invalid".

Underscores are not valid for hostnames, but are valid in DNS records. The -RecordType SRV seems to have an exception that allows underscores, but not -RecordType TXT. Please fix this or else we cannot properly configure our DNS.

Thanks.


Ron Peters Red Folder, Inc


Failing to connect VPN from Fortigate 30D to Azure

$
0
0
Hello all,
 
I have also posted this on the Fortigate Forums and while I know the debug log comes from the firewall appliance, I'm hoping that someone on the Azure side might have some insight. I'm attempting to use my Fortigate to connect to the Azure VPN and followed the video instructions step by step(youtube.com/watch?v=-57vvLIROxk). However, when I attempt to bring it up, I get no success. When I use the diag, I see the following messages
 
I believe the key line of error is the
 
ike 0:AzureVPN:5851: received notify type AUTHENTICATION_FAILED
 
If this is related to mistyping the shared key, I typed this in, clicked the copy key and pasted, copied manually and pasted it in, copied to notepad and pasted it in.
 
Please let me know if I'm not looking at the right place or if anyone needs more information to diagnose.
 
ike 0:AzureVPN: schedule auto-negotiate
ike 0:AzureVPN: auto-negotiate connection
ike 0:AzureVPN: created connection: 0x2d70000 5 xxx.xxx.xxx.xxxx->yyy.yyy.yyy.yyy:500.
ike 0:AzureVPN:AzureVPN: chosen to populate IKE_SA traffic-selectors
ike 0:AzureVPN: no suitable IKE_SA, queuing CHILD_SA request and initiating IKE_SA negotiation
ike 0:AzureVPN:5851: out CDF6B92965C6F25C000000000000000021202208000000000000016C220000B40200002C010100040300000C0100000C800E01000300000802000002030000080300000200000008040000020200002C020100040300000C0100000C800E01000300000802000005030000080300000C00000008040000020200002C030100040300000C0100000C800E00800300000802000002030000080300000200000008040000020000002C040100040300000C0100000C800E00800300000802000005030000080300000C00000008040000022800008800020000195AAE81765370D4156AAEC8B61E0E1D76CF185B3463AD2CFC40C7845308B9442F64D1761B27AB4D7C0BD3F7D8F4EC34AC367534F7C5C79BEABE2D7D94AE687CA5937110754E437803A04F2ED0EBF542B08E7ACCBF736A731EE05ABC0074F73500961782D47734495F829C915AD083470A860279B43706CBA3944A7638E5889E00000014632C7B8E43D44EB18326181ED1CEB6A3
ike 0:AzureVPN:5851: sent IKE msg (SA_INIT): xxx.xxx.xxx.xxxx:500->yyy.yyy.yyy.yyy:500, len=364, id=cdf6b92965c6f25c/0000000000000000
ike 0: comes yyy.yyy.yyy.yyy:500->xxx.xxx.xxx.xxxx:500,ifindex=5....
ike 0: IKEv2 exchange=SA_INIT_RESPONSE id=cdf6b92965c6f25c/0aa00c68858ee14d len=809
ike 0: in CDF6B92965C6F25C0AA00C68858EE14D212022200000000000000329220000300000002C030100040300000C0100000C800E008003000008030000020300000802000002000000080400000228000088000200004A2289AF543817E581F01294B6728D5EF05ACFFA13D8202C59F22BF707C22B4BD4A9810F01563ADA96B04440AF6EBE9A66BC7CEB2C8944179750BC99E85776D81E77B09C98F3A7353D4EF57E12A145EAD26470356B6AC0BACB8E03C220A2E95B717309F2E8B8559426273EFD4EFC8FB4B7C0325683EC3363D99D5CFBC68BE7E129000034E5D47C3FC9EF1370676866D4582257B3BD7F2B0C9B33C33574B1EF1D1DA98BD0E4794E708E83C63704A5F1915108C6332900001C000040041A859575EF05EEAA767D6379767ACE6D433F8CAC2B00001C000040050DD8CF38D72208249D91A60A496072AAB2CBE5192B0000181E2B516905991C7D7C96FCBFB587E4610000000926000014FB1DE3CDF341B7EA16B7E5BE0855F120000001BD040EAC826040562797E52513FC2AE10A539559E4A4DDBCBD869C3F07ED40E31B08EFCEC4D188CD3B154A5C7522AA46BFA4089D39974EBDB4A360F7A01D6A47A267C92E2F19688B9B86616695EDC12C13001C6981BCF1C96EAD895D5A64FD2D2F0DAE81FFD401F0334C1AA1D9EE5B7BA9DE43BC027D570933FB88A95AEFC084FC1374416BB16332C2CF9259BB3B22CD37F1B14750AE537C8C6A036747E2B71E17B7344F302D256
3191EAF7735CABF5868D378240EC3EDF290CC1F5CC732CEB3D24E17E52DABD27E2F0F79319EFDFC1F520FBAC85552CF2D28F5AB9CA0B30A4E64FDE768AFCED5A9084283046792C29157087DBD45FB0928D4E1DF81567E7F2ABAFD62B6775D52E13C1ABE349DAE8B49594EF7C3843606466BD597912DE6175D66FC423B7771374C796DE6F887255921A5B2E62B0E07B8BA9AE9FFCA0F6E656263CA5068A78CF84BD7432DD58F965EB3A55E7C780DCE27F7BD877D5DF9E0A3F9EB4CB0E2EA9EFDB697783317E62854253D6D7783190EC919056E991B9E39980BF7CF4508BA2D04CE3A186E4F382711E0CC7BB2D75CE172ACCDF05D9A86D278298889986C89168330E61358521592983A3C8D2D2E1406E7AB3C1
ike 0:AzureVPN:5851: initiator received SA_INIT response
ike 0:AzureVPN:5851: received notify type NAT_DETECTION_SOURCE_IP
ike 0:AzureVPN:5851: ignoring unauthenticated notify payload (NAT_DETECTION_SOURCE_IP)
ike 0:AzureVPN:5851: received notify type NAT_DETECTION_DESTINATION_IP
ike 0:AzureVPN:5851: ignoring unauthenticated notify payload (NAT_DETECTION_DESTINATION_IP)
ike 0:AzureVPN:5851: incoming proposal:
ike 0:AzureVPN:5851: proposal id = 3:
ike 0:AzureVPN:5851:   protocol = IKEv2:
ike 0:AzureVPN:5851:      encapsulation = IKEv2/none
ike 0:AzureVPN:5851:         type=ENCR, val=AES_CBC (key_len = 128)
ike 0:AzureVPN:5851:         type=INTEGR, val=AUTH_HMAC_SHA_96
ike 0:AzureVPN:5851:         type=PRF, val=PRF_HMAC_SHA
ike 0:AzureVPN:5851:         type=DH_GROUP, val=MODP1024.
ike 0:AzureVPN:5851: matched proposal id 3
ike 0:AzureVPN:5851: proposal id = 3:
ike 0:AzureVPN:5851:   protocol = IKEv2:
ike 0:AzureVPN:5851:      encapsulation = IKEv2/none
ike 0:AzureVPN:5851:         type=ENCR, val=AES_CBC (key_len = 128)
ike 0:AzureVPN:5851:         type=INTEGR, val=AUTH_HMAC_SHA_96
ike 0:AzureVPN:5851:         type=PRF, val=PRF_HMAC_SHA
ike 0:AzureVPN:5851:         type=DH_GROUP, val=MODP1024.
ike 0:AzureVPN:5851: lifetime=56600
ike 0:AzureVPN:5851: IKE SA cdf6b92965c6f25c/0aa00c68858ee14d SK_ei 16:DC3A5F30A978AE4BEAABF54D14CB5E5E
ike 0:AzureVPN:5851: IKE SA cdf6b92965c6f25c/0aa00c68858ee14d SK_er 16:15BC3779730136398F4D9ABD2925995C
ike 0:AzureVPN:5851: IKE SA cdf6b92965c6f25c/0aa00c68858ee14d SK_ai 20:028F3AD894D1FB57F2D8606D15158C17A8B09CF7
ike 0:AzureVPN:5851: IKE SA cdf6b92965c6f25c/0aa00c68858ee14d SK_ar 20:F28CEED92DF487B02B1EF88FBB60EE4D18488FB3
ike 0:AzureVPN:5851: initiator preparing AUTH msg
ike 0:AzureVPN:5851: sending INITIAL-CONTACT
ike 0:AzureVPN:5851: enc 2900000C010000000A213E0C27000008000040002900001C02000000B617525FB24BD868437C6728CE673819637FA29121000008000040242C0000A40200002801030403DCB282730300000C0100000C800E0080030000080300000200000008050000000200002802030403DCB282730300000C0100000C800E0100030000080300000200000008050000000200002803030403DCB282730300000C0100000C800E0080030000080300000C00000008050000000000002804030403DCB282730300000C0100000C800E0100030000080300000C00000008050000002D00001801000000070000100000FFFFC0A80100C0A801FF0000001801000000070000100000FFFF0A0000000A0000FF03020103
ike 0:AzureVPN:5851: out CDF6B92965C6F25C0AA00C68858EE14D2E202308000000010000014C23000130DD21BDBEF9CA7ECB91423764623474F2DCC200E89418535B7BA55DA12ABCB65355C3A404E93ECAB6BE3A69D4BD4A975A8DB122D6500C6CA9F4B62D6BCC1384FA160450DF87F5F0436E4286E4BA43744B87EAC3C8E3C3ACFC3CF9F9F9CE68E3ECB500D7AB1739D17B2699A1B980E1672C3BB1741204F649E03BEE8E28ADC375D6081453A3845277E32EAC39710AF10B6878FE0BDBF7046B62EBBB97C17CCA88BE060B7EC452A912D0D5CF69E6DF7B9B1AFC1F66AAEA7D7ACD6CCD9A683974CE7D0D1FCB8671B139593F34A3A472443885EDE3C4061BC77135C432055EB0303396BF80D58E147671DB8623F8B59FC76DABA3856A35B859E0092FC889846E359CF78082738A8D4690A380CE1C7212F9F36AAA8849C197EEF7A53DC044EA0C191E6552AFF63ADA273802B8BE3C77
ike 0:AzureVPN:5851: sent IKE msg (AUTH): xxx.xxx.xxx.xxxx:500->yyy.yyy.yyy.yyy:500, len=332, id=cdf6b92965c6f25c/0aa00c68858ee14d:00000001
ike 0: comes yyy.yyy.yyy.yyy:500->xxx.xxx.xxx.xxxx:500,ifindex=5....
ike 0: IKEv2 exchange=AUTH_RESPONSE id=cdf6b92965c6f25c/0aa00c68858ee14d:00000001 len=76
ike 0: in CDF6B92965C6F25C0AA00C68858EE14D2E202320000000010000004C29000030CDFAC022B75853A2E68C1B7A67CCE8CC88138E254E9A54793FA5164AF981D695759FE520A295C2AA38D26B0D
ike 0:AzureVPN:5851: dec CDF6B92965C6F25C0AA00C68858EE14D2E2023200000000100000028290000040000000800000018
ike 0:AzureVPN:5851: initiator received AUTH msg
ike 0:AzureVPN:5851: received notify type AUTHENTICATION_FAILED
ike 0:AzureVPN:5851: schedule delete of IKE SA cdf6b92965c6f25c/0aa00c68858ee14d
ike 0:AzureVPN:5851: scheduled delete of IKE SA cdf6b92965c6f25c/0aa00c68858ee14d
ike 0:AzureVPN: connection expiring due to phase1 down
ike 0:AzureVPN: deleting
ike 0:AzureVPN: flushing
ike 0:AzureVPN: flushed
ike 0:AzureVPN: deleted

Azure CLI Traffic Manager in ASM mode

$
0
0

Hello,

I'm a OS X user I want to add an external endpoint to traffic manager profile. I downloaded and installed Azure CLI tool ( v0.9.4 ) but it seems that it doesn't have Traffic Manager commands available in ASM mode.

Any help?

Problem moving VM to another net.

$
0
0
Hi I am trying to move a VM from the default network to a new network I have created. This page (https://azure.microsoft.com/sv-se/documentation/articles/virtual-networks-move-vm-role-to-subnet/) make it look easy.

But when I run this script I get this error message:

        Get-AzureVM : No default subscription has been designated. Use Select-AzureSubscription -Default <subscriptionName> to
    set the default subscription.
    At C:\temp\net.ps1:1 char:1+ Get-AzureVM –ServiceName abcd-ctx –Name abcd-ctx `
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo          : CloseError: (:) [Get-AzureVM], ApplicationException+ FullyQualifiedErrorId : Microsoft.WindowsAzure.Commands.ServiceManagement.IaaS.GetAzureVMCommand

How do I find the name of the subscription? If this part i needed why was it not on the documentation page? 

I in evaluating mode on azure at present. 

Azure VNET to VNET and both VNETs to On-Premise

$
0
0

Hello,

I have a client that has a Cisco ASA 5510 and two VNETs.  I need to setup a VPN connection between the two VNETs and the On-Premise environment; however since Cisco ASA devices don't support Dynamic routing, I can't use the Multi-Site VPN setup.

Any idea how to get around this?  Besides routing traffic between the two VNETs back to On-Premise?

So basically:

On-Premise < - > Azure East

On-Premise < - > Azure West

Azure East < - > Azure West

Any help would be greatly appreciated!

Thanks,

Brian

Dynamic Routing Protocol Support Through Azure S2S VPN Tunnel

$
0
0
I am planning to configure Multisite VPN tunnels between an Azure vNet and two on-premises data centers.  We are using Cisco ISR series routers that support Dynamic Routing gateways.  Can a Dynamic Routing protocol such as OSPF be enabled through the tunnel to build the routes instead of the need to define static routes on the Cisco devices?  We would like to have the routing to the vNets handled dynamically based on availability of the routes.  I did see where BGP is not currently supported on any of the gateways, but I can find no references to OSPF.  Any information or guidance is appreciated!

VM network hanging, Windows Server 2012 R2

$
0
0

Hi,

I have a Windows 2012 R2 VM running in Azure that has had several instances of network hangs. It is one of four hosted in the same subscription and subnet, but is the only one this problem has occurred on.

All four servers are running Windows 2012 R2. One is a database server, two are running terminal services (load balanced access from thin client and Windows desktop devices for a business application) and the server with the problem is a DC, running print services, DNS and file and storage services.

These servers are access via VPN from an on-premise network. The on premise network has three more DCs, soon to be reduced to one.

The times the server has hung it has been running for two to three weeks. I have had to restart the server from the Azure management portal to get it back on the network. It appears only to be the network device has stopped working.

Event Viewer shows that at the time networking has gone offline with: time service reporting it cannot communicate with one of the in-premise DCs; Netlogon fails to dynamically register or delete a DNS record; AFD reports being unable to close a UDP socket and gives the best information about the issue stating "Closing a UDP socket with local port number 546 in process 860 is taking longer than expected. The local port number may not be available until the close operation is completed. This happens typically due to misbehaving network drivers. Ensure latest updates are installed for Windows and any third-party networking software including NIC drivers, firewalls, or other security products. "

Any tips as to where to look?

Thanks,

Lindsay

Unable to remove Dedicated Circuit Link between Express Route and VNET

$
0
0

Hello,

We are unable to remove the dedicated circuit link provisioned between our Express Route and a VNET ' BCTEQER1'. I need to decomission this express route and order a different one from another provider.

I have tried forcing the removal but haven't had any luck. Any help would be appreciated.

Here is the error message when using the Power Shell command. I have masked the service key.

MGMT> Remove-AzureDedicatedCircuitLink -ServiceKey xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx -VNetName BCTEQER1 -Verbose
VERBOSE: Performing operation "Removing Dedicated Circui Link" on Target "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx BCTEQER1".
Remove-AzureDedicatedCircuitLink : BadRequest: The specified virtual network name 'BCTEQER1' is not valid or could not be found.
At line:1 char:1
+ Remove-AzureDedicatedCircuitLink -ServiceKey xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : CloseError: (:) [Remove-AzureDedicatedCircuitLink], CloudException
    + FullyQualifiedErrorId : Microsoft.WindowsAzure.Commands.ExpressRoute.RemoveAzureDedicatedCircuitLinkCommand


How to add a A record to Azure DNS without www

$
0
0

Hi there,

i'm struggling to create an A record without www in Azure DNS. I followed the instruction from https://azure.microsoft.com/en-us/documentation/articles/dns-getstarted-create-recordset/

In my basic DNS experience i normally create an A record without www for a domain, for example contoso.com. After that i then create a CNAME record www.contoso.com, which points to contoso.com.

Thank you in advance for your help..

Azure Website in VNET cannot connect to Azure Redis

$
0
0

Hi,

So i have an Azure Website in Standard mode, and inside a Virtual network, connecting to an Azure Redis instance.

For some reason, today it can no longer connect (was working fine for last month, with no changes). When i take it out of the VNET, it connects fine.

Please explain?

More info here:  http://stackoverflow.com/questions/30906891/cant-reconnect-to-azure-redis-via-stackexchange-redis

Is there any way to create more than 10 VPN's to an Azure VNet?

$
0
0

Hi

I really hope someone can help. We are midway through a multisite deployment (circa 40 in total). 

Everything going well, until I just tried to add my 11th site VPN and I can't.  I google and see that there is a 10 site max on the VPN connections to an Azure VNet. 

Can anyone advise if there is a way around this otherwise I am in deep, deep doodoo!

Any help would be very much appreciated

Thanks

Jake  

TrafficManager with API Management not working

$
0
0

I am having an issue where the TrafficManager isn’’t working, even though both endpoints are showing green:

targetbaseapi-dev.trafficmanager.net

It should redirect to these two endpoints:

targetbaseapidevwest.portal.azure-api.net

targetbaseapideveast.portal.azure-api.net

When trying to go to http(s)://targetbaseapi-dev.trafficmanager.net it gives a 503 error saying “Service Unavailable”, but if you go to the endpoint links individually they work.

Here are the Powershell commands used to manually add the API Management resources to the TrafficManager (since only web and cloud apps are supported in the UI portal):

Add-AzureTrafficManagerEndpoint -TrafficManagerProfile $TrafficManagerProfile -DomainName "targetbaseapideveast.portal.azure-api.net" -Type "Any" -Status "Enabled" -Location "East US" | Set-AzureTrafficManagerProfile

Add-AzureTrafficManagerEndpoint -TrafficManagerProfile $TrafficManagerProfile -DomainName targetbaseapidevwest.portal.azure-api.net -Type "Any" -Status "Enabled" -Location "West US" | Set-AzureTrafficManagerProfile

Thank you!

VPN Point-to-site limitations

$
0
0

Hi,

What is the maximum number of clients for point to site VPN? Also, is it possible to connect clients to the on premise network through Azure VPN?

Network Load Balancing with client affinity as Single.

$
0
0

Hi,

I have configured Network Load Balancing and added two hosts in a cluster. (Issue: Load is only on one server not forwarding to another server added in the cluster).

I have two host (Host 1 and Host 2) where application is deployed and which is added in a cluster NLB. When I am setting Port rules as "Single" in cluster properties then all load (client incoming request) forwarding to only one server (Host 1) and it is not distributed to other server i.e. Host 2.

I will appreciate If someone can help me in this scenario.

Thank You.

Best Regards,

Nikhil Gupta




Hostname resolve issue

$
0
0

Hi,

I'm newbie on Windows Azure cloud. I have created Linux VM and hosted a web i.e www.truesemantic.com. And our users are experiencing host-name request timeout issue. We have our own DNS server not in Azure DNS server. It was working good before hosted in Azure. Please see the tracert report below.

C:\Users\user>tracert -d www.truesemantic.com

Tracing route to truesem1.cloudapp.net [104.210.4.10
over a maximum of 30 hops:

  1     2 ms     1 ms     2 ms  14.140.249.129
  2    13 ms     3 ms    18 ms  14.140.249.17
  3     3 ms    17 ms    26 ms  121.243.59.253
  4    18 ms    21 ms    17 ms  172.31.16.193
  5    15 ms    14 ms    23 ms  180.87.36.9
  6    49 ms    64 ms    47 ms  180.87.36.6
  7    52 ms    49 ms    54 ms  180.87.37.14
  8    52 ms    50 ms    50 ms  116.0.83.42
  9   131 ms   129 ms   131 ms  207.46.38.249
 10   130 ms   129 ms   130 ms  204.152.140.180
 11   231 ms   229 ms   228 ms  207.46.46.148
 12   234 ms   231 ms   235 ms  207.46.47.10
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15   273 ms   272 ms   270 ms  191.234.85.12
 16   274 ms   274 ms   274 ms  191.234.81.166
 17     *        *        *     Request timed out.
 18   284 ms   283 ms   284 ms  204.152.141.39
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23   282 ms     *      284 ms  100.76.50.190
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

II) Why are we having two CNAME records in dnsstuff report. Actually I have created one CNAME record to my domain.

Domain literal has an address record provided through one or more CNAME lookups, which will slow down clients attempting to resolve this host.

<tt style="color:#303030;font-size:11px;line-height:14.8500003814697px;">www.truesemantic.com. | truesem1.cloudapp.net. | 604800
truesem1.cloudapp.net. | 54.235.159.97 | 120</tt>

<tt style="color:#303030;font-size:11px;line-height:14.8500003814697px;">Could please any one help to resolve the issue :)</tt>

Thanks in advance


[PGSQL] Cannot assign requested address

$
0
0

I have my site and VM on Azure. PGSQL is on VM. Site and VM is in VPN.
I'm using PDO_pgsql to connect to my DB:

new PDO("pgsql:host=10.0.0.4;port=5432;dbname=db;connect_timeout=5;sslmode=require;options='--client_encoding=UTF8'",
$username, $password,
array(PDO::ATTR_PERSISTENT => true, PDO::ATTR_ERRMODE => PDO::ERRMODE_EXCEPTION));


And when I'm trying to connect, getting this error:

SQLSTATE[08006] [7] could not connect to server: Cannot assign requested address (0x00002741/10049)

I already tryed to resync certs and recreate gateway with no result. And yes, I can connect to DB from my PC by VIP.

What can cause such error?

My subnets during VM deployment are not shown

$
0
0

I have created 2 subnets:



When I now want to create a new VM - catalog based - I am not allowed to choose one of my subnets. I have choosen add new cloud service:

So after deployment is finished, I find my new VM in a wrong subnet: 100.x.x.x.

Could you please help me here?

thanks&regards,

Frank



Azure AlwaysOn Listener Connection String

$
0
0

I am trying to configure my webapp to use a listener however am unable to get it to connect to the database.

currently 

using the DNS name of the cloud service + sql port works to a single database

however i cannot get it to connect to the Avliablity group listener, please help

Azure DNS: testing CNAME with NSLOOKUP does not show expected result

$
0
0

Hi there,

i'm trying to create a CNAME record, and then test it with NSLOOKUP, but the result is not what i expected:

1. i create an A record for a domain:

$rs = New-AzureDnsRecordSet -Name "@" -RecordType "A" -ZoneName "contoso.com" -ResourceGroupName "MyAzureResourceGroup" -Ttl 60
Add-AzureDnsRecordConfig -RecordSet $rs -Ipv4Address 1.2.3.4
Set-AzureDnsRecordSet -RecordSet $rs

2. i create an CNAME record pointing to the A record of the domain domain:

$rs = New-AzureDnsRecordSet -Name "www" -RecordType "CNAME" -ZoneName "contoso.com" -ResourceGroupName "MyAzureResourceGroup" -Ttl 60
Add-AzureDnsRecordConfig -RecordSet $rs -Cname "contoso.com"
Set-AzureDnsRecordSet -RecordSet $rs

3. i test the resolving with NSLOOKUP

  • the A record resolves as expected

> nslookup contoso.com ns1-09.azure-dns.com
Server: Unknown
Address: 208.76.47.9
Name: contoso.com
Address: 1.2.3.4
  • the CNAME record shows no adress and alias

> nslookup www.contoso.com ns1-09.azure-dns.com
Server: Unknown
Address: 208.76.47.9
Name: www.contoso.com
  • my expected result would look like this

> nslookup www.contoso.com ns1-09.azure-dns.com
Server: Unknown
Address: 208.76.47.9
Name: contoso.com
Address: 1.2.3.4
Aliases: www.contoso.com

Multiple site-to-site VPN with Azure

$
0
0

Hi all,

Some branch offices in my company need to connect to Azure with a site-to-site VPN.

I would like to know if it's possible to declare multiple VPN site-to-site connections (1 per branch-site) for the same virtual network?

Thanks.

Patrice

Viewing all 6513 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>