@ charanzova: 23 Apr 2022
@ vestager: 23 Apr 2022
There is an official #gdpr #adequacydecision for the #UnitedKingdom so we can keep transferring #PersonalData to the #UK and back because the #UK has deemed the security levels of #PD in the #EU as #adequate #Brexit #privacy Great job #EuropeanCommission https://t.co/U3zFSAHCJ9 https://t.co/exqwOfVgBB https://t.co/Qbe9yfpuXi
30 Jun 2021
#EDPS opens investigations following the #Schrems II Judgement regarding the use of cloud services provided by #Amazon Web Services #aws and #Microsoft and one regarding the use of Microsoft #Office365 by the European Commission #gdpr #privacy #cloudact https://t.co/BJP48W6WtV https://t.co/fJA1stx7oy
28 May 2021
Dutch #supervisoryAuthority first fine for a #Municipality. #Enschede city fined 600.000 for #wifitracking visitors of shopping centre for toooooo long. @toezicht_AP #GDPR #privacy #fines https://t.co/CjCPwqgUpo https://t.co/vSkoTAkoVE
29 Apr 2021
DNSCMD (as referenced in my article in SSWUG.org)Domain Name Server (DNS) mutations can be performed by scripts using the following command line commands (Windows 2000 or better) :
ExamplesAdding DNS records
Adding a new DNS record to access the server named TestServer at IP-Address 10.1.133.45 with the DNS server nlaaldns1:
dnscmd nlaaldns1.van_soest.it /recordadd van_soest.it TestServer A 10.1.133.45Adding the Alias FileServer pointing to the recently created TestServer
dnscmd nlaaldns1.van_soest.it /recordadd van_soest.it FileServer CNAME TestServer.van_soest.itTesting the correct configuration with the ping command:
c:>ping FileServer -4 Pinging TestServer.van_soest.it [10.1.133.45] with 32 bytes of data: Reply from 10.1.133.45: bytes=32 time=21ms TTL=126 Reply from 10.1.133.45: bytes=32 time=21ms TTL=126 Reply from 10.1.133.45: bytes=32 time=22ms TTL=126 Reply from 10.1.133.45: bytes=32 time=22ms TTL=126 Ping statistics for 10.1.133.45: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 21ms, Maximum = 22ms, Average = 21ms
Removing DNS records
Removing the Alias and Host DNS records without asking for confirmation (use in batches):
dnscmd nlaaldns1.van_soest.it /recorddelete van_soest.it FileServer CNAME 10.1.133.45 /f
dnscmd nlaaldns1.van_soest.it /recorddelete van_soest.it TestServer A 10.1.133.45 /f
Warning: A Windows domain name can not contain an underscore "_" according to these standards. The underscore is used in these examples as a spam counter measure.
Also read the topic Allow DNS Aliases on File Servers.
You may vote your opinion about this article:
Scripts and programming examples disclaimerUnless stated otherwise, the script sources and programming examples provided are copyrighted freeware. You may modify them, as long as a reference to the original code and hyperlink to the source page is included in the modified code and documentation. However, it is not allowed to publish (copies of) scripts and programming examples on your own site, blog, vlog, or distribute them on paper or any other medium, without prior written consent.
Many of the techniques used in these scripts, including but not limited to modifying the registry or system files and settings, impose a risk of rendering the Operating System inoperable and loss of data. Make sure you have verified full backups and the associated restore software available before running any script or programming example. Use these scripts and programming examples entirely at your own risk. All liability claims against the author in relation to material or non-material losses caused by the use, misuse or non-use of the information provided, or the use of incorrect or incomplete information, are excluded. All content is subject to change and provided without obligation.