Inwx returns domain name that couldn't be managed

[insxa]

If i use inwx.com what should i enter ?

[insxa]

I have loged normaly regardless of domain extension. It loads other failed domain names nad one is missed in list

[insxa]

It allow adding all domains even they are pointed to external DNS, For Namecheap when i try domains, only can be added domains that are with Namecheap DNS and domains with external DNS cant be added.

[nemunaire]

Hi @insxa!

At happyDomain, we don’t have accounts with every provider. For INWX, we rely on DNSControl’s INWX provider implementation. Here is the documentation provided by the project to connect your INWX account: https://docs.dnscontrol.org/provider/inwx

Regarding authentication, I noticed we were not supporting the totp field for INWX accounts. I’ve just added support for it. This may help if you were having login issues.

From your messages, it looks like you are successfully connecting your INWX account, but you see both:

• domains managed via INWX DNS (zones hosted by INWX), and
• domains registered in INWX but using external DNS.

You expect that only domains managed via INWX DNS should be listed in happyDomain, instead of all domains in INWX. Is this right? as I don't have INWX account, I'm trying to imagine what issue you faced.

[insxa]

I don't mind all domains is added it's just, 3 domains are added which are not registered,they were failed,cause it's hold by the registry, one Is not in the list ad it's registered in my account. I just compared to namecheap, all domains are listed but can't add that are not pointing to namecheap DNS. In inwx all domains are added regardless of dns theyee using. I point them all to external for sale pages

[nemunaire]

The full domain list from inwx is returned to happyDomain.

We can certainly filter good domains by 1 or many of those filters:

• Status: OK to limit on currently registered domain (excluding transfer, deleted, ...)

Do you think this could be sufficient? Do you see any other field we could use to limit the list to manageable domains?

[insxa]

Yes thats good, i will try in my docker install once its releasd new version

[nemunaire]

I upgrade dnscontrol to the latest release and add a filter for inwx: happyDomain/dnscontrol@5b716e3

In fact this is not use the route domain.list, but nameserver.list. Instead of filtering on Status, which is not available on this list, I used type to only report "Master" domains, ignoring "Slaves".

You could pull the latest docker image, it includes the fix. I'm unable to test if this is right, let me know.

[insxa]

I have pulled, its all the same, one domain is missing, not existing are show

[insxa]

How can i pull image with fix ?

[nemunaire]

With docker compose, run:

docker compose pull

before docker compose up

Or:

docker pull happydomain/happydomain

You should see:

2026/05/26 01:29:57 This is happyDomain master-c22cdc91e876d3c7ecdd5d2872670de86a3de1ba-rev-c22cdc9-dirty

Or any new commit reference you should see in https://github.com/happyDomain/happydomain/commits/master/:

[insxa]

i have pulled latest commit, its the same thing with inwx

[nemunaire]

Thanks for testing.

Unfortunately, without an INWX account on our side, this is very difficult for us to debug properly. The current implementation mostly relies on DNSControl’s INWX provider behavior, and we are somewhat limited in what we can validate ourselves.

From what we understand, management of domains using external DNS still works correctly, which is the main supported use case for happyDomain. The remaining issue seems to be related to how INWX reports some domains through its API.

At the moment, we probably won’t investigate this further unless we can reproduce the issue ourselves or get more detailed information from the INWX API responses.

[nemunaire]

Hi @insxa!

I recently worked on #50 where domains were not manageable by happyDomain due to the use of pseudo-DNS records.
I suspect that the issue you encounter with some of your INWX domains was related to this (as it seems not related to what I tried to fix already).

Could you give a try to the latest published Docker image?

Also, I see that I don't ask you what was the exact error message you see? and if the container logs shows anything interesting?
This could help to advance in understanding the root cause of the issue.