in some ways it may be easier with a teamviewer connection ?
Just sent email
i like team viewer. this way I can see what’s wrong
ok, the problem is you have setup the virtual server as ‘nx1.intrelligent.net’
instead of just ‘intrelligent.net’
then you need to set DNS for nx1, mail, www etc.
i’d suggest renaming your server, we will use Teamviewer and i will sort for you, but might be an hour or two later
DNS is set for all those already at the domain.
well, yes as such. however, you cannot (I believe) use your own domain as a Name Server.
you will need to setup say Godaddy to get your A records etc to point to the server
Godaddy has the NS pointed to Digital ocean and the domain in DO has all these DNs on it
This how it’s always been done
do you use Godday NS if so what are they ?
I’ll need to catch up a bit later
You can. [nameserver].domain.tld works even if hostname is [something].samedomain.tld, and even if the nameserver(s) use(s) the same IP('s) as the physical server or VPS.
I just use ns1. and ns2. on the primary and secondary server IP’s. Works fine.
Richard
I’m sorry, but I don’t follow you…
I don’t follow either
You can’t have the NS off the domain
How can it be resolved, chicken and egg
I’d like to thank everyone that commented. I finally have this whole thing resolved. SSL is properly working, as well as, e-mail coming and going and the most important part is, that I also have VTiger properly working. Again, Thanks…
You install the OS, declare the hostname, do the OS updates, and install Virtualmin.
server1.example.tld
You set up as many nameservers as you care to (or have IP addresses for, whichever is less) and assign IP addresses to them in Virtualmin.
ns1.example.tld > xxx.xxx.xxx.xxx
ns2.example.tld > xxx.xxx.xxx.xxy
You go to your registrar and register the nameservers and point them to the IP addresses.
Unless we’re talking about two different things, I thought this was pretty typical.
Richard
I was referring to setting up say fife.co.uk and use ns1.fife.co.uk as a nameserver
I don’t think I can go to nominet to register fife.co.uk and say that the nameserver is ns1.fife.co.uk
I don’t know if the .uk changes anything, but I’ve been doing it with .com, .net, .us, etc. for about 20 years, with no problems whatsoever.
I’ve also migrated nameservers that way when migrating entire servers so clients wouldn’t have to re-point their domains, using roughly these steps:
-
Set up nameservers on the gaining server using the same names as on the losing server, but don’t register them just yet.
-
Set the TTL’s on the losing server absurdly low (like 300) about two weeks before the move, if it’s a planned (rather than emergency) migration.
-
As each domain is migrated, preferably in the middle of the night, edit DNS for that domain on the losing server to point to the gaining server using A entries.
-
After all the domains are migrated, let the losing server play traffic cop for a few days. At that point, it’s just doing DNS duty.
-
When the losing server is getting no more traffic other than DNS, register the nameservers on the gaining server.
-
If all is well, decommission the losing server.
This prevents problems with client-side caching, and avoids the need for clients to re-point their domains because the nameserver names stay the same. It also minimizes site downtime or lost mail because the TTL’s are so low.
I wouldn’t attempt the above for an extraordinarily complex site; but for your run-of-the-mill sites, it works just fine. I’ve done it many times.
Now as for availability, running both nameservers on the same machine hosting the sites / mail isn’t so great because both servers are on the same physical machine, so there’s no redundancy. But on the other hand, if the server goes down, then everything it hosts goes down; so even with redundant nameservers, it wouldn’t matter much anyway. The nameservers would be pointing to a down server.
Richard
1 Like
Interesting…
Richard
Thanks for the insight 
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.