I am looking for a domain name registrant. Where can I look it up?
The Whois is an easy-to-use tool for checking the availability of a .nl domain name. If the domain name is already taken, you can see who has registered it.
On the page looking up a domain name you will find more information about what a domain name is, how the Whois works and how the privacy of personal data is protected. Alternatively, you can go straight to look for a domain name via the Whois.
I would like to transfer my domain name to another registrar. What is the procedure?
To get your domain name transferred, you need the token (unique ID number) for your domain name. Your existing registrar has the token and is obliged to give it to you within five days, if you ask for it. The procedure for changing your registrar is described on the page transferring your domain name.
The details registered about me/my company are incorrect or out of date. How can I get them updated?
To update the contact details associated with your domain name, you need to contact your registrar. Read more about updating contact details.
Why is my domain name in quarantine?
When a domain name is cancelled, we aren't told the reason, so we can't tell you. You'll need to ask your registrar. The advantage of quarantine is that, if a name's cancelled by mistake, you can always get it back.
One common reason is that the contract between you and your registrar says you've got to renew the registration every year. If you haven't set up automatic renewal and you don't renew manually, the registration will expire.
Ik heb een klacht over mijn provider/registrar. Kan ik daarvoor bij SIDN terecht?
Wanneer je een klacht hebt over of een geschil met je registrar dan zijn er verschillende mogelijkheden om tot een oplossing te komen. Hierover lees je meer op pagina klacht over registrar. SIDN heeft geen formele klachtenprocedure voor het behandelen van een klacht over jouw registrar.
What conditions do I have to meet as a registrar?
Would you like to be able to register domain names for customers or for your own organisation by dealing directly with SIDN? If so, you can become a .nl registrar. Read more about the conditions and how to apply for registrar status on the page becoming a registrar.
It's a quick fix that stores up problems for later
Friday 19 April 2019
Although it's taken a long time for the adoption of IPv6 to get going, it isn't a good idea to disable this network stack for the sake of convenience. After all, much of the IPv6 infrastructure is now in place and is extensively used. And disabling IPv6 can actually cause problems.
Migration to IPv6 has only really got going in the last couple of years. Nevertheless, Google stats show that about a quarter of visitors now reach the company's sites using IPv6.
However, the slow early pace of IPv6 adoption means that interest in the topic has waned. System managers are no longer asking their network colleagues for it. Network managers are no longer asking their internet and hosting/colo providers for it. And end users aren't asking their access providers for it. Because IPv6 currently co-exists alongside IPv4 as a parallel network, there is also a risk of an IPv6 infrastructure that was set up earlier falling into disuse, perhaps unnoticed.
'Prefer IPv4 over IPv6'
As a result, it's not unusual for a connection to a dual-stack system to take a while to come up, due to an issue with the intermediate IPv6 network. There's then a delay before the system tries again using IPv4. You'll therefore often hear it suggested that the best thing to do is disable IPv6. However, that advice is misguided. If you can't find an answer to your IPv6 problems, or the solution is in someone else's hands, what you should do is change your client's network setting. Instead of the common 'Prefer IPv6 over IPv4' default setting, switch to 'Prefer IPv4 over IPv6'. The rationale for that is explained in this Cisco blog post. Cisco says that disabling IPv6 is treating the symptom, not the disease: the underlying network problem remains unresolved.
We're currently in the midst of transition from IPv4 to IPv6. While that transition is in progress, running a dual-stack IPv4/IPv6 set-up on a network infrastructure is temporarily unavoidable. Anyone who remains in doubt should bear in mind that the Netherlands is lagging a long way behind on IPv6 adoption [1, 2]. Consequently, people around you may be less inclined to prioritise IPv6 than their counterparts elsewhere. Meanwhile, however, the rest of the world is migrating fast.
And, in an international environment — which the internet obviously is — you can't afford to stick with an outmoded, incomplete connection. Don't forget that the annoying delay you're experiencing because of someone else's poor IPv6 set-up is exactly what others will experience if your network isn't configured correctly or doesn't support all the options. Last month, Infoblox published a blog post emphasising the reciprocal nature of a (business) internet connection: Things are fine for the companies that don't support IPv6 on the grounds that their IPv4 address stocks or NAT set-ups cover their needs. It's their customers, partners and suppliers with no IPv4 addresses left who encounter the problems.
The sooner we all switch over, the sooner we'll all be rid of the problems and expense associated with the current situation. And the sooner we can all enjoy the fruits of a fully symmetrical internet.
