Re: One A record fails on one server on Sunday evening

How do I export the cache dump? rndc dumpdb on the first execute took a few seconds, but after updatedb && locate named_dump.db (as it suggested it would store it there) returns nothing. The man page for rndc doesn't say anything about these commands either. Josh Luthman Office:

Re: One A record fails on one server on Sunday evening

if I ssh in I can ping (and hence resolve) the mail.alexandertelecominc.com. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 "When you have eliminated the impossible, that which remains, however improbable, must be the truth." --- Sir Ar

Re: One A record fails on one server on Sunday evening

Let me say it this way... Starting ~7PM EST Sunday evening the command dig mail.alexandertelecominc.com @74.218.88.168 #fails dig mail.alexandertelecominc.com @4.2.2.2 #works until I issue rndc reload && /etc/init.d/named restart #on the 74.218.88.168 server Josh Luthman Office: 937-

Re: One A record fails on one server on Sunday evening

The issue is that the A record no longer gets resolved. The command dig mail.alexandertelecominc.com @firstserver times out. Not sure what else I can provide that would help. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 "When you

One A record fails on one server on Sunday evening

start around 7PM EST Sunday. I have been able to solve this each Monday morning by issuing the commands (rndc reload && /etc/init.d/named restart). I have not had to do this on the second 3.9 server. I am looking for any suggestions or ideas to help fix this issue. Thanks in advance!