Hello guys,
I was yesterday assigning my nameservers for the first time with DirectAdmin, so i changed all nameserver settings i could find. After i added the nameservers to the Zones i wanted to request nameservers @ my domainhoster, but i didnt came that far.
I have ips:
*0 - > for websites , shared IP
*1 -> Free
*2 -> SSH
I have yesterday made my setting *1 for ns1 and *2 for ns2, today i want to login to SSH on the *2 ip, and i get 'no route to host', but apache still works on that ip. So the ip is still online and linked, but SSH doesnt work anymore. This is only after i tried to assign the nameservers to the server.
Is this a known problem, or, how do i get rid of it. SSH is the most important tool i need for every hoster i think
I was yesterday assigning my nameservers for the first time with DirectAdmin, so i changed all nameserver settings i could find. After i added the nameservers to the Zones i wanted to request nameservers @ my domainhoster, but i didnt came that far.
I have ips:
*0 - > for websites , shared IP
*1 -> Free
*2 -> SSH
I have yesterday made my setting *1 for ns1 and *2 for ns2, today i want to login to SSH on the *2 ip, and i get 'no route to host', but apache still works on that ip. So the ip is still online and linked, but SSH doesnt work anymore. This is only after i tried to assign the nameservers to the server.
Is this a known problem, or, how do i get rid of it. SSH is the most important tool i need for every hoster i think
Last edited: