how bad is it for MX and NS records for a zone to list hosts that are
in child zones of a domain (if it is bad at all..)?
eg,
$ORIGIN foo.com.
.
.
.
@ NS bar.xx
joe.urg
wibble.wobble
xx NS ...
...
<etc.. more delegations>
@ MX 10 eek.urg
20 nak.bother
20 ack.syn
obviously the foo.com. zone will have to have the glue records for all
the NS records, and the com. registry will also have the addresses of
these hosts.
so it'll /work/ fine, and it's quite common for NS and MX records to
point to hosts outside of the zone itself. so i can't see any reason
why NS and MX records could not be to hosts in child zones of the zone
in question.
no??
--paulj
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
