Services_dyndns not work
-
If you were on an earlier snapshot I might believe you, there was a problem early yesterday but it was fixed by the snapshot date you posted. And it works fine here.
not, the version still not work.
2.4.0-RC (amd64)
built on Thu Sep 14 22:15:51 CDT 2017 -
We're going to need a lot more detail than "not work".
Any errors in the logs? Any messages about dyndns in the logs at all?
What entries do you have on which tabs – specifically -- and how do you know they are failing or not updating correctly? How are you testing? Is the cached IP address status wrong?
-
"all service"
Utter nonsense… There are like 40 different dyndns services you could be updating in pfsense, along with custom... And what are you doing with your lan dns??
With jimp -- going to need WAY MORE detail of what your doing and what you feel is not working..
-
because i have build myself dyndns dns server in lan. Whether it is my own server or other external server can not be automatically updated.
no see any log. I can only update it manually.
 -
We're going to need a lot more detail than "not work".
Any errors in the logs? Any messages about dyndns in the logs at all?
What entries do you have on which tabs – specifically -- and how do you know they are failing or not updating correctly? How are you testing? Is the cached IP address status wrong?
After upgrading the system to the latest version, all dynamic DNS displays red ip
-
2.4.0-RC (amd64)
built on Fri Sep 15 16:04:53 CDT 2017
 -
Debugging this guy is a waste of time. Yeah, DynDNS doesn't work for you because you have goddamn frickin' insane WAN mess on your box. Delete about 90% of those (pseudo)WANs and maybe you'll get an idea which IP should actually be used. I imagine you actually got banned from whatever dyndns service you were using due to insane amount of updates caused by your configuration and all those mostly non-working VPNs and tunnels. Also must be a pure joy to use any service on that box when it's perpetually restarting services due to WAN state changes.
-
Debugging this guy is a waste of time. Yeah, DynDNS doesn't work for you because you have goddamn frickin' insane WAN mess on your box. Delete about 90% of those (pseudo)WANs and maybe you'll get an idea which IP should actually be used. I imagine you actually got banned from whatever dyndns service you were using due to insane amount of updates caused by your configuration and all those mostly non-working VPNs and tunnels. Also must be a pure joy to use any service on that box when it's perpetually restarting services due to WAN state changes.
You are not correct, all my service accounts are normal. Because I can manually update the manual and the previous version is normal, and I use these configurations for many years.
-
I try edit and delete an item, then all cache ip lost.
-
I was not suggesting to delete the DynDNS accounts. I was suggesting to sanitize your box by removing the tunnel/VPN madness altogether. Having 12 WANs is just insane.
-
I was not suggesting to delete the DynDNS accounts. I was suggesting to sanitize your box by removing the tunnel/VPN madness altogether. Having 12 WANs is just insane.
i have ipv4 wan is 3, ipv6 tunnel is 3. VPN is bgp need. The number of errors with the VPN does not matter.
-
BGP? Holy mackerel…
P.S. The number of errors with VPN does matter (ditto for the tunnels) since it's restarting services on your box over and over and over again. Actually surprised you are still able to have some connectivity maintained for some time. Fix/disable gateway monitoring for those superslow VPNs.
-
/var/run/radvd.pid -C /var/etc/radvd.conf
Could your give me the two files ?
-
Uh, the PID is process ID. It won't exist when the process is not running. As for /var/etc/radvd.conf, that's what you should give to us so that someone can finally get some relevant information.
-
2.4.1-DEVELOPMENT (amd64)
built on Sun Sep 24 21:37:23 CDT 2017
FreeBSD 11.1-RELEASE-p1dyndns not work , no any log for this. seem is dyndns service no start.
-
Either the language barrier is beyond working with, or his is just trolling dok.. He has multiple multiple threads as you know - and they are all pretty much gibberish.. And when asked for info he just repeats the nonsense..
He posted his radvd.conf in the other thread where ipv6 is not working.
https://forum.pfsense.org/index.php?topic=135858.msg748498#msg748498Where he has dhcp server running on on his gif interface that is also going up down ;)…
Love to help the guy.. But it prob best for him to just start over - it seems to be a complete cluster! And he would have better luck working in his native language section..
-
Yes, restoring factory config, and reconfiguring the box from scratch with sanity in mind would be extremely helpful for that setup. (And making backups on each step so that diagnosing where things broke is actually possible.)
-
DHCPv6 cant start is because use fd42:d42:d42:53::1 dns. pfsense should has bug for this. Using any dns address should not affect the other.
This post is devoted to dynamic DNS issues. I did not change any configuration, the previous version is working properly, and now some versions are not working properly
-
Either the language barrier is beyond working with, or his is just trolling dok.. He has multiple multiple threads as you know - and they are all pretty much gibberish.. And when asked for info he just repeats the nonsense..
He posted his radvd.conf in the other thread where ipv6 is not working.
https://forum.pfsense.org/index.php?topic=135858.msg748498#msg748498Where he has dhcp server running on on his gif interface that is also going up down ;)…
Love to help the guy.. But it prob best for him to just start over - it seems to be a complete cluster! And he would have better luck working in his native language section..
Not that I am not clear, but not enough information can be provided. I can only reflect the results of the problems,Because the system does not provide an error log or prompt.
I also have video recording to reflect the problems that arise, so this is not related to language.But still thank you for your enthusiastic participation.
such as
https://forum.pfsense.org/index.php?topic=136701.0 -
@yon:
DHCPv6 cant start is because use fd42:d42:d42:53::1 dns. pfsense should has bug for this. Using any dns address should not affect the other.
This post is devoted to dynamic DNS issues. I did not change any configuration, the previous version is working properly, and now some versions are not working properly
For example, the reason for this problem is my own groping to find, the system does not have any tips or error log. Who can think of VPN's DNS settings will affect LAN's DHCPV6？
