The wiki is gone
wiki.corp.internal doesn't open anymore.
- Get wiki.corp.internal resolving to 10.1.1.8 and opening on 443 from vm-user
- Keep intranet.corp.internal resolving to 10.1.1.4broken
Background
"wiki.corp.internal doesn't open anymore. The intranet still works." Last night the wiki moved from an old VM to vm-wiki2 at 10.1.1.8, and a cleanup deleted the old VM. Names come from the private zone corp.internal. Users sit in subnet-users, like vm-user.
- 1See it fail
Prove the problem yourself before you change anything. Reports are often wrong.
VM commands forVMs: Linuxssh vm-userWhat's this?
Opens a shell on vm-user, so the next commands run on that VM. In this lab it's a shortcut. In real Azure you'd connect through something like Azure Bastion, or SSH to an address you can reach.
nslookup wiki.corp.internalWhat's this?
Asks the VM's DNS server what IP address a name points to. Run it on the VM that has the problem, because each VM can get a different answer.
nc -zv wiki.corp.internal 443What's this?
netcat, a standard Linux tool. Tries to open a TCP connection and reports whether it worked.
-zonly check whether the port answers. Send no data-vprint the result in wordswiki.corp.internalwhere to connect443the port to try
Ticks off when the test runs on vm-user.
- 2Find where it stops
- 3Name the cause
- 4Fix it and test again
?
- Resource group, the outer dashed frame
- Virtual network, with its address space top right
- Subnet, with range and usable IPs (5 reserved)
- Network security group. A small shield on a VM's NIC means the NIC has one too
- Route table on the subnet
- VM Appliance Private endpoint
- Peering Connected Initiated or access off
- Goal working Goal broken, X marks where it stops
- Private DNS zone, dotted lines go to linked VNets
- Orange pulse: what your last command changed. Drag to pan, Ctrl and scroll to zoom.
vm-user → wiki.corp.internal:443should work: not working