Need help? Check out our Support site, then


Deadlock on registering .NL domainname

  1. Hello Readers,

    The dutch organisation that provides .NL domains, can't register a domainname with a nameserver that doesn't itself hosts the domainname.

    The message is:
    --------------------------
    Some problems need to get fixed:
    - Some of your name servers cannot be used (are broken).

    ** Full check report:

    * primary name server "ns1.wordpress.com." [BROKEN]
    Broken: name server "ns1.wordpress.com." does not resolve.
    The name server is not (or not yet) known by the global DNS system.
    Check the spelling of the name, or wait a while until the name is
    known.

    * secondary name server "ns2.wordpress.com." [BROKEN]
    Broken: name server "ns2.wordpress.com." does not resolve.
    The name server is not (or not yet) known by the global DNS system.
    Check the spelling of the name, or wait a while until the name is
    known.

    * secondary name server "ns3.wordpress.com." [BROKEN]
    Broken: name server "ns3.wordpress.com." does not resolve.
    The name server is not (or not yet) known by the global DNS system.
    Check the spelling of the name, or wait a while until the name is
    known.

    ** More information:
    TE refers to SIDN document "Technische Eisen" (Dutch only)
    http://www.sidn.nl/doc/te.pdf
    RFC1035 RFC "Domain Names - Implementation and Specifications"
    http://rfc.net/rfc1035.html
    RFC1123 RFC "Requirements for Internet Hosts
    http://rfc.net/rfc1123.html
    RFC1912 RFC "Common DNS Operational and Configuration Errors"
    http://rfc.net/rfc1912.html
    RFC3330 RFC "Special-Use IPv4 Addresses"
    http://rfc.net/rfc3330.html
    RIPE203 "Recommendations for DNS SOA Values"
    http://www.ripe.net/ripe/docs/ripe-203.html

    ** DNScheck 4.2.1, 2008/03/25 13:58:16 CET+0100
    ------------------

    while WordPress.COM has a simmular issue:

    ------------------
    Possible problem with vanuitbewegingnaaronderneming.nl
    We were unable to verify that vanuitbewegingnaaronderneming.nl is pointing to WordPress.com. If you own this domain, follow the directions below to get it ready for your blog. If you don’t own it, try a different name to see if something else is available. If the domain is available, you may be able to register it with another registrar and then map it to your blog.

    How to resolve:
    Using the DNS tools provided by your domain registrar, remove any existing nameservers and add the following:

    NS1.WORDPRESS.COM
    NS2.WORDPRESS.COM
    NS3.WORDPRESS.COM
    Then come back here and try again. It may take several hours for our system to recognize the changes.

    -------------------

    A call to this dutch organisation (www.sidn.nl) made clear that they will not help, even when I suggested that they made a 24 hour exception on this policy.

    Does anyone have any idea how to solve this problem?

    Thanks,

    René Vaessen.

  2. I am sorry,

    Besides the problem the registrar seems to have with their own DNS Lookups, the message now says:

    Errors=1, Warnings=0, Informational=0

    ** Summary: REJECTED vanuitbewegingnaaronderneming.nl.

    Some problems need to be fixed:
    - Some of your name servers cannot be used (are broken).

    ** More information:
    TE refers to SIDN document "Technische Eisen" (in dutch)
    http://www.sidn.nl/doc/te.pdf
    RFC1035 RFC "Domain Names - Implementation and Specifications"
    http://rfc.net/rfc1035.html
    RFC1123 RFC "Requirements for Internet Hosts"
    http://rfc.net/rfc1123.html
    RFC1912 Common DNS Operational and Configuration Errors
    http://rfc.net/rfc1912.html
    RIPE203 Recommendations for DNS SOA Values
    http://www.ripe.net/ripe/docs/ripe-203.html

    ** Full check report:

    * primary name server "ns1.wordpress.com." [BROKEN]
    Broken: the name server does not know of domain "vanuitbewegingnaaronderneming.nl."
    No SOA record was found for the requested domain, because the
    addressed server does not have the domain configured and does not
    relay the request either.

    * secondary name server "ns2.wordpress.com."
    Info: name server looks correctly configured.

    * secondary name server "ns3.wordpress.com."
    Info: name server looks correctly configured.

  3. I'll get this fixed.

Topic Closed

This topic has been closed to new replies.

About this Topic