Chose your color

Frequently visited

Frequently asked questions

  • 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.

More frequently asked questions

Microsoft extends Windows 11 464XLAT support to include fixed-line networks

New phase in changeover from IPv4 to IPv6 requires appropriate transition mechanisms

The Microsoft logo at Microsoft's French headquarters in Issy-les-Moulineaux
  • Thursday 22 August 2024

Microsoft has announced plans to extend support for the 464XLAT transition mechanism in Windows 11. At present, Windows 11 supports only CLAT for mobile networks, but a future version will also provide support for other network interfaces. It will then be possible to enable 464XLAT on fixed-line networks as well.

Generic support for 464XLAT is important now that we appear to have passed a critical tipping point in the transition from IPv4 to IPv6. The reason being that, having passed peak IPv4, we need to make use of a different type of transition mechanism. Until now, IPv4 has been taken as the basis, and IPv6 has been superimposed or enabled alongside IPv4. However, such 'first-generation' transition mechanisms are no longer appropriate and should be regarded as legacy.

Transition mechanisms including legacy

IPv6 should now form the starting point, with access to IPv4-only hosts enabled as an IPv6-based service. Applying that principle in combination with the NSA's security recommendations, only 3 transition mechanisms should be considered for access networks: NAT64, DNS64 and 464XLAT.

Transition mechanisms

NAT64, DNS64 and 464XLAT

NAT64 is a NAT technology that enables IPv6-only clients behind a NAT64 gateway to communicate with IPv4-only systems on the internet. To do so, the clients behind the gateway use a special IPv6 prefix in combination with the IPv4 destination address. The resulting packets are internally routed to the NAT64 gateway, which then establishes an IPv4 connection to the outside world for the client.

DNS64 supplements the NAT64 mechanism. If a caching resolver with DNS64 support receives a request for the AAAA-records for a domain name, but only A records are available, the server creates a (synthetic) AAAA resource record set for the NAT64 configuration. The combination of NAT64 and DNS64 yields a complete transition mechanism, for which no modifications to individual IPv6-only systems are required.

Finally, 464XLAT works in much the same way as DNS64, but the NAT64 destination address is compiled by the CLAT function in the network stack on the client. Applications therefore see both an IPv6 interface and an IPv4 interface (as with a dual-stack), meaning that 464XLAT also works with protocols that include IPv4 literals.

Although a DNS64 server isn't necessarily required for 464XLAT, one can still be used for traffic that definitely does not contain literals (i.e. for applications that don't use them). The advantage of 464XLAT is that the client doesn't need a (routable) IPv4 address, but IPv4 literals continue to work. The latter feature is vital for applications that don't send AAAA queries [Signal desktop].

464XLAT on fixed-line networks

464XLAT has traditionally been used on mobile networks because it enables large numbers of end users to be connected. However, as explained above, the transition mechanism should now be the norm on fixed-line networks as well. Guidance on the use of NAT64, DNS64 and 464XLAT on operator and enterprise networks is provided in RFC 8683.

Microsoft's announcement refers to implementation of the CLAT function in the network stack for fixed-line connections, and setting corresponding options on the stub resolver and the DHCP client. Apple's macOS desktop operating system has supported 464XLAT for some time now, [1] and the clatd daemon is available for Linux.

For detailed information about NAT64, DNS64 and 464XLAT, see our IPv6 FAQs.