thank you for your reply, however i notice if i update manually duckdns ip based on the elastic ips given on aws, it will automatically update to the original ip that is given by duckdns. Do u have any suggestions on how to overcome this?
I tested it - still unchanged after 15 hours, might be a bug. you can try to setup a cron job [1] and hardcode the IP [2], or just let it discover on its own, then it should be fine. let me know if it works!
hi, my aws account only provide t2.micro as the free tier, is t4g.small provided free for you?
hey! t4g.small is offered for free until 31 Dec '25, as mentioned here - https://aws.amazon.com/ec2/faqs/#t4g-instances
it won't have that free-tier label in the list of the machines, but every AWS customer gets 750 free hours per month
note that t4g.small is burstable performance instance, so set the Credit specification (in the Advanced settings) to Standard to prevent paying for the surplus CPU credits (more info on the burstable instances here - https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/burstable-credits-baseline-concepts.html)
thank you for your reply, however i notice if i update manually duckdns ip based on the elastic ips given on aws, it will automatically update to the original ip that is given by duckdns. Do u have any suggestions on how to overcome this?
I tested it - still unchanged after 15 hours, might be a bug. you can try to setup a cron job [1] and hardcode the IP [2], or just let it discover on its own, then it should be fine. let me know if it works!
[1] - https://www.duckdns.org/install.jsp
[2] - echo url="https://www.duckdns.org/update?domains=<your subdomain>&token=a7c4d0ad-114e-40ef-ba1d-d217904a50f2&ip=<put the ip here>" | curl -k -o ~/duckdns/duck.log -K -
Sorry for the late update. Ive used other domain at noip. its easier :)))). Thank you so much for your help, this might be helpful for others.