rhg@cpsolv.CPS.COM (Richard H. Gumpertz) (07/25/90)
It appears that we have finally tracked down a problem with the domain CPS.COM sometimes showing up with an MX and sometimes not. It was a misconfigured secondary NS for CPS.COM: due to miscommunication, named at that site wasn't configured with a "secondary" line telling it that it was an authoritative NS for CPS.COM. Therefore, it never fetched the zone information from the primary server and instead responded to inquiries by just returning whatever happened to be in its cache (usually just the NS records obtained from a root DNS server and not the MX records which it was supposed to have obtained by zone transfer from the primary NS). This brings up an interesting point: maybe "named" and other DNS servers should complain to a local administrator if they see an NS record go by pointing at the local site when the local site hasn't loaded any authoritative records for the zone. Thanks to all who helped me track down the problem; it appears to be fixed as of today. -- ========================================================================== | Richard H. Gumpertz rhg@CPS.COM (913) 642-1777 or (816) 891-3561 | | Computer Problem Solving, 8905 Mohawk Lane, Leawood, Kansas 66206-1749 | ==========================================================================