-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Docker release #54
Comments
Hello @daerup, |
Apologies for the lack of documentation about this, but Namecheap requires that we communicate the outgoing IP address at every API call. |
Great thank you, now it works! Do you perhaps know if there is a setting for max purchase price? Also is it possible to test the connector, so that in case the domain becomes available everything works out? I also notices that some TLD do not work (.ch for example). Is there anything I can do? |
Some RDAP servers are not officially published by IANA, they seem to be functional though. I refer you to issue #41. ln -s custom_rdap_servers.example.yaml custom_rdap_servers.yaml If you are using Docker, this can be configured via volumes. I will think about a potential limitation with maximum price but if you inquire about the prices before adding a connector, you should not be surprised in theory ;) Concerning the tests, the only test that is performed is an attempt to connect to the API when you modify a connector (@vinceh121 I think this had been implemented for Namecheap too). |
There currently isn't. Although if the domain is at a premium price, it won't be bought.
While Namecheap's sandbox environment is implemented, when I developed the connector it wasn't running properly altogether. You may be able to test the sandbox by setting your |
Perfect thank you! Btw. its not possible to monitor Also, what is the definition for a premium price? |
The registry behind .io currently doesn't have RDAP support. You can see the deployment status here: https://deployment.rdap.org/ By premium price I mean buying premium domains. A premium domain is either:
|
Could you release a new docker image that includes the new providers?
The text was updated successfully, but these errors were encountered: