[FEATURE_REQUEST] Designer TLD Support

[servebeer]

Is your feature request related to a problem? If so, please describe.

Yes, I get this error when trying to monitor my custom domain (jon.irish): "An error occurred, see the logs for more info. Whois server not yet supported. We are adding new servers on a weekly basis." I assume that this error will go away when whois support is added? If not, can we get support for designer TLD's?

Describe the solution you'd like

Support for designer TLD's

Priority

Low (Nice-to-have)

Is this something you would be keen to implement

No response

[liss-bot]

If you're enjoying Dashy, consider dropping us a ⭐
_{🤖 I'm a bot, and this message was automated}

[Lissy93]

I'm not super clear on where this error occurs. But there's no reason why Dashy shouldn't work on any domain. This sounds more like an issue up stream, likley with your dns provider, or possibly firewall

[servebeer]

Hi Alicia,
So I took a look at DNS being the issue (I use an internal DNS server (MS Windows DNS)) thinking that you might be right. But when I do a "nslookup jon.irish" I do get a response:

nslookup jon.irish
Server: localhost
Address: 127.0.0.1

Non-authoritative answer:
Name: jon.irish
Address: 108.194.208.147

I then tried doing a "dig" from an internal linux system "dig jon.irish":

$ dig jon.irish

; <<>> DiG 9.18.4-2-Debian <<>> jon.irish
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53882
;; flags: qr rd ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;jon.irish. IN A

;; ANSWER SECTION:
jon.irish. 0 IN A 108.194.208.147

;; Query time: 0 msec
;; SERVER: 172.18.16.1#53(172.18.16.1) (UDP)
;; WHEN: Thu Jul 21 07:55:28 CDT 2022
;; MSG SIZE rcvd: 52

Thus it appears that name resolution is working fine. I also believe that this rules out the firewall blocking the lookup request. If you have any other suggestions, I would be happy to try them.

If it matters, I use CloudFlare as my DNS provider. I have two registered domains with them: jon.irish and irishtech.biz. The irishtech.biz domain works fine with the Domain Monitor widget.

[Lissy93]

I'm not sure I'm following. Maybe I'm misunderstanding the issue, but your domain name shouldn't have any impact on Dashy at all, as there is no domain functionality built in to the app. That's something that you would manage on your side.

I'm hosting my instance on a custom domain the normal way with a reverse proxy, and have also used fake .lan domains with local dns config just fine.

Unsure where the error message came from, but it's not from dashy.

Tell me if I'm completely misunderstanding this, but otherwise this ticket should be closed and instead opened in the right project.

[servebeer]

Let me give you a little more background (should have done this from the beginning, sorry). I own (2) domains: jon.irish and irishtech.biz. When I setup both to be monitored with the Domain Monitor widget (config below):

widgets:
  - type: domain-monitor
    options:
      domain: irishtech.biz
      apiKey: xxxxxxxxxxxxxxxxxxxx
    id: 0_1258_domainmonitor
  - type: domain-monitor
    options:
      domain: jon.irish
      apiKey: xxxxxxxxxxxxxxxxxxxx
    id: 1_1258_domainmonitor

Domain Monitor handles irishtech.biz just fine, but I get the "An error occurred, see the logs for more info. Whois server not yet supported. We are adding new servers on a weekly basis." on the jon.irish domain.

[Lissy93]

Ahhh, now that makes sense. You should have mentioned it was a widget! 😅

So this data is coming from whoapi.com. Any issues with the service, will need to be raised with them, I have no control here.

Alternatively, maybe look into using another provider for the domain info. Although of the top of my head, I don't know of any Who Is API's that are both easy for the user to sign up for, have a generous free plan, and a compatible T&Cs and privacy policy.

[servebeer]

Thanks Alicia,I went to their web site and issued an api request there, and received the same error. Hopefully they will add support for this in the future.Sent from my iPadJonOn Jul 23, 2022, at 6:34 AM, Alicia Sykes ***@***.***> wrote: Ahhh, now that makes sense. You should have mentioned it was a widget! 😅 So this data is coming from whoapi.com. Any issues with the service, will need to be raised with them, I have no control here. Alternatively, maybe look into using another provider for the domain info. Although of the top of my head, I don't know of any Who Is API's that are both easy for the user to sign up for, have a generous free plan, and a compatible T&Cs and privacy policy. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[Lissy93]

Looking at their docs, they have a list of supported tlds. And they say to just contact them to get new extensions added. Maybe that'd work

ICANN maintains WHOIS records separately for each TLD in it's own authoritative registry, which then gets propagated downstream. Since there's no central and official list of TLDs, I guess that most WhoIs APIs have to maintain their own list along with lookup endpoints. But I agree it's a bit annoying.

But like I said, if you know of a better whois api, I'd be happy to consider updating the widget to use data from elsewhere :)

[servebeer]

Thanks Alicia,I have submitted a support request with them.JonSent from my iPadOn Jul 23, 2022, at 7:00 AM, Alicia Sykes ***@***.***> wrote: Looking at their docs, they have a list of supported tlds. And they say to just contact them to get new extensions added. Maybe that'd work ICANN maintains WHOIS records separately for each TLD in it's own authoritative registry, which then gets propagated downstream. Since there's no central and official list of TLDs, I guess that most WhoIs APIs have to maintain their own list along with lookup endpoints. But I agree it's a bit annoying. But like I said, if you know of a better whois api, I'd be happy to consider updating the widget to use data from elsewhere :) —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>