@veronikya said in mongodb replica set:
The host’s local dns resolution is not configured. The problem of the host’s hosts being unable to be resolved in docker has been solved. Surprisingly
Solution:
Edit the /etc/resovel.conf file
Add 127.0.0.53
One immediate issue I can think of here is that editing resolv.conf directly is no longer supported and not recommended (because the changes do not survive a reboot) - unless you install the resolvconf package?
@veronikya said in mongodb replica set:
In a cluster, the database does not need to be exposed to the outside world
Actually, they should NEVER be exposed to the outside world. The cluster should communicate on it’s own internal network only.
@veronikya Not sure I follow completely in relation to the purpose of this topic - I know you mention
The subtle configuration differences make me uncomfortable
However, could you provide clarity around exactly what you want to do, and the steps you’ve taken so far? I also do not understand the need to expose ports to the internet when it should only be localhost?
@crazycells the only accurate way is to use the URL Inspection Tool
@crazycells yes, exactly. You want to allow crawlers such as Google bot etc.
@crazycells yes. I’m guessing the regulators here are the SEC.
@crazycells see the link located at the top right of that screenshot 
And as if FTX wasn’t enough…
https://news.sky.com/story/binance-faces-4bn-bill-to-settle-us-criminal-case-13013106
@crazycells Good news in the short term, but interested to see if this does impact the SEO of your forum. Do you have Bot Fight Mode enabled in CF?
@crazycells that’s as good a test as any 
