These forums are locked and archived, but all topics have been migrated to the new forum. You can search for this topic on the new forum: Search for Dns not resolved on the new forum.
Web Hosting and Cloud Computing Control Panels
Howdy,
Could you provide an example of a domain that isn't resolving? That would help us to troubleshoot the issue. You can always edit your post later and remove it.
-Eric
.
We can offer some generic suggestions without the actual domain name... make sure there isn't a firewall blocking port 53 UDP, make sure the port is being forwarded if it's behind a NAT router, make sure BIND is listening on your public IP... but it's really be helpful to see the actual domain name that you're having problems with, then we can see the actual problem that's occurring.
-Eric
.
.
There's folks here in the Forums who will sometimes log into your server to provide assistance -- as far as support provided by myself and the other Virtualmin staff -- the remote login service is just for Virtualmin Pro customers, and even then we try to use it as a last resort :-)
I'm happy to toss out some suggestions though.
In the domain you shared above, the website is located at the IP "5.9.10.x".
However, the nameservers are at "46.4.68.x".
Is that correct? If so, which of those two is your Virtualmin server?
-Eric
.
Well, from what I'm seeing here, it looks like the nameserver records at your registrar are pointing at the old server.
You may need to go to your registrar, and where it lists the IP address for your two nameservers, you would need to update those to point to your new server.
-Eric
.
Your registrar would have both of your nameservers registered, including their IP addresses. That's the part that needs fixed at the moment.
What needs corrected isn't on your own Virtualmin server, it's a setting at the registrar for your domain.
-Eric
.