DNS A vs NS record

[CarlosMedina]

As far as I understood, the A record tells which IP-address belongs to a domain, so far it was still clear to me. But as I understood, the NS record tells which nameserver points belongs to a domain, and that nameserver should tell which IP-address belongs to a domain. But that was already specified in the A record in the same DNS file. So can someone explain to me what the NS records and nameservers exactly do, because probably I understood something wrong.

I'm not able to understand the role of NS Record.

 

[Active8]

let me google that for you :

DNS Record

This definition explains the meaning of DNS Record and why it matters.

www.techopedia.com

 

[MaXi32]

As far as I understood, the A record tells which IP-address belongs to a domain, so far it was still clear to me. But as I understood, the NS record tells which nameserver points belongs to a domain, and that nameserver should tell which IP-address belongs to a domain. But that was already specified in the A record in the same DNS file. So can someone explain to me what the NS records and nameservers exactly do, because probably I understood something wrong.

I'm not able to understand the role of NS Record.

Your question similar to this https://serverfault.com/questions/224920/dns-a-vs-ns-record

 

[MaXi32]

In directadmin it also uses both NS and A record for name server. It is weird that it doesn't show up the A record in UI for every domain and hostname but it only show when you query with API or cat /etc/bind/domain.com.db. In brief, the nameserver for A record is hidden in UI.

 

[Richard G]

In brief, the nameserver for A record is hidden in UI.

Seems logical to me. You don't want customers to go change nameserver ip's, that way they might be able to run their own nameservers, which is in fact for admins and resellers. And it could cause issues, extra support hours. So good thing that is hidden.