Hello And thanks for joining me again for Cyber Aires. Microsoft Azure Administrator A Z 103 course I'm Will Carlson. And this is Episode 36 public and private I p addresses.
In today's episode, we're gonna talk about some of the differences between public and private I p addresses and what assets they're associated with. Here in Azure,
we're gonna talk about which resource is in azure support, which types of addresses, and that's gonna very based on the asset type. And then we're gonna go in and configure a public and a private I p address on a virtual machine as well.
Ticket started private I p addresses are going to be those that are not row doble to the public Internet. These air gonna be addresses that are only useful within the azure environment.
And we have a couple of resource is here that private I P addresses apply to virtual machines, internal load balancers and application gateways or a Z 103 The 1st 2 of these are gonna be particularly useful and meaningful likely to be testable material. And you can see the association column here is going to be
what on that device is the private I P address actually associated with.
So when I go to change the private I P address on a virtual machine, I'm gonna do that by making changes to the network interface card of that virtual machine.
And you can see that all of these private, all of these resource is support both dynamic and static. Private I p addresses
Now the association point for an internal load Balancer doesn't make sense yet. Don't worry. We're gonna have episode dedicated to discussion about internal and external public load balancers.
The other type of I p address we're gonna run into here in Azure is a public i p address. And these clearly are going to be those that are addressable over the Internet over the public Internet. We have four. Resource is here that public I p addresses can be associated with.
And the same information here is faras What actually do these public I p addresses associate with on the resource
and whether or not they could be dynamic or static Notice VP and gateways and application gateways do not support static public I p addresses
to dive into portal and make this all make a little more sense. We're going to start by going in here to our virtual machines blade and clicking on one of the virtual machines that we currently have set up.
The first I p address that we're gonna work on changing is going to be the private I. P. Address. Every resource here in Azure is going to have a private i p address so we can communicate with it within the azure environment
and to change the private i p address on a virtual machine. We're gonna come in here to networking
in the networking blade of a virtual machine. We can see quite a lot of information all the way from information about the network interface card itself and also some of the port rules that are associated with our network security group. But for this episode, in order to change that, in order to change that private I p address,
we're gonna go ahead and click on the name of the network interface card,
and that brings us into the network interface card blade. Now, to make the change, I can come down here to I p configuration.
I can click here on the I p that's already assigned to this network interface card.
And I can go ahead and set the private eye p from dynamic to static.
Simply change it to static. Set the address to be whatever it is that I want. Keep in mind, this has to be an I. P. Address that has not already been assigned by Azure.
And I can see here a warning that changing this is going to cause the virtual machine to need to be rebooted. So keep that in mind when you're making this initial configuration change that it really is wise to do this on the initial set up before this machine is varying production workloads.
Now, that would seem pretty apparent to those of us that have managed infrastructure ourselves. Internally, it's pretty standard practice to make everything have a static I p address.
That's not gonna be on by default. Here in Azure Azure is going to assume that you're going to use the baked Indian s server that gets deployed as a virtual as part of your virtual network here in the azure environment.
I can also see here interestingly, that this machine also has a public I p address already enabled, or we could go ahead and said and change that here as well.
I can't save changes,
and that's all there is to changing the private eye p from dynamic to static.
Another way to get in here and to see the same thing in a little bit different way would be to come in through the resource group
and go into the IittIe resource group, where my virtual machine is. That
and I can see the files in Virtual Machine is right here
and then looking through this list I can see right here files ing 8 43 is actually the network interface that's associated with this virtual machine. So I could click on this,
and that gets me back to the same page that I got to buy navigating through the virtual machine networking blade.
If we go back here to the I T. Resource Group,
I can also see the public I p address resource that's associated with the file sink virtual machine.
In order to change the public I p from dynamic to static, I can simply click on that resource, come over here to configuration,
and then I can change the assignment of this I p from dynamic to static so changing dynamic to static on both a private and the public I p addresses largely similar. We simply have to find the resource that is that I p address and then make the change at that point in time
Now for public I p addresses. There are a few other interesting configuration items here, and we could go ahead and set an idle time out.
An adult time out is going to make sure that TCP and http connections are kept open regardless of whether or not they're receiving to keep alive from the client. We can also go in and set a D. N s label that creates an A record in azure D. N s so that we can access this particular resource using de en ESAs well.
And we can also go in and set some alias records for this particular resource if we wanted to track it differently. Even still,
we're not gonna make any changes to the public i p address today. But I hope you can see that by navigating to the resource of the network interface card or the public i p address itself That's how we're going to make changes to whether or not those addresses are static or dynamic.
So what if we need to add a public i p address to a resource that doesn't already have one? So for this example, we're gonna go ahead and click back into the I T. Resource Group.
We're gonna click on our service desk Of'em.
Now we could go back into the networking blade of this particular VM. We could click on our network interface card,
go back to I p configurations and click on this I p address here
and we can see that the public I p addresses disabled so we could go ahead and enable the public i p address from this blade and that would deploy a public i p address to this virtual machine.
Another way of getting this done would be by going up here to create a resource and searching for public I p address.
And then we can create one from here.
Once we've created a public I p address through the re create a resource blade
that doesn't associate that public I p address with anything. All I did was create a public I p address, and it's just simply sitting in this resource group as an un deployed resource. Essentially,
I can see it here as the service desk B m. I t
go ahead and click on that and get down into that public I p address resource. And the trick here is to associate this public I p with a resource. We don't associate this of the load balancer will associate with a network interface of our service desk of'em
and I can select. Okay,
that's the longer way of doing what we could have done simply through the VM blade. But it is another way to get that done. Get this a couple of more options on how we set up the I P. And it also allows us to configure public I p addresses with other resource is load balancers in this example.
So in today's discussion, we went through how we can assign a public i p address to a resource in azure two ways. In fact,
we talked about making public and private I p addresses static and remember that doing so will oftentimes result in a reboot. Azure is kind enough to warn us when that is necessary.
And we also configured I p addresses on a virtual machine here in the portal as well. Coming up next, we're going to talk again from the networking perspective about service in points, what they do for us and why they really are a great solution for a number of use cases.
Thanks for joining me today. I'm looking forward to the service in point episode coming up very soon.