I just noticed that the named instance I have running in my dom0 is only
listening on some addresses.
Netstat -ln shows the following relevant listeners:
tcp 0 0 192.168.122.1:53 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN
tcp 0 0 ::1:53 :::* LISTEN
tcp 0 0 ::1:953 :::* LISTEN
udp 0 0 192.168.122.1:53 0.0.0.0:*
udp 0 0 127.0.0.1:53 0.0.0.0:*
udp 0 0 ::1:53 :::*
What's missing from this list is 192.168.1.19 -- the primary IP for the dom0!
(Bridged network configuration, obviously!)
Which explains why from various domUs and from outside boxes I can't in
fact use the DNS server on this machine.
My DNS config seems compatible with the "caching-only" nameserver config
in the Bind admin manual (with more zones pre-loaded). It's what's
installed by default in Centos 5.whatever I believe. It doesn't contain
an "allow-query" clause; the doc says the default for allow-query is
"any".
Is anybody else running named in caching-only mode in a Xen dom0? Or at
least a domU? I suspect this is some intersection of xen and named
behavior, but there must be lots of people here running caching-only
nameservers, so somebody must have a working example they could show me?
-- 
David Dyer-Bennet, dd-b@xxxxxxxx; http://dd-b.net/
Snapshots: http://dd-b.net/dd-b/SnapshotAlbum/data/
Photos: http://dd-b.net/photography/gallery/
Dragaera: http://dragaera.info
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users