I have a domain to which I have access to the DNS administration, but my registrar does not have an API.
I have a VPS that I host my own websites.
I have a home fibre connection that sometimes changes IP and my home (Raspberry Pi) VPN becomes impossible to connect to as I do not know the new public IP.
As a workaround I have set up PushBullet (along with a script that runs daily) to send the new public IP to my phone, so i can update my VPN client and be able to access my home VPN. All works well.
I'm getting pretty annoyed with the frequency at which my IP changes and I have to keep editing and re-importing the VPN profile on my phone. I twon't let me change the IP without re-importing. Not the end of the world, but not the point.
As I have my own domain and VPS I was wondering how I could go about utilising my existing assets to create, essentially, a DIY DNS server or "forwarder" so I can create a subdomain to use in my config files, but also write a script on my Raspberry Pi to automatically update my VPS with the new IP so that any request (OpenVPN traffic) is sent to my Rasperry Pi server?
I could join up DynDNS or A-N-Other dynamic DNS provider, but I think I have the right tools.
I'm not looking at changing my name servers or anything like that.... my domains and websites all work perfectly as they are...
Would this be a job for BIND? Could IPTables suffice, given it can be defined to specific traffic?