🚀 go-pugleaf

In article <1992Oct27.171625.17257@uts.cc.wayne.edu> rwilson@uts.cc.wayne.edu (Ron Wilson) writes:
>I have no trouble when adding new hosts to my departmental domain,
>chem.wayne.edu, with the new address records being propagted to the
>rest of the net.  However, when I try to add MX records, they don't
>get get beyond the name servers within the department.  Eg:
>
>	I add:
>
>		pharm.wayne.edu.   IN   MX   fourcroy.chem.wayne.edu.
>		dirac              IN   A    141.217.26.27

This has nothing to do with the record being an MX record.  It has
everything to do with the name being "pharm.wayne.edu".

Nameservers don't work by magic.  They are components of a hierarchical
distributed database structure.  Your problem is that parts of that
hierarchy are missing.

In simple terms you have no authority over the name "pharm.wayne.edu"
but you (at fourcroy) do have authority for the name "chem.wayne.edu".
You need to discuss this with the domain administrator for "wayne.edu"
which does have authority, and could delegate that authority.

In the mean time you should start studying the manuals to find out how
nameservers work, and how authoritative zones of control are established.