We have provided 45 websites through a developer for our parishes. Over the Thanksgiving holiday, the developer stood up a new server and moved all of the parish websites. This required changing A-records for all 45 websites. I am having problems with 1 of the 45.
I don’t manage the DNS for the one problem website, a local service provider does. I do manage DNS for the 44 other parish sites and they made it through the move successfully.
Here is the problem which did not exist before the move:
If you visit the site by typing only the domain name, stmarkmtcalvary.church, the sub-menu items work but all of the new browsers are calling the website unsafe.
If you visit the site by using the full URL, https://www.stmarkmtcalvary.church, the website loads but sub-menu items do not work.
The developer said to ask the managed service provider to ensure there are 2 A-Records both pointing to the IP. One should have a host of @ and the other should have a host of www.
The service provider says the have looked at the problem and they are not the cause. They said they only need to create 1 A-record but won’t tell me which one. He said something about only the webhost would need an A-record using @ not them so I assume that’s the one they won’t create.
The service provider sent me a screen shot from Free DNS checker which he says proves they are not the problem.
The web host/developer says they aren’t the problem either.
I don’t know enough to figure out where the problem lies. Is there a security reason why they wouldn’t want to create two A-records?