Missing DNS A record?

  • Thread starter Thread starter Adam Marx
  • Start date Start date
A

Adam Marx

I want to ask if when hosting multiple zones on my DNS server
(DNS1.domainname.com) if each zone that I add needs to have an A record that
points to my DNS servers public IP? (e.g. DNS1.hosteddomain.com)

I hope I'm asking this question correctly?

Thanks,

Adam M.
 
In
Adam Marx said:
I want to ask if when hosting multiple zones on my DNS server
(DNS1.domainname.com) if each zone that I add needs to have an A
record that points to my DNS servers public IP? (e.g.
DNS1.hosteddomain.com)

I hope I'm asking this question correctly?
Click to expand...

You only need an A host named DNS1 in the domainname.com zone.
All other zones will need a NS record for DNS1.domainname.com.
 
AM> I want to ask if when hosting multiple zones on my DNS
AM> server (DNS1.domainname.com) if each zone that I add
AM> needs to have an A record that points to my DNS servers
AM> public IP? (e.g. DNS1.hosteddomain.com)

BEST PRACTICE is for the intermediate domain names, used in delegation
information, to be subdomains of the domain that is being delegated. (e.g.
Use "a.ns.example.com." as an intermediate domain name for delegating
"example.com.". Use "a.ns.WebAJM.com." as an intermediate domain name for
delegating "WebAJM.com.".)

This prevents the delegation from being effectively glueless, and allows
delegation information to be continually refreshed with every response to a
query, reducing the load on the enclosing superdomain's content DNS servers.
(i.e. The delegation information for "example.com." is refreshed whenever an
"example.com." response is received, and there is the least need to fall back
to asking the "com." content DNS servers for it every so often.)

GOOD PRACTICE is for the intermediate domain names, used in delegation
information, to be subdomains of the superdomain that encloses the domain
being delegated. (e.g. Use "a.ns.example.com." as an intermediate domain name
for delegating "example.com.", "WebAJM.com.", and anything else under "com.".
Use "a.ns.example.net." as an intermediate domain name for delegating
"example.net." and anything else under "net.".)

This prevents the delegation from being effectively glueless, but doesn't
allow delegation information to be continually refreshed in most cases. (e.g.
The attempts by the "WebAJM.com." content DNS servers to refresh the
"WebAJM.com." delegation information in every response that they send will all
be ignored, since the "a.ns.example.com." information in those responses will
be discarded as poison. Every so often, resolving proxy DNS servers will need
to fall back to querying the "com." content DNS servers for fresh
"WebAJM.com." delegation information.)

BAD PRACTICE is for the intermediate domain names, used in delegation
information, to _not even_ be subdomains of the enclosing superdomain. (e.g.
Use "a.ns.example.com." as an intermediate domain name for delegating
"example.NET." or "example.ORG.".)

This renders the delegation effectively glueless (requiring extra, separate,
back-end queries to be made in order to retrieve it in the first place), and
prevents the delegation information from being continually refreshed in _all_
cases.
 
Back
Top