TruCluster and Bind9

Danny Mayer mayer at gis.net
Sun Jan 27 23:30:37 UTC 2002


At 03:13 PM 1/27/02, Alaa Alamood wrote:
>Thanks for answer
>
>Yes actully I try to reload the nameserver several times.
>The cluster machine using just alias and there is no physical interface,
>and what the cluster doing is when you start the service in one machine
>then you could use both the cluster alias ip address and the ip address
>for the computer where the service is, what's happen is I can see the
>bind just on the computer that running the bind server not on all
>cluster machine.
>
>
>  is that bug on bind 9.2, or there is an option to contoll that for
>compaq trucluster?

You need to talk to the Compaq people.  They had modified the BIND
code to handle cluster alias ip addresses. I know they were working
on BIND 9, so ask them about it.

         Danny


>regards
>Alaa
>
>
>Kevin Darcy wrote:
>
> >Alaa Alamood wrote:
> >
> >>Hi
> >>
> >>I spend all my last night tring to find out is there is any hint or
> >>solution for the following problem I got yesterday after I update my
> >>server from bind8 to bind 9
> >>
> >>I have truCluster version 5.1a which runnig bind 8 as a default, the
> >>cluster contain 2 nodes, each of which with two ip address and both have
> >>one ip address as alias, which normally I used,
> >>
> >>cluseter1->1.2.3.4 |
> >>               ->2.3.4.5 |
> >>                              |  myServer 10.0.0.1 (which alias ip
> >>address for my cluster system)
> >>                              |------->
> >>cluster2->5.6.7.8  |
> >>              ->6.7.8.9 |
> >>
> >>in bind 8 its just working fine, ip can use 10.0.0.1 as my master server
> >>and I can nslookup from any where in my internal network using this ip
> >>address
> >>
> >>but in bind 9 if I installet in cluster1 then I can just using cluseter1
> >>as bind server when I try to use the alias of the server it say can't
> >>connect to server
> >>
> >>nslookup myclient cluster1->ok
> >>nslookup myclient myServer -> no answer
> >>
> >>any one can help with this problem
> >>
> >
> >Did you start the nameserver before bringing up the cluster address? If so,
> >then named wouldn't know about the cluster address immediately and
> >therefore wouldn't listen on it. It only checks for new interfaces every so
> >often (controlled by the "interface-interval" option). One way to force it
> >to check for new interfaces is to reload the nameserver. Did you try doing
> >that after the cluster address was brought up?
> >
> >
> >- Kevin
> >
> >
> >
> >
> >
>



More information about the bind-users mailing list