
This account is no longer supported. Please follow @dnsbelgium for news, support and updates from DNS Belgium and it's products.
Leuven, Belgium
Joined June 2011
- Tweets99
- Following50
- Followers231
- Likes1
@YoungCrazyFool Geen enkel probleem hoor, u bent zeker niet de eerst die dns.be in hoort. ^KD
@YoungCrazyFool hun website, dms.be, klinkt in de radiospot heel erg als dns.be. We hebben nog zo'n vragen over 'onze' spot gekregen 2/2 ^KD
@YoungCrazyFool Beste Wim, het gaat hier om een misverstand. Wij zitten niet achter die reclamespot, maar wel DM&S 1/2 ^KD
Quick reminder that this account is no longer in use. Please follow @DNSBelgium for support, news & updates on DNS Belgium and it's products
In order to simplify our twitter presence we will no longer support this account. We invite you to follow @DNSBelgium for all future updates
@JoeriDeBouvere Gebruik je daarvoor EPP of de web-applicatie? En heb je ondertussen nog hetzelfde probleem, of is de transfer gelukt? ^KD
@JoeriDeBouvere Dag Joeri, welke problemen krijg je precies? Dan onderzoeken we dit meteen. ^KD
According to the most recent results of the APWG, the number of domains used for phishing falls by 40% ow.ly/q0D8V
We have posted a short article regarding the domain name fraud we mentioned in our previous tweets ow.ly/pWuwW
This is not a valid offer! There is no priority for .be registrants to register the same domain in .com. More info to follow soon. (2/2)
Some of our registrants were contacted by an unknown company with an offer to register a .com variant of their .be domain name... (1/2)
It seems that the online WHOIS was unavailable in some cases, where it caused an empty page to appear. The issue has now been solved.
Our online WHOIS functionality is currently unavailable. We are investigating the issue and will report on the progress.
DNS.be retweeted
DNS Belgium implements RDAP, the successor of WHOIS, as an open source project ow.ly/pevo0
As from 1:30, our websites are available again. We are currently testing the staging system, the tryout system will be tested tomorrow. ^KB
Due to unexpected events, we need more time to complete our failover test. The new ETA is set to 02:00 CEST. Thanks for your patience ^KB
The failover test has started. The registrar website is currently unavailable. We'll keep you posted about the progress of the test.
Important news for our registrars: we will run a second failover test, starting tomorrow as from 17:00 CEST ow.ly/oGAm9
