{"id":85444,"date":"2021-09-27T12:00:00","date_gmt":"2021-09-27T11:00:00","guid":{"rendered":"https:\/\/www.avanet.com\/blog\/le-service-sophos-dyndns-myfirewallco-est-supprime\/"},"modified":"2023-08-02T07:35:49","modified_gmt":"2023-08-02T06:35:49","slug":"le-service-sophos-dyndns-myfirewallco-est-supprime","status":"publish","type":"post","link":"https:\/\/www.avanet.com\/fr\/blog\/le-service-sophos-dyndns-myfirewallco-est-supprime\/","title":{"rendered":"Le service Sophos DynDNS myfirewall.co est supprim\u00e9"},"content":{"rendered":"\n<p>De nombreux administrateurs ne sont pas connect\u00e9s en permanence au pare-feu, mais seulement lorsqu&rsquo;il y a quelque chose \u00e0 configurer, \u00e0 actualiser ou \u00e0 v\u00e9rifier. En fonction de l&rsquo;anciennet\u00e9 de la derni\u00e8re connexion au backend, divers messages d&rsquo;avertissement apparaissent dans le tableau de bord. Ceux-ci restent d&rsquo;ailleurs affich\u00e9s, m\u00eame si on les a lus. Pour une future mise \u00e0 jour sur le SFOS, il serait certainement utile de pouvoir les masquer soi-m\u00eame. \ud83e\udd14<\/p>\n\n<p>Eh bien, je m&rsquo;\u00e9gare un peu l\u00e0.\n\ud83d\ude05 Parmi ces messages d&rsquo;alerte, j&rsquo;ai r\u00e9cemment remarqu\u00e9 celui annon\u00e7ant que Sophos allait arr\u00eater le service Dynamic DNS (myfirewall.co) fin janvier 2022. <\/p>\n\n<figure class=\"wp-block-gallery has-nested-images columns-default is-cropped wp-block-gallery-1 is-layout-flex wp-block-gallery-is-layout-flex\">\n<figure class=\"wp-block-image size-large\"><a href=\"https:\/\/www.avanet.com\/assets\/sophos-firewall-dashboard-alert-ddns-discontinuing.jpg\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"668\" data-id=\"13547\" src=\"https:\/\/www.avanet.com\/assets\/sophos-firewall-dashboard-alert-ddns-discontinuing-1024x668.jpg\" alt=\"Le service Sophos DDNS est suspendu Message dans le tableau de bord du pare-feu\" class=\"wp-image-13547\" srcset=\"https:\/\/www.avanet.com\/assets\/sophos-firewall-dashboard-alert-ddns-discontinuing-1024x668.jpg 1024w, https:\/\/www.avanet.com\/assets\/sophos-firewall-dashboard-alert-ddns-discontinuing-64x42.jpg 64w, https:\/\/www.avanet.com\/assets\/sophos-firewall-dashboard-alert-ddns-discontinuing-300x196.jpg 300w, https:\/\/www.avanet.com\/assets\/sophos-firewall-dashboard-alert-ddns-discontinuing-600x391.jpg 600w, https:\/\/www.avanet.com\/assets\/sophos-firewall-dashboard-alert-ddns-discontinuing-768x501.jpg 768w, https:\/\/www.avanet.com\/assets\/sophos-firewall-dashboard-alert-ddns-discontinuing-1536x1002.jpg 1536w, https:\/\/www.avanet.com\/assets\/sophos-firewall-dashboard-alert-ddns-discontinuing-18x12.jpg 18w, https:\/\/www.avanet.com\/assets\/sophos-firewall-dashboard-alert-ddns-discontinuing.jpg 2024w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/a><\/figure>\n<\/figure>\n\n<p>Nous savons que certains ont utilis\u00e9 le service Dynamic DNS de Sophos lorsqu&rsquo;ils n&rsquo;avaient pas d&rsquo;IP fixe.\nSophos ne donne pas de raison pour l&rsquo;arr\u00eat de ce service, mais renvoie \u00e0 des fournisseurs tiers. <\/p>\n\n<figure class=\"wp-block-gallery has-nested-images columns-default is-cropped wp-block-gallery-2 is-layout-flex wp-block-gallery-is-layout-flex\">\n<figure class=\"wp-block-image size-large\"><a href=\"https:\/\/www.avanet.com\/assets\/sophos-firewall-ddns-myfirewall-co-discontinued.jpg\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"473\" data-id=\"13549\" src=\"https:\/\/www.avanet.com\/assets\/sophos-firewall-ddns-myfirewall-co-discontinued-1024x473.jpg\" alt=\"Le serveur DDNS Sophos est abandonn&#xE9;\" class=\"wp-image-13549\" srcset=\"https:\/\/www.avanet.com\/assets\/sophos-firewall-ddns-myfirewall-co-discontinued-1024x473.jpg 1024w, https:\/\/www.avanet.com\/assets\/sophos-firewall-ddns-myfirewall-co-discontinued-64x30.jpg 64w, https:\/\/www.avanet.com\/assets\/sophos-firewall-ddns-myfirewall-co-discontinued-300x139.jpg 300w, https:\/\/www.avanet.com\/assets\/sophos-firewall-ddns-myfirewall-co-discontinued-600x277.jpg 600w, https:\/\/www.avanet.com\/assets\/sophos-firewall-ddns-myfirewall-co-discontinued-768x355.jpg 768w, https:\/\/www.avanet.com\/assets\/sophos-firewall-ddns-myfirewall-co-discontinued-1536x710.jpg 1536w, https:\/\/www.avanet.com\/assets\/sophos-firewall-ddns-myfirewall-co-discontinued-18x8.jpg 18w, https:\/\/www.avanet.com\/assets\/sophos-firewall-ddns-myfirewall-co-discontinued.jpg 2048w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/a><\/figure>\n<\/figure>\n\n<h2 class=\"wp-block-heading\" id=\"h-9-anbieter-fur-ddns-als-alternative\">9 Fournisseurs de DDNS comme alternative<\/h2>\n\n<p>Nous utilisons \u00e9galement ce service, car nos fournisseurs d&rsquo;acc\u00e8s ne proposent pas d&rsquo;IP fixe sur tous les sites, ou du moins uniquement pour les connexions professionnelles, qui sont beaucoup plus ch\u00e8res.<\/p>\n\n<p>Sur le pare-feu, on a maintenant la possibilit\u00e9 de choisir les fournisseurs suivants :<\/p>\n\n<ul class=\"wp-block-list\"><li>DynDNS<\/li><li>DynAccess<\/li><li>EasyDNS<\/li><li>ZoneEdit<\/li><li>Google DDNS<\/li><li>Namecheap<\/li><li>DNS-O-Matic<\/li><li>No-IP<\/li><li>FreeDNS<\/li><\/ul>\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\"><p>Nous faisons nous-m\u00eames confiance au fournisseur No-IP.<\/p><\/blockquote>\n\n<p>Si l&rsquo;on a \u00e9galement utilis\u00e9 le nom DNS dans la configuration SSL VPN, il ne faut pas oublier de le modifier \u00e9galement et de d\u00e9ployer la nouvelle config sur les clients.<\/p>\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>De nombreux administrateurs ne sont pas connect\u00e9s en permanence au pare-feu, mais seulement lorsqu&rsquo;il y a quelque chose \u00e0 configurer, \u00e0 actualiser ou \u00e0 v\u00e9rifier. En fonction de l&rsquo;anciennet\u00e9 de la derni\u00e8re connexion au backend, divers messages d&rsquo;avertissement apparaissent dans le tableau de bord. Ceux-ci restent d&rsquo;ailleurs affich\u00e9s, m\u00eame si on les a lus. Pour [&hellip;]<\/p>\n","protected":false},"author":5,"featured_media":36943,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[371],"tags":[],"class_list":["post-85444","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-non-classifiee"],"blocksy_meta":[],"acf":[],"_links":{"self":[{"href":"https:\/\/www.avanet.com\/fr\/wp-json\/wp\/v2\/posts\/85444","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.avanet.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.avanet.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.avanet.com\/fr\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/www.avanet.com\/fr\/wp-json\/wp\/v2\/comments?post=85444"}],"version-history":[{"count":0,"href":"https:\/\/www.avanet.com\/fr\/wp-json\/wp\/v2\/posts\/85444\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.avanet.com\/fr\/wp-json\/wp\/v2\/media\/36943"}],"wp:attachment":[{"href":"https:\/\/www.avanet.com\/fr\/wp-json\/wp\/v2\/media?parent=85444"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.avanet.com\/fr\/wp-json\/wp\/v2\/categories?post=85444"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.avanet.com\/fr\/wp-json\/wp\/v2\/tags?post=85444"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}