On Mar 13, 2016, at 10:52 AM, Curtis Villamizar <cur...@orleans.occnc.com> wrote: > Are you saying they only looked at the primary NS record?
That’s my theory, yes. > Maybe I misread a prior post but I thought you meant primary MX record. The > former, if true, would be even more broken. This is Yahoo. Basically what happened is we moved our machines from a Comcast business connection to a 1000bT fiber connection with CenturyLink. We left one of the machines (the primary name server) on the Comcast connection with a fixed IP and put everything else on the gigabit. Someone made a change to the service plan with Comcast and in the process dropped the IP pool with Comcast, so NS1 went offline. The other two DNS servers on the gigabit connection were fine, and everything was working with the email except we started to get complaints that users were not getting mail from yahoo users. Since updating the NS records to reflect only the new IP pool, yahoo mail has started to come in (not that we ever got much mail from yahoo anyway). The only thing that has changed is that NS1 is responding to DNS lookups now, so I have to think that Yahoo was only looking at NS1 and never checking the secondary and tertiary DNS servers. This would not surprise me. I seem to recall years ago that Yahoo would never send mail to our backup MX, back when we had such a thing. -- Far away, across the fields, the tolling of the iron bell calls the faithful to their knees to hear the softly spoken magic spells.
