Aliasing a `now-serve` deployment to custom domain

Hopefully I just have a bad dependency somewhere.

Note that the domain I’m trying this with is a .bm (Bermuda) domain name, not sure if that matters but it’s definitely not common.

Deployment ID and domain truncated and replaced, respectively, for privacy.

$ now alias wKUr5n example.bm --debug

> [debug] Checking for updates.
> [debug] Up to date (0.25.0).
> [debug] /list: 703.425ms
> [debug] matched deployment wKUr5n by uid wKUr5n
> example.bm is a custom domain.
> Verifying the DNS settings for example.bm (see https://zeit.world for help)
> [debug] #1 GET /whois-ns: 287.395ms
> [debug] Retrying: Error: Whois error (500): An unexpected internal error occurred
    at Alias._callee11$ (/usr/local/lib/node_modules/now/build/lib/index.js:900:27)
    at tryCatch (/usr/local/lib/node_modules/now/node_modules/babel-runtime/regenerator/runtime.js:88:40)
    at GeneratorFunctionPrototype.invoke [as _invoke] (/usr/local/lib/node_modules/now/node_modules/babel-runtime/regenerator/runtime.js:341:22)
    at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (/usr/local/lib/node_modules/now/node_modules/babel-runtime/regenerator/runtime.js:121:21)
    at step (/usr/local/lib/node_modules/now/node_modules/babel-runtime/helpers/asyncToGenerator.js:17:30)
    at /usr/local/lib/node_modules/now/node_modules/babel-runtime/helpers/asyncToGenerator.js:28:13
    at run (/usr/local/lib/node_modules/now/node_modules/core-js/library/modules/es6.promise.js:108:47)
    at /usr/local/lib/node_modules/now/node_modules/core-js/library/modules/es6.promise.js:119:28
    at flush (/usr/local/lib/node_modules/now/node_modules/core-js/library/modules/$.microtask.js:19:5)
    at nextTickCallbackWith0Args (node.js:433:9)
> [debug] #2 GET /whois-ns: 84.056ms
> [debug] Retrying: Error: Whois error (500): An unexpected internal error occurred
    at Alias._callee11$ (/usr/local/lib/node_modules/now/build/lib/index.js:900:27)
    at tryCatch (/usr/local/lib/node_modules/now/node_modules/babel-runtime/regenerator/runtime.js:88:40)
    at GeneratorFunctionPrototype.invoke [as _invoke] (/usr/local/lib/node_modules/now/node_modules/babel-runtime/regenerator/runtime.js:341:22)
    at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (/usr/local/lib/node_modules/now/node_modules/babel-runtime/regenerator/runtime.js:121:21)
    at step (/usr/local/lib/node_modules/now/node_modules/babel-runtime/helpers/asyncToGenerator.js:17:30)
    at /usr/local/lib/node_modules/now/node_modules/babel-runtime/helpers/asyncToGenerator.js:28:13
    at run (/usr/local/lib/node_modules/now/node_modules/core-js/library/modules/es6.promise.js:108:47)
    at /usr/local/lib/node_modules/now/node_modules/core-js/library/modules/es6.promise.js:119:28
    at flush (/usr/local/lib/node_modules/now/node_modules/core-js/library/modules/$.microtask.js:19:5)
    at nextTickCallbackWith0Args (node.js:433:9)
> [debug] Retrying: FetchError: request to https://api.zeit.co/whois-ns-fallback?domain=example.bm failed, reason: socket hang up
    at ClientRequest.<anonymous> (/usr/local/lib/node_modules/now/node_modules/node-fetch/index.js:127:11)
    at emitOne (events.js:77:13)
    at ClientRequest.emit (events.js:169:7)
    at Socket.socketErrorListener (_http_client.js:265:9)
    at emitOne (events.js:77:13)
    at Socket.emit (events.js:169:7)
    at Stream.onStreamError (/usr/local/lib/node_modules/now/node_modules/spdy/lib/spdy/handle.js:89:18)
    at emitOne (events.js:77:13)
    at Stream.emit (events.js:169:7)
    at /usr/local/lib/node_modules/now/node_modules/spdy-transport/lib/spdy-transport/connection.js:752:12

[jonscottclark]

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

[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.