Re: named not working

• Next message: Brian: "squid server w/3com 905B explodes under load"
• Previous message: Thomas Beer: "named not working"
• In reply to: Thomas Beer: "named not working"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Sun, Jan 21, 2001 at 06:52:02PM +0100, Thomas Beer wrote:
> Hi!
>
> I've installed bind and he's starting properly.
> But if I try to start a query using 192.168.1.2
> as I configuered as ns in /etc/named.conf
> nothing happens. If I start using 192.168.1.1
> I'm getting querys, but independent of a
> running nameserver.

Your bind is running on 192.168.1.1 (as it mentiones down there):
> /var/log/messages
>
> Jan 21 18:30:29 daemon named[1312]: listening on [127.0.0.1].53 (lo)
> Jan 21 18:30:29 daemon named[1312]: listening on [149.225.82.181].53 (ippp0)
> Jan 21 18:30:29 daemon named[1312]: listening on [192.168.3.99].53 (ippp1)
> Jan 21 18:30:29 daemon named[1312]: listening on [192.168.1.1].53 (eth0)

So you either have to use one of these IPs as your nameserver in
/etc/resolv.conf *or* let your bind run on the box which owns
192.168.1.2 *or* give that host (which has 192.168.1.1 as its current
IP address) the 192.168.1.2 IP address additionally:

        ifconfig eth0:1 192.168.1.2

MfG, JBG

-- 
Fehler eingestehen, Größe zeigen: Nehmt die Rechtschreibreform zurück!!!
/* Jan-Benedict Glaw <jbglaw@lug-owl.de> -- +49-177-5601720 */
keyID=0x8399E1BB fingerprint=250D 3BCF 7127 0D8C A444 A961 1DBD 5E75 8399 E1BB
     "insmod vi.o and there we go..." (Alexander Viro on linux-kernel)

• application/pgp-signature attachment: stored

• Next message: Brian: "squid server w/3com 905B explodes under load"
• Previous message: Thomas Beer: "named not working"
• In reply to: Thomas Beer: "named not working"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Tue Jan 23 2001 - 21:00:32 EST