rbind / support

Technical support for rbind
https://support.rbind.io
MIT License
48 stars 24 forks source link

Request for rbind.io subdomain #926

Closed brendonkoh closed 1 year ago

brendonkoh commented 1 year ago

Netlify website address

brendonkoh-portfolio.netlify.app

Preferred rbind.io subdomain

brendon.rbind.io

Agreement

nanxstats commented 1 year ago

@brendonkoh We have configured the rbind subdomain you requested. Please:

  1. Add the rbind subdomain in your Netlify account as the custom domain to your site, as is shown below. Simply use your subdomain.rbind.io as the record, no www needed.

  1. There might be messages saying "DNS verification failed" or "check DNS configuration" on Netlify after adding the rbind subdomain -- they can be safely ignored as long as the site renders properly.

  2. You may also find the last two sections of this post helpful for redirecting HTTP traffic to HTTPS automatically.

Thanks! -Nan

brendonkoh commented 1 year ago

Hello @nanxstats thanks so much for your help with this!

I have some issues adding the subdomain as a custom domain - it states that the subdomain is already being managed by another team. Would you have any suggestions on how I could work around this?

image

Best, Brendon

nanxstats commented 1 year ago

@yihui Now I also see the same message above when adding a rbind.io subdomain on Netlify. Do you see the same issue?

yihui commented 1 year ago

Sorry I have no idea what that means. At least rbind.io is not managed by Netlify DNS. I'm not sure if anyone else set up their subdomain with Netlify DNS, and don't know how to find it out...

nanxstats commented 1 year ago

ChatGPT tells me to use dig, which is technically correct and impresive.

#!/bin/bash

while read subdomain; do
  ns=$(dig +short NS "$subdomain")
  if [[ "$ns" =~ "netlifydns.com" ]]; then
    echo "$subdomain is managed by Netlify DNS"
  else
    echo "$subdomain is not managed by Netlify DNS"
  fi
done < subdomains.txt

However, the result is not useful because that's unlikely the root cause here.

Maybe folks from Netlify updated some of their backend logic? I see this exact question is poping up on their support site since last week. For example: 2022-12-26, 2022-12-28, 2022-12-30, 2023-01-05.

nanxstats commented 1 year ago

Looks like it's working now - so I'm closing this.