$ host -t A onlydomains.com.au
onlydomains.com.au has address 198.50.252.65
$ curl -v https://onlydomains.com.au/
* Trying 198.50.252.65:443...
* connect to 198.50.252.65 port 443 failed: Connection refused
* Failed to connect to onlydomains.com.au port 443 after 222 ms: Couldn't connect to server
* Closing connection
curl: (7) Failed to connect to onlydomains.com.au port 443 after 222 ms: Couldn't connect to server
$ host -t A onlydomains.com.au
onlydomains.com.au has address 198.50.252.65
$ curl -v https://onlydomains.com.au/
* Trying 198.50.252.65:443...
* connect to 198.50.252.65 port 443 failed: Connection refused
* Failed to connect to onlydomains.com.au port 443 after 222 ms: Couldn't connect to server
* Closing connection
curl: (7) Failed to connect to onlydomains.com.au port 443 after 222 ms: Couldn't connect to server


Not only that, but how embarrassing is it for a domain registrar to not be able to get domain management right? Support tell me things like:
> We only have onlydomains.com we don't use onlydomains.com.au
To which I reply:
> No, you are wrong. I've been a very long-term customer and your portal has always been available on both domains. You don't know your own company's history.
Not only that, but how embarrassing is it for a domain registrar to not be able to get domain management right? Support tell me things like:
> We only have onlydomains.com we don't use onlydomains.com.au
To which I reply:
> No, you are wrong. I've been a very long-term customer and your portal has always been available on both domains. You don't know your own company's history.