Is it possible with ISPconfig?

Follow the multi-server guide to configure your VPS server as the ispconfig master, with all services running. Then install ispconfig on the host machine as a slave, connecting to the master you already have setup. In ISPConfig gui you would configure it with only DNS service enabled, and "is mirror of server" set to your vps server.

 

Ie. follow https://www.howtoforge.com/multiser...se-servers-on-debian-squeeze-with-ispconfig-3, making adjustments for your OS according to other Perfect Server guides (unless you happen to be installing squeeze, which you shouldn't). You're installing a master server with all services and a slave with DNS only.

 

That sounds like you needed your server to answer DNS for purposes of domain registration.

#1: The ispconfig install may proceed on the bare metal server without issue, or it may need a little manual tweaking of things, depending on what the hosting folks did. You'll need to remove the setup for the current domain (ie. sampleserver.samledomain.com above) on the baremetal server, then proceed as mentioned above (ie. install ispconfig in bare metal and vps servers). Just add sampleserver.samledomain.com back into DNS in the ispconfig gui.

#2: If you really don't want ispconfig on the bare metal server, you can just run a manually configured name server there. Install ispconfig in the vps with full services. In bind config on the vps server you'll need to allow transfers from the bare metal server's ip address (I don't think the ISPconfig gui has a setting for that). Then you could manually add DNS zones to the nameserver config on the bare metals server, as a slave of the vps - the nameserver itself will then connect and download the DNS records.

 

Adding a client is only necessary if you want to delegate the administration of DNS or other assets to a client. If you just manage your own domains, then you can add a client for yourself but you don't have to.

This can not be changed later (at least not easily). If you selected no here and this server shall be a slave of another server, then the best way is to uninstall ispconfig on the slave and reinstall it in expert mode tolet the installer join the master server.

 

The installation mode of the master does not matter, normal mode is ok there.

Regarding hostnames and dns, ensure that you set the hostnames of all servers in the /etc/hosts files on all server (as described in the multiserver installation tutorials) and that you added a mysql root user on the master that can access the master from hostname and ip of the slaves. The procedure to add this mysql root users is described in the multiserver tutorials as well.

The question if the slave shall join the master is always presented in expert mode, so you must get it.

 

This means that the root access on the master has not been added correctly or the connection is closed by a firewall. you can test the connextion with the mysql command from the slave:

mysql -u root -p -h master.server.tld

replace master.server.tld with the full hostname of the master server. This connection mus be working first before you can install ispconfig on the slave server.

 

If this is a slave server then you have to answer no as slaves are managed trough the GUI of the master, so they don't have their own GUI.

That's ok and described in all ispconfig install guides (perfect setup and multiserver).

 

Run tools >Resync in ispconfig interface to sync existing dns zones to the new slave server.

 

No, you shouldn't need to resync manually, any changes in the future should happen on the slave as well. Try adding a record or zone and it should show up on the slave in about a minute. The resync tool is there if for some reason the master and slave get out of sync (ie. you experience some problem that breaks that), but they normally run/update just fine.