Dynamic DNS Behind VoIP Box
-
After searching the forums, I haven't found an answer to this. I found a couple of references that alluded to it, but nothing definitive.
Can pfSense update a dynamic DNS service, I use ZoneEdit, when the pfSense box is behind a VoIP box. The VoIP box will have the "real" IP, and pfSense will have a local one.
A previous service I used, before switching to pfSense, circumvented this issue by accessing a web page on their server, which returned the calling IP. Is there any way to use something like this, instead of relying on the WAN interface IP.
Cheers.
-
Can pfSense update a dynamic DNS service,
Yes. See Services -> Dynamic DNS
I use ZoneEdit,
pfSense Dynamic DNS can be configured for use with ZoneEdit.
when the pfSense box is behind a VoIP box. The VoIP box will have the "real" IP, and pfSense will have a local one.
pfSense Dynamic DNS servce checks the IP address of the monitored interface at 1AM. If its a private IP address then pfSense goes out to the web to get the public IP address. If the IP address has changed the dynamic DNS service is notified.
If the public IP address changes more frequently than daily then it would be better if the IP address of the monitored interface changed more frequently OR if the address was polled more frequently.
A previous service I used, before switching to pfSense, circumvented this issue by accessing a web page on their server, which returned the calling IP. Is there any way to use something like this, instead of relying on the WAN interface IP.
http://myip.dnsomatic.com is an example of such a service.
-
If its a private IP address then pfSense goes out to the web to get the public IP address.
That was the piece of "magic" I was trying to validate, as my searches didn't find anything that spelled it out.
Everything else, I already knew, as I've been running pfSense for quite a while now, with ZoneEdit handling the DNS for me.
@wallabybob:If the public IP address changes more frequently than daily then it would be better if the IP address of the monitored interface changed more frequently OR if the address was polled more frequently.
I think my searches revealed that I could load the cron package, and change the frequency of the check.
The IP only changes very rarely, but on those odd occasions, waiting for a number of hours for the update could be quite frustrating.
Now all I have to check, is if either the FTP "helper" in pfSense when it has a "private" WAN IP, or the VoIp box, is smart enough to modify the passive FTP replies to use the public IP. I know that pfSense, when it has the public IP on the WAN interface copes quite happily.
Cheers.