When you’re at home, you probably don’t need to worry about the ip address, but it’s a great idea to know what the ip address is first. The first address you request is the source ip address. The source ip address is the address that the first network interface (aka the ‘host’) is attached to. You can see this by running ipconfig.
For most of us, the first network interface is most likely a router. And when youre at home the internet is a single network that all hosts are attached to. So the first address you request is the address of the router that is closest to you. If you have more than one router at home, the first address you request will be the one from the router that is closest to you.
This is why if you use cable Internet you will probably not have a problem, but if you have DSL you will have issues. Because you will need to use different IP addresses to get to different web sites. And there is no easy way to tell if your router is set up to use different addresses. So you will need to use a program like ipconfig.sh to help you figure this out.
This is why it is so important to keep your router up-to-date, and set up the router to use your ISP’s address rather than your own. Also, if you are using a router, you should also be using a static IP address on your router, and not using one from your ISP. Static IP addresses are a great way to keep your DNS servers updated, as well as to prevent your router from using your ISP’s addresses.
The problem is that it is possible to have two different dhcp packets come in at the same time. You can’t have two packets that each use the same IP address. This is why your ISP address is a better choice than a static one. A static address may be good for you if your ISP has a lot of traffic, but it’s not so good if you are just using the same one for every website you visit.
If you want more control over your DNS servers, it’s best to have the same IP address in every DNS server in your Internet browser. That way you can be sure it’s actually your IP address when your site is installed and not the other way around.
In any case, it sounds like the address itself is a bit of a chicken and egg problem, because the address is also what you send to your ISP when you want to change the DNS. But when you want to be sure your DNS is set to your own IP, you better just send your own IP address.
You can still be the first to tell me, “Don’t use this.
It’s a different story when you want to do this if you connect to a public IP address. First off, you need a DNS server that’s willing to broadcast the IP address to all computers on the network. That means you need some form of encryption or something else that helps you know who belongs to what DNS entry. In a sense, you’re asking for trouble because your ISP probably isn’t going to want to give you an IP address in the first place.
I’ve talked about this a little before, but if you don’t encrypt the IP address you have a much easier time figuring out who belongs to what. You might need a server that you trust that you can reach from anywhere, or you might need to use a DNS entry that you know will work in all situations. The other possibility is that youre using DHCP, but youre using a packet that’s not a DHCP packet, so you need to decrypt it first.