robeb
03-18-2003, 06:48 PM
Can someone can look this over and let me know if I know what the hell I'm talking about. I'm trying to figure this whole DNS thing out.
In a typical zone file you might have...
mydomain.com. IN SOA ns.mydomain.com.
This means that any request to resolve the domain mydomain.com or any subdomain of mydomain.com will be sent to ns.mydomain.com or whatever the name of the name server is.
Thus, the name server must also have a NS record and a A or CNAME record to resolve itself, correct? So...
mydomain.com. IN NS ns.mydomain.com.
ns.mydomain.com. IN A 1.2.3.4
This is so when you use a comand like "dig" you get back the Authority Section of the name server (ns.mydomain.com) and Additional Section, which lists the resolved IP of the name server (1.2.3.4).
So, it wouldn't be a good idea to have something like
blah.mydomain IN NS ns.mydomain.com.
unless blah.mydomain.com resolved to an actual IP. Hence, the reason we have
mydomain.com. IN NS ns.mydomain.com.
because mydomain.com does resolve to an actual IP address.
In a typical zone file you might have...
mydomain.com. IN SOA ns.mydomain.com.
This means that any request to resolve the domain mydomain.com or any subdomain of mydomain.com will be sent to ns.mydomain.com or whatever the name of the name server is.
Thus, the name server must also have a NS record and a A or CNAME record to resolve itself, correct? So...
mydomain.com. IN NS ns.mydomain.com.
ns.mydomain.com. IN A 1.2.3.4
This is so when you use a comand like "dig" you get back the Authority Section of the name server (ns.mydomain.com) and Additional Section, which lists the resolved IP of the name server (1.2.3.4).
So, it wouldn't be a good idea to have something like
blah.mydomain IN NS ns.mydomain.com.
unless blah.mydomain.com resolved to an actual IP. Hence, the reason we have
mydomain.com. IN NS ns.mydomain.com.
because mydomain.com does resolve to an actual IP address.