You could manually maintain the zone files for that client's DNS, setting the MX server to the second one if this is an ongoing problem...
Perhaps an obvious solution -- have you mentioned the problem to the client so they can fix the server/ update the MX records to remove the faulty server? On 6/2/09, Nelson Serafica <[email protected]> wrote: > I'm using bind 9.5.0-P1. I host some domain. However, my mta says "no mx > record" to one of the recipient of my client's email. I just discovered that > their primary dns servers is down but when I query the secondary dns, it is > fine. > > Is there a possible way in bind that when one domain's dns server I'm trying > to query is not available, it will query the secondary dns automatically? > > Or should I do this in my MTA instead on my DNS? > > > > > -- Daniel --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Linux Users Group. To post a message, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit our group at http://groups.google.com/group/linuxusersgroup -~----------~----~----~----~------~----~------~--~---
