Hello all! I’m having a bizarre issue setting up a new install. We’re moving from hosted to self-hosting our installation, and are using the domain www.pidforum.org. I have spun up an Ubuntu server, and am using the standard install. Domain is currently pointing at the IP of the server with @, *, and www. all set as A names. installation appears to go without a hitch…everything looks like it’s working. Initial domain check says it’s ok, installation proceeds and completes. But it doesn’t work. Server isn’t listening on 443 or 80, and when i discourse doctor it says: Discourse version at www.pidforum.org: NOT FOUND Discourse version at localhost: NOT FOUND Now here’s the weird thing…if i redo discourse-setup, and change ONLY the domain name to another domain i control (discourse.xxxxxxx.yyy) it works fine. Everything else is the same…same server, same everything, ONLY changing the domain name. What could cause this? Help, I’m going insane trying to sort this out.

I am not, but a friend just suggested i move my DNS there so that I have DNSSEC controls.

in the continuing saga: Network Solutions confirmed to me that they did not see any DNSSEC records associated with the domain on their side…so…ghost in the machine from the previous registrar? In any case, since they can’t delete what isn’t there, we’re trying to add new records and hope that those overwrite the phantom ones and kick everything back to where it should be. This is by far the strangest DNS issue I’ve ever seen.

[תמונה] griffey: This is by far the strangest DNS issue I’ve ever seen. I have to agree :slight_smile:

[תמונה] griffey: Does anyone have any idea what 199.19.56.1 That is a .org nameserver [תמונה] griffey: I am not, but a friend just suggested i move my DNS there so that I have DNSSEC controls. DNSSEC controls must be done at your registrar since, like glue records, the DS records for your domain must be present at the TLD nameservers. Your DNS provider will have no control over that. I still see the records present there: pidforum.org. 86400 IN DS 30311 8 2 A75DEB1CF7CE3EE94899941C7E92B72A7E83A7B5DCD3717D6731804B 4D851E46 pidforum.org. 86400 IN RRSIG DS 8 2 86400 20211008152857 20210917142857 39681 org. goYqP/QgI0+8jN/pL3yVhZfeWAGXoibV/DHDduL+DWj47b9U18nRKctf OJB+TNznVcQeEtG67UM5O+nr5FmrfzowCHvgRsUaanVlo1nCXjlOg9eV KqZmkVcN2no1oklqbQBtN7GDqtX+G1BYmQCaIWbZ38PGBAnc2aQ0Ftr8 cAg= ;; Received 252 bytes from 199.19.53.1#53(c0.org.afilias-nst.info) in 93 ms and the analyser still shows an error: [image] [תמונה] griffey: Network Solutions confirmed to me that they did not see any DNSSEC records associated with the domain on their side…so…ghost in the machine from the previous registrar? You need to bother them until they get someone on their side to fix this - this is the registrar’s responsibility to get correct. You might also get somewhere by talking to the previous registrar and asking them to stop submitting glue and DS records for your zone. EDIT: At the moment, your published .org zone records are: pidforum.org. 86400 in ns lee.ns.cloudflare.com. pidforum.org. 86400 in ns jillian.ns.cloudflare.com. pidforum.org. 86400 in ds 30311 8 2 (a75deb1cf7ce3ee94899941c7e92b72a7e83a7b5dcd3717d6731804b4d851e46 ) pidforum.org. 86400 in rrsig ds 8 2 86400 20211005151127 20210914141127 39681 org. bDTwz7kYTRJXb7LuN1qj1mCBtiq0DMUM9dNzppGgR/+pTX6b0cWuMhFngI1zMk870aJU6BozFxwuv/AhUHl3y3/PHrjDOsSVA1SubPZM/tC/ylWSUexcVxVhQkQRLkpKPUlL61sZTX8VNca3MBWXx/kFSt7uThR0IYeW+2fQXqQ=

I did get confirmation this morning that the previous registrar (argeweb in the netherlands) did confirm that they finally removed the DS records for this domain from their system. So at this point i have Network Solutions (registrar) that has confirmed they have correct (new) DS records in place from Cloudflare (nameserver) and that the previous registrar (Argeweb) has removed their records. Hopefully, I just have to wait for all of that to shake out across the globe. NetSol and Cloudflare confirmation happened late on wed, and Argeweb confirmation happened this morning. Maybe over the weekend this will all reconcile. crossed fingers

[תמונה] griffey: NetSol and Cloudflare confirmation happened late on wed, and Argeweb confirmation happened this morning. It should take no longer than a day.

There’s a lot of Should going on in all this…Argeweb should have disabled DNSSEC before transferring a domain in the first place. Network Solutions should have been able to see and disable it on their end when transferred in. Should is the bane of this whole project. :slight_smile:

[תמונה] griffey: There’s a lot of Should going on in all this… I don’t know exactly the interface behind the registrar and the root zone operators; whether they send deltas or daily complete updates. But they should know the process and have done the right thing. Likewise, Network Solutions should have imported the previous DS records to their intrerface as you transferred the zone in. Presumably they also transferred in the NS records, but maybe you had to supply those? DNS is tricky to get right; DNSSEC even more so.

Should have / could have / would have Atleast you know what the issue is and how to get it fix. Suppliers will almost blame the other person.

בעיית התקנה מוזרה בנוגע לשם דומיין ספציפי

תמיכה התקנה

IAmGav (Gavin Perch) 27 בספטמבר,‏ 2021,‏ 12:46pm 39

move your domain to google cloud.

you can then control dnssec settings yourself

נושא		תגובות	צפיות
Discourse Installed but nothing on domain Self-hosting	8	803	14 בנובמבר,‏ 2022
Unable to change domain name Self-hosting	10	1943	4 באוקטובר,‏ 2020
Misconfigured DNS preventing discourse-setup completion Self-hosting	13	2083	21 במרץ,‏ 2020
I cant Pass the domain checking Self-hosting	1	675	10 בינואר,‏ 2023
Discourse not coming up on DigitalOcean Self-hosting	13	1315	25 בספטמבר,‏ 2018

בעיית התקנה מוזרה בנוגע לשם דומיין ספציפי

נושאים קשורים