On 04/03/2012 02:30 PM, Barry Margolin wrote:
In article,
Keith Burgoyne wrote:
On 04/03/2012 11:14 AM, Barry Margolin wrote:
In article,
Chuck Swiger wrote:
On 4/2/2012 10:37 PM, Keith Burgoyne wrote:
[ ... ]
I've recently replaced the master server at 24.222.7.11, and a
On 04/03/2012 11:14 AM, Barry Margolin wrote:
In article,
Chuck Swiger wrote:
On 4/2/2012 10:37 PM, Keith Burgoyne wrote:
[ ... ]
I've recently replaced the master server at 24.222.7.11, and am now running
bind 9.7.3.
My question is: I keep seeing log entries like
Apr 2 23:
Hi all,
I have what, I hope, will be a rather quick question regarding 'lame
server resolving' errors.
I've recently replaced the master server at 24.222.7.11, and am now
running bind 9.7.3.
My question is: I keep seeing log entries like
Apr 2 23:24:17 clementine named[5870]: lame server
is a nice side
effect of this problem/solution.
Thanks again!
Keith
On 22/09/11 02:02 PM, Niall O'Reilly wrote:
On 22/09/11 17:34, Keith Burgoyne wrote:
Here's the named.conf file from my name server.
The meat of your configuration seems to be in the (hidden)
r non-primary name servers to get zone data
allow-transfer { 24.222.7.2; 24.222.7.40; };
// all views must contain the root hints zone:
include "/etc/named.domains.root";
// include the domains that we serve
include "/etc/named.domains.external";
};
Hi there,
I have a potentially BIND related problem and I'm positively stuck. I've
posted this question on Server Fault
(http://serverfault.com/questions/306997/cant-seem-to-resolve-domain-but-can-dig-it)
with little exposure. The jist of it is:
My name server (24.222.7.12) refuses to resolv
6 matches
Mail list logo
