-
Notifications
You must be signed in to change notification settings - Fork 9
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
No Domain Connect config found for domain #37
Comments
I had the same issue since yesterday. Nothing helps. Tried multiple times to make a new setup. Since 1 hour all working fine for now. It seems the where some problems on provider side. |
Yes, the API was not available for few hours at IONOS. All back online now. |
I still get the same error when trying to set a domain Has it to be a txt or a cname record? 🤔 |
@DATKTV formally it is TXT record but at IONOS we use CNAME at another host (in the end it's the same). Here the valid output
|
This is my output. Aside from the line >
|
@DATKTV , so you have mixed the type and the content of the record. |
@DATKTV now it's correct |
@pawel-kow thank you very much. It works again 👍 |
Until yesterday everything worked fine. But today when I try to setup a domain this error is raised:
Traceback (most recent call last):
File "/home/haproxyuser/.local/lib/python3.6/site-packages/dyndns/domain_setup.py", line 16, in main
config = dc.get_domain_config(domain)
File "/home/haproxyuser/.local/lib/python3.6/site-packages/domainconnect/domainconnect.py", line 245, in get_domain_config
ret = self._get_domain_config_for_root(domain_root, domain_connect_api)
File "/home/haproxyuser/.local/lib/python3.6/site-packages/domainconnect/domainconnect.py", line 271, in _get_domain_config_for_root
raise NoDomainConnectSettingsException('No Domain Connect config found for {}.'.format(domain_root))
domainconnect.domainconnect.NoDomainConnectSettingsException: No Domain Connect config found for my.domain
I tried to solve it with issue #33 and #35 but it didn't help.
Do you have an idea, what is wrong?
The text was updated successfully, but these errors were encountered: