<div>
What Mal Osborne said. &nbsp;And I think that it's smart to have both forward and inverse DNS entries for a nameserver.
</div>


What Mal Osborne said.  And I think that it's smart to have both forward and inverse DNS entries for a nameserver.

<div>
Thanks for the answer, I am looking more on whether I should put the *Glue Record* for name server in my zone file?<br />
<br />
As we see that &nbsp;ns1.example.net is different domain than example.com and I am not authorized for inverse lookup zone of &nbsp;ns1.example.net
</div>


Thanks for the answer, I am looking more on whether I should put the *Glue Record* for name server in my zone file?

As we see that  ns1.example.net is different domain than example.com and I am not authorized for inverse lookup zone of  ns1.example.net

<div>
<div class="content wysiwyg-content">
Hello, my domain is example.com and my NS server is ns1.example.net<br />
<br />
Both are different domain. Should I still keep the IP of ns1.example.net in the zone file of example.com?<br />
<br />
Thanks!
</div>
</div>


Hello, my domain is example.com and my NS server is ns1.example.net

Both are different domain. Should I still keep the IP of ns1.example.net in the zone file of example.com?

Thanks!

Is it mandatory to keep PTR record of NS server in zone file?

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.