How to use domain name as provider URL?

[emclab]

Here is the snippet code for generating provider (ethersjs 5.4):

let connection = {}; connection.url = GLOBAL.PROVIDER_URL; //<<==http://www.my_domain.com??? connection.headers = { "Authorization" : Bearer ${ _tokenBesu }}; const _provider = new ethers.providers.StaticJsonRpcProvider(connection, 2018);

The GLOBAL.pROVIDER_URL used to be the server IP. address and was working fine. Is domain name OK as PROVIDER_URL? I am having some issue with domain-name instead and not sure if it is allowed here. Many thanks.

[ricmoo]

Domain names work just fine, I use them all the time. :)

[zemse]

Without any change, the code starts churning out block number with domain name. Not sure how the problem disappeared

Lol I can relate to that

[emclab]

The domain name does not work on ethers 5.4.6. Upgrading to 5.4.6 solves "unrecognized field 'type'" in tx submitted to Besu server. But somehow domain name stopped working. Now only ip works.

[emclab]

I scan the boot node log a few times and didn't find any error message about the (domain) provider request. Also the serverError in error message above is empty on app end. Does it imply where the problem is, app side or server side? Please help!

[emclab]

There is no error log with nginx server. nginx reverse proxy is used for the Besu boot node. Is it possible that the provider did not send out rpc request to the boot node for some reason?

[ricmoo]

The provider doesn't care about boot nodes. It just makes a normal web connection to a server.

I am 99% sure this is an issue with your network. If you have a reverse proxy set up, that seems to indicate to me you have a somewhat complex setup; it could be a vhost config issue, or DNS config problem (anything out of place with DNSSEC, round-robin, etc) or firewall problem (such as a mobile device trying to connect to non-secure backends, VPC, etc).

You might want to also reach out to the Besu folks, as it could be a configuration on their side too. I have never used it, so they may have their own level of vhost or proxy settings involved that could conflict with your setup.

I really don't think this is an ethers problem though; we use domain names for INFURA, Alchemy, etc. and I use the @ethersproject/web library I many unrelated-to-ethereum projects for both domain name and IP address requests. :)