Looks like it might be that I was using a custom Check IP service. Trying
on a new installation of pfSense without a custom one it worked fine.
On Fri, May 12, 2017 at 8:47 AM Vick Khera wrote:
> On Thu, May 11, 2017 at 3:40 PM, Julian Heisz
> wrote:
>
> > Are you using the default public IP fi
On Thu, May 11, 2017 at 3:40 PM, Julian Heisz
wrote:
> Are you using the default public IP finder (forget the specific term
> pfSense uses and not in a position to check at the moment) or do you have a
> custom one set up? I have a custom one set up, which works for other DDNS
> but may for some
Are you using the default public IP finder (forget the specific term
pfSense uses and not in a position to check at the moment) or do you have a
custom one set up? I have a custom one set up, which works for other DDNS
but may for some reason not work here.
On Thu, May 11, 2017, 2:47 PM Vick Khera
On Thu, May 11, 2017 at 1:06 AM, Julian Heisz
wrote:
> This appears to be an issue with pfSense, however the wiki suggests that I
> use the forum or mailing list before submitting a ticket in Redmine. Of
>
"works for me". My DNS server runs BIND 9. My pfSense sits behind a NAT
from the FiOS rout
I just set up RFC2136 on both my DNS server and pfSense. I can confirm it
works, as if I unset the "Public IP" option, it works fine (although is
useless, as it sets the A record to my private IP). However, if I unset
that option it will silently fail to do *anything*, instead choosing to do
nothin