Verizon FiOS WAN IP changing very often

[5mall5nail5]

Hi all - running an Asus AC66u with Merlin 376.44

I run a very low traffic blog from an ARM device (BeagleBone Black) and it'd been working very well for the last oh, month or two. I flashed to Merlin and that may be completely coincidental, but now I've noticed my IP is changing way more often. I think my IP was the same for almost a year! Now, though, it seems to change every so often. I think it was 98.114.45.xxx earlier this week, then it went to 173.xxx.xxx.xxx yesterday/today, and now it's 98.114.45.xxx again.

I have my domain (www.beagle-pi.com) setup to use my WAN IP as an A Record on GoDaddy. It works fine. Then, randomly, I go to post an update and the site doesn't resolve and it turns out my WAN IP is different. I know this is not ideal, but I haven't had the IP change for a long, long time and now it's changed 2 or 3 times just this week!

Is Verizon annoyed that I have a domain pointing to my IP (but why would it care, I use the Asus ddns setup too...) or is it because my site might be getting hits? Or, is it purely coincidental? I flashed 376.44 today but I don't think that'd release the WAN IP... though maybe?! I went from 374.xx to 376.xx today... so maybe that is what did it? Any info is helpful!

 

[Deleted member 27741]

I'm not a DNS expert so this might not work but instead of pointing to the IP address with an A record, you could point to your ddns url with CNAME?

So for example under CNAME (Alias)-
Host= www
CNAME= yourddnsurl.whatevercom.com

Of course, you could use it for other services as well, I'm honestly surprised they don't block port 80 but maybe you are talking about something else I just used www as an example.

 

[MadNachos]

I have had good results by using the Asus DDNS service that the router has an option of using with an CNAME record on my domains DNS server that points to 'whatever.asuscomm.com'. It is very seldom out of sync with a TTL value of 300. Another option would be to setup 'ddclient' on a Linux box on your LAN to update your DDNS record. I suspect that much of your issue is that GoDaddy caches a lot of DNS data and probably uses a high TTL value. If you get no love using GoDaddy consider using Amazon's DNS service. Its cheap and you can a lot of control over it.

As for FiOS, I have been on it for ages with this router (I live in one of their beta test cities so its been here a long time) and I dont notice frequent DHCP refreshes but I have never used their routers at all and I use the same MAC address of the original router I used when the service was installed. Perhaps you might want to clone the MAC from your original FiOS router if you ever had one? One of the guys that did my install said that in some areas they are very strict about watching MAC addresses as a way to prevent theft of the service. However, if that is enforced in your area it just shouldnt ever acquire an address that will give you internet access, just access to a FiOS page telling you to call support.