WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Named in domu listening on only some IP addresses

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Named in domu listening on only some IP addresses
From: Simon Hobson <linux@xxxxxxxxxxxxxxxx>
Date: Thu, 28 Oct 2010 18:10:30 +0100
Delivery-date: Thu, 28 Oct 2010 10:12:30 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <310f5e47feca287e986f34afa007d6da.squirrel@xxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <310f5e47feca287e986f34afa007d6da.squirrel@xxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
David Dyer-Bennet wrote:
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!

What happens if you stop and start the service (not reload or restart) after starting Xen and any guests ?

If it's still the same then I'd say you need to look at the config - does the OS have a file for declaring startup options ? I don't think this is anything to do with ACLs in your BIND config - if (for example) you specify an "allow-query" clause, that doesn't control which interfaces/IPs the service will listen on.

If stopping/starting the service brings it up on all interfaces/IPs, then perhaps something isn't ready at the time BIND starts.

--
Simon Hobson

Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed
author Gladys Hobson. Novels - poetry - short stories - ideal as
Christmas stocking fillers. Some available as e-books.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>