{"id":1600,"date":"2017-02-10T15:52:25","date_gmt":"2017-02-10T13:52:25","guid":{"rendered":"https:\/\/www.tld.sc\/en\/?p=1600"},"modified":"2017-02-10T15:52:25","modified_gmt":"2017-02-10T13:52:25","slug":"dns-belgium-switches-to-the-cloud","status":"publish","type":"post","link":"https:\/\/www.bnamed.blog\/en\/2017\/02\/dns-belgium-switches-to-the-cloud\/","title":{"rendered":"DNS Belgium switches to the cloud"},"content":{"rendered":"<p><img decoding=\"async\" loading=\"lazy\" class=\"alignright size-full wp-image-1304\" src=\"https:\/\/www.tld.sc\/en\/wp-content\/uploads\/2013\/11\/dnsbelgium.png\" alt=\"\" width=\"238\" height=\"71\" \/>On Saturday February 11th DNS Belgium will switch their technical system for registering and managing domain names to the Amazon cloud (AWS). The migration will start at 9am and it will probably take until late afternoon before all services will be available again. <!--more--><\/p>\n<p>Meanwhile all existing .be domain names remain active. However it won&#8217;t be possible to register new .be names or to make changes to existing registrations. Also checking whether a name has already been registered and by whom won&#8217;t be possible.<br \/>\nUntil now the DNS Belgium system ran on dedicated servers co-located in professional datacenters. As far as we could find, they&#8217;re one of the first registries to switch their services to &#8220;the clud&#8221;. Within Europe there are no other country code registries who have already done this. However the Swedish registry is also investigating this possibility.<\/p>\n<p>We spoke with Philip Du Bois, General Manager of DNS Belgium about the consequences (and dangers) regarding this switch.<\/p>\n<p>TLD.sc: Is this switch interesting financially?<\/p>\n<p>Du Bois: Financially it is indeed a bit more interesting, however this wasn&#8217;t by all means our main reason.<br \/>\nOn the long term we will definitely save more because it won&#8217;t no longer be required to upgrade every few years. The main advantage is we will now have more time to automate and we will have <span id=\"result_box\" class=\"\" lang=\"en\"><span class=\"\">the ability<\/span> <span class=\"\">to describe<\/span> all aspects of our platform code (software defined)<span class=\"\">, which increases<\/span> <span class=\"\">the<\/span> <span class=\"\">quality<\/span> and therefore the security<span class=\"\">.<\/span><\/span><\/p>\n<p>TLD.sc: This &#8220;cloud&#8221; also offers great advantages regarding reliability. <span id=\"result_box\" class=\"\" lang=\"en\"><span class=\"\">With a failure it <\/span>can be restarted in a different virtual environment, something with isn&#8217;t so obvious with <span class=\"\">physical hardware<\/span>. Are there also any <span class=\"\">disadvantages?<\/span><\/span><\/p>\n<p>Du Bois: Until now we haven&#8217;t experienced any.<\/p>\n<p>TLD.sc: <span id=\"result_box\" class=\"\" lang=\"en\"><span title=\"TLD.sc: Is de beveiliging tegen hacking even sterk als op eigen hardware?\n\n\">Is the protection against hacking as strong as on your own hardware?<br \/>\n<\/span><\/span><\/p>\n<p>Du Bois: <span id=\"result_box\" class=\"\" lang=\"en\"><span title=\"Lut: Hoewel we in 2 gereputeerde datacenters in Belgi\u00eb onze co-location doen (deden) zijn we ervan overtuigd dat de AWS datacenters beter beveiligd zijn omdat er niemand van een 3e partij binnenkomt.\">Although we do (did) our co-location in two reputable data centres in Belgium, we are convinced that the AWS data centres are more secure because no one from a 3rd party comes in. <\/span><span title=\"Bij een co-location zijn er soms ook medewerkers van andere bedrijven in het gebouw.\n\n\">With a co-location sometimes employees of other companies are in the building.<\/span><\/span><\/p>\n<p>TLD.sc: <span id=\"result_box\" class=\"\" lang=\"en\"><span title=\"TLD.sc: Betekent dit dat persoonlijke adresgegevens (die niet altijd in de WHOIS getoond worden) nu te grabbel liggen voor bijvoorbeeld Amerikaanse inlichtingsdiensten?\n\n\">Does this mean that personal addresses (which aren&#8217;t always shown in the WHOIS) are now up for grabs for, for example, US intelligence services?<\/span><\/span><\/p>\n<p>Du Bois: Obviously this has also been <span id=\"result_box\" class=\"\" lang=\"en\"><span title=\"Du Bois: Ook dit is uiteraard uitvoerig besproken en bestudeerd.\">widely discussed and studied. <\/span><span title=\"Alle data (zowel op het netwerk als op de disk) zijn ge\u00ebncrypteerd en worden bewaard op servers binnen de EU.\">All data (both on the network and on the disc) are encrypted and stored on servers in the EU. <\/span><span title=\"Het is dus in principe niet mogelijk dat AWS aan VS instanties toegang geeft tot onze niet-versleutelde data.\">It is therefore not possible, in principle, that AWS gives access to US authorities to our non-encrypted data. <\/span><span title=\"Onze data zullen ook de EU grenzen niet overschrijden en er is al zeker geen sprake van transport van gegevens richting de VS.\n\">Our data will not exceed the EU limits and there is certainly no question of transport of data toward the US<br \/>\n<\/span><span title=\"AWS heeft ook het principe dat, als er een request van de VS zou binnenkomen, ze ons default hiervan verwittigen.\">AWS also has the principle that, if there would come a US request, they inform us of this by default. <\/span><span title=\"Op die manier kunnen wij onze positie evalueren en gepast reageren.\">That way we can evaluate our position and respond appropriately. <\/span><span title=\"Indien we de vraag ongepast of disproportioneel vinden, zullen we onmiddellijk de nodige juridische procedures opstarten en ons verzetten tegen het doorsturen van de informatie.\">If we find the question inappropriate or disproportionate, we will immediately initiate the necessary legal proceedings and oppose the transmission of the information. <\/span><span title=\"Indien de vraag wel gefundeerd en proportioneel is, zullen we met de US Law enforcement samenwerken zoals we dit zouden doen met onze lokale veiligheidsdiensten en in overeenstemming met de waarborgen die in onze T&amp;C voor domeinnaamhouders opgenomen zijn.\">If the demand is justified and proportional, we will work with the US Law enforcement as we would do with our local security forces and in accordance with the guarantees provided for domain name holders in our T &amp; C.<\/span><\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>On Saturday February 11th DNS Belgium will switch their technical system for registering and managing domain names to the Amazon cloud (AWS). The migration will start at 9am and it will probably take until late afternoon before all services will be available again.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/posts\/1600"}],"collection":[{"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/comments?post=1600"}],"version-history":[{"count":1,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/posts\/1600\/revisions"}],"predecessor-version":[{"id":1601,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/posts\/1600\/revisions\/1601"}],"wp:attachment":[{"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/media?parent=1600"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/categories?post=1600"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/tags?post=1600"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}