On 04/01/11 03:47, Tony MacDoodle wrote:
> Hello,
>
> I am trying to configure 2 different domains on one host that only has
> one physical interface plummed.
>
> I think I have an errorthat I list the hostname of the interface in both
> zone files as below and this might be why I can't resolve
In message <4d956ac7.2010...@data.pl>, Torinthiel writes:
> On 03/31/11 20:58, Barry Finkel wrote:
> > On 03/31/11 13:17, bind-users-requ...@lists.isc.org wrote:
> >> Hello,
> >>
> >> I get the following messages on the BIND server when I do a short name=
>
> >> nslookup from a client:
> >>
> >>
On 03/31/11 20:58, Barry Finkel wrote:
> On 03/31/11 13:17, bind-users-requ...@lists.isc.org wrote:
>> Hello,
>>
>> I get the following messages on the BIND server when I do a short name
>> nslookup from a client:
>>
>> Mar 31 14:08:04 jedi named[1299]: [ID 873579 daemon.info] network
>> unreachabl
Hello,
I am trying to configure 2 different domains on one host that only has one
physical interface plummed.
I think I have an errorthat I list the hostname of the interface in both
zone files as below and this might be why I can't resolve properly. Do you
see any mistakes in the files below?
Th
On 03/31/11 13:17, bind-users-requ...@lists.isc.org wrote:
Hello,
I get the following messages on the BIND server when I do a short name
nslookup from a client:
Mar 31 14:08:04 jedi named[1299]: [ID 873579 daemon.info] network
unreachable resolving 'C.ROOT-SERVERS.NET//IN': 2001:500:1::803f
Hello,
I get the following messages on the BIND server when I do a short name
nslookup from a client:
Mar 31 14:08:04 jedi named[1299]: [ID 873579 daemon.info] network
unreachable resolving 'C.ROOT-SERVERS.NET//IN': 2001:500:1::803f:235#53
Mar 31 14:08:05 jedi named[1299]: [ID 873579 daemon.i
> I was wondering if someone had a sample named.conf file I could reference
> that would allow for the configuration of 2 different domain names?
This is so easy that I'm suspecting you're _really_ thinking of something
else than what you're actually asking for. If it isn't, please excuse me,
I do
Thanks Evan,
I'll send in a bug report and upgrade to the latest release.
Paul
On 31 March 2011 17:18, Evan Hunt wrote:
> > Mar 31 16:34:42 ns2 named[3806]: dispatch.c:3018: INSIST(n == 1) failed
> > Mar 31 16:34:42 ns2 named[3806]: exiting (due to assertion failure)
> >
> > has anyone seen t
I was wondering if someone had a sample named.conf file I could reference
that would allow for the configuration of 2 different domain names?
Thanks
___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
> Mar 31 16:34:42 ns2 named[3806]: dispatch.c:3018: INSIST(n == 1) failed
> Mar 31 16:34:42 ns2 named[3806]: exiting (due to assertion failure)
>
> has anyone seen this before, and knows what causes it?
It's some sort of corruption in the task management system; I've never seen
it happen before.
On Mar 29, 2011, at 10:49 AM, Tony Finch wrote:
Kay wrote:
some domain has 12 IPs but traffic of the server is not equal.
The traffic of 11 IPs is same and just 1 IP is higher than others.
If you use round-robin DNS you are relying on the clients not to muck
around with the responses they ge
Hello,
One of our DNS stopped with this critical error:
Mar 31 16:34:42 ns2 named[3806]: dispatch.c:3018: INSIST(n == 1) failed
Mar 31 16:34:42 ns2 named[3806]: exiting (due to assertion failure)
has anyone seen this before, and knows what causes it?
Thanks
Paul
In message , Mike Diggins writes:
> On the master name server, I'm upgrading BIND from an older version,
> 9.2.1, to 9.7. However, when I attempt to load this zone Domain.CA, it
> gives me an error:
9.7 catches more common configuration errors. Remember nameservers
can't catch all configuratio
13 matches
Mail list logo
