[brandz-discuss] lx brandz on intel: nslookup/dig failures

[Eric Enright]

On 8/4/06, Wolfgang Engelien <woe2001 at med.cornell.edu> wrote:
> At 11:25 PM 8/3/2006, Eric Enright wrote:
> >Ping works for me, but nslookup and dig both give me this:
> >
> >$ nslookup google.ca
> >;; reply from unexpected source: 192.168.0.1#53, expected 192.168.0.1#53
> >;; reply from unexpected source: 192.168.0.1#53, expected 192.168.0.1#53
> After these two lines I get
>
> ;; connection timed out; no servers could be reached

I think I got something similar with dig; it had a little more output
than nslookup.

> However I can ssh into the nameserver with no problem. NFS mounts are
> no problem either.
>
> >>  2) Does anybody have a implementation of Solaris on Intel with brandz and
> >>lx brand, where name service lookups are working?
> >
> >Yes, mine works fine:
> What kind of intel processor do you run?

Pentium M.

> >[eric at linux eric]$ uname -a
> >Linux linux 2.4.21 BrandZ fake linux i686 i686 i386 GNU/Linux
> Is this based on CentOS? Which version?
> Or is it RHEL AS 3? Which Update?

It is CentOS 3.5, installed from the tarball available on the brandz
site.  I don't know if it's been updated or anything, I downloaded it
when brandz was first released.

> >My zone is configured to be on the same subnet as the global zone,
> >however.  If you create your own private one for zones, then the
> >routing becomes a bit more complicated and you need to play with
> >ipfilter.  Which setup do you have?
>
> My zone is actually on a different subnet. I will put it on the same
> subnet to check if it makes a difference.

Hopefully that will help.  But I am unsure if this is "correct" or not
as I now get a LOT of syslog warnings with this message:

ip: [ID 903730 kern.warning] WARNING: IP: Hardware address
'00:0e:35:13:31:45' trying to be our address 192.168.000.050!

and for 192.168.0.101.

Perhaps someone else can comment on this?


-- 
Eric Enright