[Server-devel] DNS strangeness on 0.5.2

[Jerry Vonau]

On Sun, 2009-05-17 at 12:42 -0700, Sameer Verma wrote:
> We have a server with XS -0.5.2 on it, yum updated as of yesterday.
> When I plug it into my home network, which talks to a WRT54G+dd-wrt
> over Ethernet, it works fine.
> When I use the XS on a segment of our campus network, it does not.
> 
> Details follow:
> 
> Home network: The XS gets a private IP from the WRT54G on eth0
> (192.168.89.148). The DNS that XS gets on eth0 points to itself
> (nameserver 172.18.0.1). 

No, that is hard-coded in the /etc/resolv.conf.in file part of the
xs-config package, which is used with git keep /etc/resolv.conf static.

> The XOs get IP and DNS from the XS
> (ip:172.18.10.13 dns 172.18.0.1). Browse on the XO can resolve IPs and
> FQDN.
> 
> Campus network: When I use the XS on a segment of our campus network,
> it gets a public IP from our campus dhcp server (130.212.xxx) but I
> don't see any SFSU DNS servers in cat /etc/resolv.conf on the XS. Its
> still points to itself (172.18.0.1) The XO gets IP (172.18.10.13), DNS
> (172.18.0.1), all as expected. Browse will not go out to say
> http://verma.sfsu.edu/ but will go out to http://130.212.24.20 which
> is verma.sfsu.edu's IP.
> 
On the XO, I guess you can't ping verma.sfsu.edu, but by ip address it
works? Can you ping anything else out on the internet by name?

Think you would need to create the domain mapping in named on the XS for
it to resolve verma.sfsu.edu. 

> Any ideas on what's broken? Where should I begin to look?
> 

You could edit /var/named-xs/school.external.zone.db to match your
external view on eth0.

> cheers,
> Sameer

Jerry