The master is still down. I think what happen is when someone tried to email to that domain, it is still not propagated in our dns servers that's why my mta says "No mx record". But now, using dig without "@<DNS>" shows the mx record on the domain.
I use dig @primary and it was still no result. I hope they know the consequence of not fixing the problem. Or yet, change the secondary dns to be the primary dns while their primary dns is still down. Bryan Smith wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > There are a few things that could cause this: > > 1. TTL in the zone > 2. If this is replication to slave, then the changes from the master > aren't transferring to the slave. > 3. Are you incrementing the serial on the zone? If not then the changes > will NEVER transfer to the slave. > > Pull out dig and if you can dig the domain from the system that is > having the error. You may find that the zone is not as it should be on > the slave, even though it resolves. > > When the master is down the slave should be queried automatically as > long as the changes are propagated to the root servers and your local > DNS.Once the master is back up try digging the master and slave to see > if things are appropriate: > > dig MX @primary.dns.com hostname > > dig MX @secondary.dns.com hostname > > Do these match? Does your syslog show the changes being transferred to > the slave? > > Bryan > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
