Aliasing a `now-serve` deployment to custom domain about vercel

[jonscottclark]

Ok, I've followed up with the administrator to add 2 more.

[jonscottclark]

I should also mention that I told the domain administrator to set their name servers to two of the zeit.world locations and he's confirmed that he's done that. Haven't seen for my own eyes, though.

[leo]

@jonscottclark I don't think that's the reason for this error, but like mentioned here, you should use at least 4 name servers.

[jonscottclark]

I tried a number of whois lookup websites and some said the TLD wasn't supported, others responded with empty information. Took about 6 or 7 tried before I found one that worked.

% NOTE: The registry for this domain name does not publish ownership
%       records (whois records) in the standard format.  This data
%       represents the most likely status of the domain based on 
%       information provided by the Internet's domain name servers (DNS).

domain: [redacted].bm
status: taken
nameserver: london.zeit.world
nameserver: newark.zeit.world

% For more information, please visit http://www.bermudanic.bm

This is what I got from http://whois.domaintools.com/

[leo]

@jonscottclark btw: nslookup leo.im

[jonscottclark]

@leo

Non-authoritative answer:
*** Can't find [redacted].bm: No answer

[jonscottclark]

Could there potentially be a --force option if we can verify by some other means that the nameservers are legitimate?

[leo]

@jonscottclark That's interesting! If nslookup doesn't work, the name servers probably aren't set up properly. I'm not sure but it might also be related to now checking the name servers from your local device. Maybe your device doesn't yet know that there are new name servers behind the domain...

[jonscottclark]

@leo I tried clearing my DNS cache and it still failed.

I'll try with a .com domain and let you know if I run into the same issue.

[OlliV]

What's the status?

[jonscottclark]

It was discovered that the NIC responsible was/is having issues — though I wasn't told specifically what the issues were.

For what it's worth, the only site that seems to be able to return WHOIS information for .bm domains at time of writing is http://whois.domaintools.com/ — others returned no data, or threw an error.

I suppose the issue really is just how to handle 500 errors — and the fact that after running the command above and receiving those errors, that when running now alias ls, it says > 1 alias found but doesn't list it.