| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
(cherry picked from commit 74533d412818113372b7b1a4e46db48313fd965d)
|
|
|
|
|
|
| |
the domain in the GUI to update the domain's @ record. Then in the backend code, remove that from the FQDN since CloudFlare doesn't like that to be sent explicitly. Fixes #7357
Fix is confirmed to work by two forum users: https://forum.pfsense.org/index.php?topic=122099.msg699763#msg699763
|
|
|
|
| |
and for all IPv6 items
|
|
|
|
| |
(cherry picked from commit ac5ee07ee1daef2f43e728895290ca6d11efe0f3)
|
|
|
|
| |
(cherry picked from commit cb5961d1fa64a45cbec5ef5d677b57f8d62f50b5)
|
|
|
|
| |
(cherry picked from commit 15dcf1320c08eb9339eda3e6fdf04599c51694b7)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Included a checkbox to enable and disable this feature when CloudeFlare
type is selected.
Included proxied variable in the update script as well.
Defaults to false, as the is the current functionality
Added help text
Updated Last tested date
Hope this helps other people. I use both dynDNS and the Proxy service.
And by default without this feature, the proxy gets disabled. This
is a huge problem, as I have all traffic blocked except for CloudFlare.
And because I have certain other security features enabled, when the Proxy
goes disabled, The Site goes down hard to end users.
With this feature, I can ensure the proxy stays enabled.
(cherry picked from commit e10d25b4c3109347a43a729f8c098138272fe1e7)
|
|
|
|
| |
(cherry picked from commit 176d24e1206586cc67888bcbd3a4d947f043a187)
|
|
|
|
| |
(cherry picked from commit 16b163661b1d1a5bcc9a24ce023f7a06c5fb420e)
|
|
|
|
| |
(cherry picked from commit 260228142573deeb8ef5eaee34c761ca783f8cd3)
|
|
|
|
| |
(cherry picked from commit 8d8405baf12806a7f09ef8562cfb24f9083809d3)
|
|
|
|
| |
(cherry picked from commit c46412956fb629a2f7dc94ca2a553444046a39c3)
|
|
|
|
| |
(cherry picked from commit 166f4a4c67e61334791b43a21845603c1295ab2c)
|
|
|
|
| |
(cherry picked from commit 616a24828992d37ea67e810dbf9fd84ec80562e7)
|
|
|
|
| |
(cherry picked from commit cc5adcaa679686e54e4035fa5bc283b1cac085a2)
|
|
|
|
|
|
| |
Note: corresponding change to upgrade_config.inc to come in master to
correctly implement the upgrade_155_to_156 code, that is master only and
will become upgrade_158_to_159
|
|
|
|
| |
(cherry picked from commit 19b7263e859243adfcf6588533cb47b4c768765e)
|
|
|
|
| |
(cherry picked from commit 575b1dcf0bdb28c431fca420d27bdedf579ec9c4)
|
|
|
|
| |
some dyndns implementations rely on the correct HTTP header being set. the information was lost and now fixed.
|
| |
|
|
|
|
|
|
|
|
|
| |
CURLOPT_USERAGENT expect the value to the user-agent string, not the entire key-value pair.
Before this fix, HTTP header "User-Agent: User-Agent: phpDynDNS/0.7" was sent for DDNS updates.
NGINX configuration at GratisDNS will not accept a user-agent formatted in the above way.
This commit fixes GratisDNS Dynamic DNS service.
(cherry picked from commit ce9a957241c0453402d0765be0fe25e1cca48c2a)
|
|
|
|
| |
Original code for master in pull request #3061
|
| |
|
|
|
| |
The service renamed there addresses
|
|
|
|
|
| |
FreeDNS IPv6 support confirmed working using same method as v4 with v6 source address. Simple second service with _useIPv6
(cherry picked from commit ac16181a2cfefec293e0562a7bfe8e2f7140e191)
|
|
|
|
|
| |
Fixed a bug regarding a leading space in $ZoneID that causes an AWS 505 error. Also adds support for updating DNS if TTL changes.
(cherry picked from commit a4bda7563136a7b47a1d090cededdb1b1a076019)
|
|
|
|
| |
Remove "you" personalizations.
|
|
|
|
| |
(cherry picked from commit 7a2c15f527459cc82aadaf23d06895174c008320)
|
|
|
|
| |
VIPs, gateway groups, etc. correctly. Ticket #4858
|
| |
|
| |
|
|
|
| |
I tried to consolidate and make some of the message logging more consistent along the way.
|
|\ |
|
| | |
|
|/
|
|
|
|
| |
Upgrade existing entries automatically. Implements #4366
Code should be generic enough that if other DynDNS providers would work better with a separate domain field, they can pick up the feature without too much trouble.
|
| |
|
|
|
|
|
|
|
|
|
| |
By having 'proxiable' and 'proxied' values set to false, CloudFlare is turned off (i.e. not go through CloudFlare) for the domain when updating the DNS records.
Setting them to 'true' would turn CloudFlare on that domain, however the user may have disabled it for their own reasons and would not like it changed.
Instead, removing these two values will not alter the status of CloudFlare on the domain.
Tested with false/false, true/false, false/true, true/true in all scenarios.
|
| |
|
|
|
|
|
| |
SPDNS is a free DynDNS service from the German company Securepoint
Security Solutions
|
| |
|
|
|
|
|
|
| |
and bits of white space.
Note: There are plenty of files still with old-format copyright sections
in here.
|
|
|
|
| |
it applies to all types.
|
|
|
|
| |
Ticket #3858
|
| |
|
|
|
|
| |
Ticket #4990
|
|
|
|
|
|
|
| |
fixing is more complex than just fixing the variable screw up and
disabling cert validation for their SSLLabs F-graded site. Updates made on
their site even take quite some time to be reflected, seems to be a
largely abandoned service.
|
|
|
|
| |
Resubmit of #1793
|
|
|
|
|
|
| |
Resubmit of #1812
The current implementation isn't working due to API change. Credits: det0nat3 @ https://forum.pfsense.org/index.php?topic=87436.msg534817#msg534817
|
|
|