Vesta Control Panel - Forum

if you make a new domain and set up the dns with that domain in vestacp
the dns is not ready and correct ,its just the same shit like in zpanelcp thats is why it use named.

why?

@ <<<<<<<<<this is show always in named and that is in correct.

there is not one provider that can handle this...

what is not correct ,simple there are no working correct a records for that nameserver it points to @ fools haha...

if you make for that domain a record for ns1 and ns2 (for that domain and not point it to @ but static ip) it shall work..
without this 2 ns a records to your static ip (it works but you have not setup the correct way) you can test in on dnsreport.

there is only a point to @ -> dns and no a records ,if you do not change manual ,take a look at your dnsreport you will see what i am talking about. no a records for that ns domain . only that @points to that domain ,just the same like in zpanelcp.

this is not the correct way

mach wrote:if you make a new domain and set up the dns with that domain in vestacp
the dns is not ready and correct ,its just the same shit like in zpanelcp thats is why it use named.

why?

@ <<<<<<<<<this is show always in named and that is in correct.

there is not one provider that can handle this...

what is not correct ,simple there are no working correct a records for that nameserver it points to @ fools haha...

if you make for that domain a record for ns1 and ns2 (for that domain and not point it to @ but static ip) it shall work..
without this 2 ns a records to your static ip (it works but you have not setup the correct way) you can test in on dnsreport.

there is only a point to @ -> dns and no a records ,if you do not change manual ,take a look at your dnsreport you will see what i am talking about. no a records for that ns domain . only that @points to that domain ,just the same like in zpanelcp.

this is not the correct way

There are many ways to do the same thing. It is your opinion that states it's not correct to use @.