11-27-2018
16,426,
2,136
Join Date: Sep 2000
Last Activity: 19 February 2019, 7:24 AM CST
Location: Asia pacific region
Posts: 16,426
Thanks Given: 1,658
Thanked 2,136 Times in 1,127 Posts
Yes, but having your public dynamic IP address "change rarely; typically less than once a month" is a non-contractual unique situation which is mostly "a fluke" versus a contractually obligated service. My IP address changes daily or more often, so if I needed a static public IP address, for any reason, I would just pay for it. After all, we get what we pay for. But since you can get a virtual server with a dedicated public IP address as some server farm for as little as $5 to $10 US, it is generally less expensive to host any data or application in a data center (production, development, backup, storage, cloud) and use the "cheap dynamically allocated IP address server" for home where I do not keep to ping or access from outside my LAN.
Since we were discussing "Public ip is not shown in ifconfig - Ubuntu 16.04" and the original poster seeming does not understand basic IP addressing, routing and NAT, then it I think it is safe to assume that if they really need a public IP address then they need to pay for that service from the ISP. Also, in my view (maybe I am wrong) but if they had the skills to create scripts which watched for changing IP addresses on the public side and then updated all their services and mappings to keep it all in sync, they more likely would not be asking such as question and would have known the 192.168.0.0 address block was not publicly routable nor assigned by their ISP.
At least, that is how I read it.