Error 2201 with new domains?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Goodings Media
    Confirmed User
    • Apr 2007
    • 1987

    #1

    Error 2201 with new domains?

    Hiya guys,

    Ive had my nameservers registered for about a week now.

    When I try and change the nameservers on any domains (with Moniker or GoDaddy) I try to set them to ns1 and ns2.goodingsmedia.com and get

    "Authorization error 2201"

    Ive been in touch with the registrar who says my nameservers are working fine, and yeah if you ping them or run any checks on them they are apparently working fine.

    Ive checked to make sure the DNS settings for the domains on my server are set to use the new nameservers.

    Any ideas?

    Thanks
    ICQ: 446-568-913 Email: liam||goodingsmedia.com msn: [email protected]
  • harvey
    Confirmed User
    • Jul 2001
    • 9266

    #2
    maybe this helps

    Question: Why am I getting 2201 authorization error when doing an INFO command?
    Answer: You need to include the hosts= option in your INFO command.

    The INFO command allows you to retrieve both delegated host information and also subordinate host information. It does so by supporting the following 4 options:

    1. hosts="all" (delegated hosts and subordinate hosts information is being requested)
    2. hosts="del" (just the delegated hosts information is being requested)
    3. hosts="sub" (just the subordinate hosts information is being requested)
    4. hosts="none" (no information about hosts is being requested)

    We consider the subordinate host information to be privileged to the owning registrar. The only options that can be used by registrars who do not own the domain are hosts="del" and hosts="none". Use of the other 2 options will result in an "AUTHORIZATION FAILED" error.

    Another thing to note is that if no option is specified the default option is assumed to be hosts="all" based on the EPP protocol, which will result in an "AUTHORIZATION FAILED" in the case of a EPP-DOMAIN-INFO request by a non-owning registrar.

    Please also note there is currently a bug in which a hosts=none option will fail in Production. This will be corrected in a future release. The hosts=none option works in OTE. In Production, please use hosts=del.

    Please incorporate this into your INFO commands. A sample would look like this.

    <command>
    <info>
    <domain:info
    xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
    xsi:schemaLocation="urn:ietf:params:xml:ns:domain-1.0
    domain-1.0.xsd">
    <domain:name hosts="xxx">test.com</domain:name>
    </domain:info>
    </info>
    This post is endorsed by CIA, KGB, MI6, the Mafia, Illuminati, Kim Jong Il, Worldwide Ninjas Association, Klingon Empire and lolcats. Don't mess around with it, just accept it and embrace the truth

    Comment

    • Goodings Media
      Confirmed User
      • Apr 2007
      • 1987

      #3
      Erm, so the guy who runs the server needs to add that? That tech side of things isn't my comfort zone I must admit....
      ICQ: 446-568-913 Email: liam||goodingsmedia.com msn: [email protected]

      Comment

      • harvey
        Confirmed User
        • Jul 2001
        • 9266

        #4
        Originally posted by Goodings Media
        Erm, so the guy who runs the server needs to add that? That tech side of things isn't my comfort zone I must admit....
        well, tell him to check that. If that's not the problem, then I don't know
        This post is endorsed by CIA, KGB, MI6, the Mafia, Illuminati, Kim Jong Il, Worldwide Ninjas Association, Klingon Empire and lolcats. Don't mess around with it, just accept it and embrace the truth

        Comment

        • Goodings Media
          Confirmed User
          • Apr 2007
          • 1987

          #5
          thanks Ive forwarded that on
          ICQ: 446-568-913 Email: liam||goodingsmedia.com msn: [email protected]

          Comment

          Working...