Re: EPP host renames

InterNetX - Volker Janzen <[email protected]>
Newsgroups gmane.ietf.provreg
Message-ID <[email protected]>
Hi Seth,

funny thing, we discussed this issue in the last days. This is a test
case I build for our QA suite (using generic domain names as example):

- Create domain example.com.
- Create host objects ns1.example.com and ns2.example.com and
  add them to example.com.
- Create domain otherdomain.com with nameservers ns1.example.com and
  ns2.example.com.
- Remove nameservers ns1.example.com and ns2.example.com from
  domain example.com.
- Delete domain example.com.

Now there may be two answers from the EPP server:

- 1001, action pending
- 2305, Object association prohibits operation

In case of 2305, we as a registrar need to take extra steps to delete
example.com. The best option in my opinion is: rename the
ns1.example.com and ns2.example.com to something that is out of the
(.com) zone (and remove all GLUE IPs!).

If the Google registry would allow the delete of the domain anyway (and
return 1001), we would be fine with that. Otherwhise I'd recommend
implementing host rename.

One thing to keep in mind: if we manage otherdomain.com, we'd be able to
remove the GLUE hosts from this domain name, which in pain on our side.
If the otherdomain.com is not managed by us, we're not capable of doing
so and we would not be able to delete the domain name.

Hope this helps.


Kind regards,
	Volker Janzen (Senior Developer)

-- 
InterNetX GmbH
Maximilianstr. 6
93047 Regensburg
Germany

Tel: +49 941 59559-0
Fax: +49 941 59579-050

www.internetx.com
www.facebook.com/InterNetX
www.twitter.com/InterNetX

Geschäftsführer/CEO: Thomas Mörz
Amtsgericht Regensburg, HRB 7142

GPG-Key: 0x186C5F77
GPG-Fingerprint: 392E 8730 FE23 DCE8 8878 8524 5361 BCCC 186C 5F77


_______________________________________________
provreg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/provreg
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.