Creating ns1.domain.tld & ns1.domain.tld, not working

Community Support DNS
21

My registrar said my domain need these dns

Name Server: ns1.mysrsx.com
Name Server: ns1.mysrsx.net
Name Server: ns2.mysrsx.com
Name Server: ns2.mysrsx.net

In order to use the dns management system on their system

I told them about this matter and they still insisted that it should be the wrong setup at the server

22

If you use THEIR dns servers you are not using YOUR dns servers.

Iā€™m sorry but this issue is not related to Hestia.

23

In the nameserver I need to input their nameservers, total 4 NS
Then I can use the managed/custom DNS

But, yeah, it should be their issue
Iā€™ll try other registrar
Thanks

24

Right, to use their dns servers. To use your own dns servers the registar (or you from their control panel) should do two things:

1.- Add 2 glue records for ns1.cybereverweb.my.id and ns2.cybereverweb.my.id pointing to your serverā€™s ip 213.35.110.37

2.- Add those dns servers as your ns servers so doing a whois you should see them listed there:

$ whois cybereverweb.my.id | grep 'Name Server'
Name Server: ns1.cybereverweb.my.id
Name Server: ns2.cybereverweb.my.id
25

They didnā€™t let me to do the 2nd step

I MUST use their 4 dns

Name Server: ns1.mysrsx.com
Name Server: ns1.mysrsx.net
Name Server: ns2.mysrsx.com
Name Server: ns2.mysrsx.net

Donā€™t know the reason, Iā€™ll just use other registrar

image
image1276Ɨ595 36.9 KB

1 Like
26

I donā€™t know whether you changed your registrar or they did the job but it is working now:

$ whois cybereverweb.my.id | grep 'Name Server'
Name Server: ns1.cybereverweb.my.id
Name Server: ns2.cybereverweb.my.id


$ dig cybereverweb.my.id +trace -4 +nodnssec

; <<>> DiG 9.18.19-1~deb12u1-Debian <<>> cybereverweb.my.id +trace -4 +nodnssec
;; global options: +cmd
.                       86181   IN      NS      m.root-servers.net.
.                       86181   IN      NS      l.root-servers.net.
.                       86181   IN      NS      i.root-servers.net.
.                       86181   IN      NS      j.root-servers.net.
.                       86181   IN      NS      a.root-servers.net.
.                       86181   IN      NS      c.root-servers.net.
.                       86181   IN      NS      h.root-servers.net.
.                       86181   IN      NS      e.root-servers.net.
.                       86181   IN      NS      g.root-servers.net.
.                       86181   IN      NS      d.root-servers.net.
.                       86181   IN      NS      f.root-servers.net.
.                       86181   IN      NS      k.root-servers.net.
.                       86181   IN      NS      b.root-servers.net.
;; Received 239 bytes from 127.0.0.1#53(127.0.0.1) in 0 ms

id.                     172800  IN      NS      d.dns.id.
id.                     172800  IN      NS      b.dns.id.
id.                     172800  IN      NS      c.dns.id.
id.                     172800  IN      NS      ns4.apnic.net.
id.                     172800  IN      NS      e.dns.id.
;; Received 362 bytes from 198.41.0.4#53(a.root-servers.net) in 3 ms

cybereverweb.my.id.     3600    IN      NS      ns2.cybereverweb.my.id.
cybereverweb.my.id.     3600    IN      NS      ns1.cybereverweb.my.id.
;; Received 143 bytes from 45.126.57.57#53(d.dns.id) in 203 ms

cybereverweb.my.id.     14400   IN      A       213.35.110.37
cybereverweb.my.id.     14400   IN      NS      ns1.cybereverweb.my.id.
cybereverweb.my.id.     14400   IN      NS      ns2.cybereverweb.my.id.
;; Received 159 bytes from 213.35.110.37#53(ns1.cybereverweb.my.id) in 155 ms
27

I change the registrar, it works well now
Thanks for the help @sahsanu

2 Likes