In message <961092e10911030921x3ff3ce60xdb3d1f0534159...@mail.gmail.com>, Josh
Luthman writes:
> 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
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: 937-552-2340
Dir
In article ,
Josh Luthman wrote:
> It has happened the last 4 or 5 Sunday nights.
>
> Currently there are no logs - what categories would you suggest I start
> logging?
>
> The server comes back with simply no response. It just times out. It
> resolves every other record I could think of to
It has happened the last 4 or 5 Sunday nights.
Currently there are no logs - what categories would you suggest I start
logging?
The server comes back with simply no response. It just times out. It
resolves every other record I could think of to ask it. Also, it may or may
not be relevant but i
Josh Luthman said:
> 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 se
On Mon, 2 Nov 2009, Josh Luthman wrote:
> dig mail.alexandertelecominc.com @74.218.88.168 #fails
What does "fails" mean?
> 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
Check named logs and look at
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-552-2340
D
Josh Luthman said:
> --000e0cd32f54da30b8047764ddcc
> Content-Type: text/plain; charset=ISO-8859-1
>
> 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.
Well, whe
> I am looking for any suggestions or ideas to help fix this issue. Thanks in
> advance!
To get good help, you may want to tell us what the issue is. Provide
real names and show your real tests. Also the version of BIND you are
using is out of date and is no longer supported.___
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 have eliminated
I have two servers that users query that as as cache servers.
The server having the problem is CentOS 4.4 running bind 9.2.4
The second server configured similarly is CentOS 3.9 also running bind
9.2.4.
There is one A record on Godaddy's DNS servers that fails look ups on the
4.4 server start ar
11 matches
Mail list logo
