That's the Google DNS Resolver and not the authoritative DNS server of your domain. I'm talking about the DNS server of your domain, not about the DNS resolver that is sued by your desktop or server.
In that case, I am stuck I don't understand what could be the problem... I can access HTTP or https://mydomain.com I have an entry at my domain registrar for myserver.mydomain.com and mydomain.com I have also tried just adding a subdomain myserver but still nothing.
I cannot work out the issue here I thought it might be an SSL problem. I have removed the site and the cert's recreated the site and the cert's but still the same issue. Back to a new rebuild, I guess
A rebuild should not be necessary, especially not when DNS is the problem. So please share the domain and hostname so we can check this.
Thanks for PMing me the hostname. When running Code: dig a server1.example.com (with your hostname ofcourse), it turns out the DNS record does indeed not exist on the nameservers for your domain. Your authoritative nameservers are hosted by meganameservers.eu. I believe you had several DNS problems in a thread earlier. It might be worth reading more about DNS: https://www.cloudflare.com/learning/dns/what-is-dns/ To resolve your issue, create a A (and eventual AAAA) record for your hostname on the authoritative nameservers, which should point to the public IP of your server.
I can confirm I have an A record for my domain it has never changed Yes we should fix one problem first... sorry I'm just getting frustrated
In theory yes, but most likely you just missed adding the record for this subdomain. Could you share the current records?
It is better to send it here so others can eventually help you out aswell, but if you'd rather PM it, feel free.
You probably need to add a trailing dot to the record - some providers do this automatically, most don't. So instead of "server1.example.com" -> "server1.example.com." Also, from what you send in PM, I see your MX record is pointed to your root domain (example.com). It should be pointed to a subdomain, for example server1.example.com.
@mrbronz I did ask you to dig your ISPConfig FQDN to check whether it is already propagated to the right ip but you answered in positive. I just run dig command with the above info and clearly it has not. You should really just ask if you do not know how to do it instead of giving misleading answers and taking other people's time unnecessarily.
yes I have been plying around trying all sorts of combinations, all I have done is alter the IP address
At that point I was the correct information, I did not deliberately give false information, I do know how to do it and I did. Could have, should have would have, is not really a helpful point to a solution. But thanks for pointing out I made a mistake...
