Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
What is the good practice on Azure, always set a Static IP address on network interface or use the dynamic (DHCP) option?
I prefer to use the dynamic IP because it's easier to scale UP and down the virtual machines. But I have a sysadmin coworker and he say me that not a good practice to use the dynamic option.
These virtual machines are behind a load balancer, nobody is using it directly.
Using dynamic IP in this scenario sounds better choice, you can use static IP in below mentioned scenarios,
• When you must update firewall rules to communicate with your Azure resources.
• DNS name resolution, where a change in IP address would require updating A records.
• Your Azure resources communicate with other apps or services that use an IP address-based security model.
• You use SSL certificates linked to an IP address.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
I have created an application which I am running on my device with the local IP address. Now what I am trying to do is I want to access it through static IP so that if I am not connected to the same network I can access it through static IP. In turn, I can get this from Google when I type "my static IP" on Google.
Currently my app is running on localhost:8080 or '192.168..:8080' so whoever is connected to same server over same network is able to see that but I want to do it with static IP.
Now you should have to live this app on Heroku or an EC2 instance, then they will provide a public IP address.
So static IP just means an IP address that doesn't change. This can be local (the 192.168.x.x) or public (where you can access it from anywhere). There are some hosting options, and I'd recommend Heroku.
If this is your first time, you'll need to know some things like setting scripts for "postinstall" or setting up your Procfile, so take a look at this guide for deploying.
There are numerous other options as well for deployment with lots of information and tutorials you can Google pretty easily.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
Lets say I have a CentOS server running on AWS. When I deployed it, I got a public IP t which I can connect to from my other systems, and a Private IP on that server that shows up if I do ifconfig, which is not accessible by systems outside that VPC.
So if I add another network interface, will that create another Public IP for that instance or there can only be 1 Public IP per instance?
If so, how do we get to decide on what interface we want to route the traffic via? Does AWS take away this capability from the users? (I tried understanding Elastic IP's but having a hard time, if the answer lies in there I will try to read more)
Here is the documentation you need to read. You can attach more than one Elastic Network Interface to an EC2 instance. Each ENI can have a public IP address. That public IP address can optionally be an Elastic IP address.
Regarding how you decide what interface to route traffic to, that's entirely up to you. You would generally point specific DNS records to specific public IP addresses.
AWS EC2 instances have the concept of "Elastic Network Interfaces" (ENI).
Instances can have multiple ENIs and each ENI can have multiple IP-addresses. How many are allowed depends on the EC2 instance type and is documented in the documentation: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html
The decision how to route is up you, as you can decide which IP receives traffic (by pointing traffic to this IP) and if that IP is even allowed to receive certain traffic (via EC2 security groups and Network ACLs).
Same for outgoing traffic using the routing table on the instance itself and utilizing NAT instances.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
From our Azure environment we are calling an external webservice which does IP filtering. We are currently running on two instances of our website and the outgoing IP addresses for those sites have been added to the FW on the external webservice.
If we need to scale out, by adding say 2 more instances, will/is there a risk the new instances get a new outgoing IP?
The website in itself has a fixed public IP (to allow for DNS), but we see that one of the instances gives a different IP, so if we setup autoscaling will we loose complete control (not that we have any) of that?
Please refer to http://social.msdn.microsoft.com/Forums/azure/en-US/fd53afb7-14b8-41ca-bfcb-305bdeea413e/maintenance-notice-upcoming-changes-to-increase-capacity-for-outbound-network-calls?forum=windowsazurewebsitespreview for the list of IP addresses that can be used for outgoing connections from Azure websites.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I am hosting and application in IIS. the application is a INTRANET APPLICATION.
Already the server has 2 application hosted in it with host names
site1.k.com and site2.k.com
k.com is my domain name.
I have give host name for my site as
site3.k.com
Do i have to make DNS entry for this.
If you have a wildcard dns entry such that <anything>.k.com goes to your server, then you don't need a specific DNS entry for site3.k.com, but it might make things easier down the road if you have it.
Of course, if you don't have the wildcard set up, and you need to have the url for site3.k.com work, then yeah, it'd be required.
Now, you mention that this is intranet ... if you have a windows server configured to broadcast that it's name is site3 via WINS service, then you might get away with not having the DNS entry, but this behavior is not reliable, because WINS may or may not route to remote sites, depending on WAN and/or VPN configurations, and will generally be a pain in the ass for support.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
Simply put, I have a domain xyz.com,
I want pc.xyz.com to point to my pc IP (which is dynamic)
any available solutions?
I need a Mac client to update the changing IP, and a service to run on my domain to get those updates.
Something like http://www.dyndns.com/
( I have a domain from Dreamhost if that helps..)
You can set up a CNAME entry so that pc.xyz.com is an alias to a dyndns name. I know that doesn't strictly answer the question of how to run a dyndns-like service yourself, but it will achieve the effect you described with a minimum of effort.
How to set up DNS service dynamic / static is a good place to start. Technically, the concepts are not difficult, but much easier if you use a DNS server that is able to use MySQL or some other database. For example: MySQL BIND SDB Driver ...
The project was started so that we could automatically create sub-domains for user's homepages on account creation.
By far this is the easiest approach and allows you to write a very thin client that can send a quick web request to your system to update the DNS based on your new IP ... Maybe even build your own REST API ...
You could combine cron (or, since you're using a Mac, launchd) and the DreamHost API to achieve the result you want, as described here.