Branded Nameservers.

[victorbendas]

Hello guys, how are you?

I need a little help asap. I'm using vestacp on ubuntu 14.04 at digitalocean. I'm trying trying to set up my branded nameservers with success following the VestaCP Documentation. Can you see my step by step below and tell me what i'm doing wrong?

My domain is cmt.rocks, and my vps ip is 162.243.228.89.

1) First of all I'm going to my domain registrar, the namecheap and registering the glue records:



I'm pointing both the NS1 and NS2 to the digitalocean droplet IP which is 162.243.228.89.

2) Now i've changed the domains namesevers to ns1.cmt.rocks and ns2.cmt.rocks.



3) Now on VestaCP, i added my domain cmt.rocks.



4) Than, on DNS I have changed the template to child-ns and also edited the package, changing the name servers to ns1.cmt.rocks and ns2.cmt.rocks.





5) now in the DNS I pointed a NS1 A to VPS IP, and the same to NS2. See my dns list bellow:

LISTING CMT.ROCKS
@TXT "v=spf1 a mx ip4:162.243.228.89 ?all"
@MX10 mail.cmt.rocks.
ftpA 162.243.228.89
popA 162.243.228.89
wwwA 162.243.228.89
mailA 162.243.228.89
ns2A 162.243.228.89
ns1A 162.243.228.89
@A 162.243.228.89
@NS ns2.cmt.rocks.
@NS ns1.cmt.rocks.


---

And finally, after a couple hours and still getting that message when trying access the website:




Does anyone know what I doing wrong or what I'm missing?

[BBuchanan1013]

Hello guys, how are you?

I need a little help asap. I'm using vestacp on ubuntu 14.04 at digitalocean. I'm trying trying to set up my branded nameservers with success following the VestaCP Documentation. Can you see my step by step below and tell me what i'm doing wrong?

My domain is cmt.rocks, and my vps ip is 162.243.228.89.

1) First of all I'm going to my domain registrar, the namecheap and registering the glue records:



I'm pointing both the NS1 and NS2 to the digitalocean droplet IP which is 162.243.228.89.

2) Now i've changed the domains namesevers to ns1.cmt.rocks and ns2.cmt.rocks.



3) Now on VestaCP, i added my domain cmt.rocks.



4) Than, on DNS I have changed the template to child-ns and also edited the package, changing the name servers to ns1.cmt.rocks and ns2.cmt.rocks.





5) now in the DNS I pointed a NS1 A to VPS IP, and the same to NS2. See my dns list bellow:

LISTING CMT.ROCKS
@TXT "v=spf1 a mx ip4:162.243.228.89 ?all"
@MX10 mail.cmt.rocks.
ftpA 162.243.228.89
popA 162.243.228.89
wwwA 162.243.228.89
mailA 162.243.228.89
ns2A 162.243.228.89
ns1A 162.243.228.89
@A 162.243.228.89
@NS ns2.cmt.rocks.
@NS ns1.cmt.rocks.


---

And finally, after a couple hours and still getting that message when trying access the website:




Does anyone know what I doing wrong or what I'm missing?

From what I can tell, your DNS hasn't propogated yet.
http://www.intodns.com/cmt.rocks

[victorbendas]

Thatś strange because it already past more than 48hrs. There is something I miss

[BBuchanan1013]

Thatś strange because it already past more than 48hrs. There is something I miss

Call me crazy, but do check two things:

First, check the button at the top that says IP. You may have an internal and external IP address. You maybe pointing everything right, but it might actually be adding to the internal and not the external. I know it sounds crazy but check it anywho.

Check under Admin, like click admin at the top, then scroll down and check what the default name servers are there.

edit:
Side note, check to make sure Bind or named, which ever is actually running. That could be the whole issue.

[amargo]

i have same trouble

[misterpat]

I did just what you did in the first picture. I use Godaddy though. I added 2 hosts. NS1 and NS2 on my main domain both pointing to my shared IP. Just like you did, so I would say you're good there.

In VestaCP, On the main domain, I added 2 NS records, one with ns1 and the other with ns2 both pointing to my shared IP. Works great and http://www.intodns.com shows all good. I will screen shot the NS records I have if needed.

[starter]

To setup my own private nameservers I followed a very similar path to you victorbendas. Although, I did not set the DNS template of my domain to child-ns (from what I understand this template is intended to vanity name servers, not private name servers, but maybe someone could confirm this point?).

My NS were not working, and as I was desperately looking to fix the configuration, I thought: let's try to reboot the server. And it worked!
Seems that the VestaCP NS does not apply all its configuration without a restart.

Probably a bind9 restart would have been enough:

Code: Select all

service bind9 restart

Note that to check your new configuration you don't necessarily have to wait as long as 48h, you can simply try to see what happens in the locations where it propagates faster: https://www.whatsmydns.net

I hope it will help others in with the same problem.