Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 23 Jan 2000 12:19:07 +0000
From:      Brian Somers <brian@Awfulhak.org>
To:        Roland Jesse <jesse@prinz-atm.CS.Uni-Magdeburg.De>
Cc:        freebsd-isdn@FreeBSD.ORG, brian@hak.lan.Awfulhak.org
Subject:   Re: leafnode+, DNS, and a dialup connection using i4b 
Message-ID:  <200001231219.MAA00978@hak.lan.Awfulhak.org>
In-Reply-To: Message from Roland Jesse <jesse@prinz-atm.CS.Uni-Magdeburg.De>  of "23 Jan 2000 12:06:00 %2B0100." <0vu2k51207.fsf@cs.uni-magdeburg.de> 

next in thread | previous in thread | raw e-mail | index | archive | help
> [Posted this to -questions before but to no avail. Does not look like
> there are active i4b users over there.]

I think a lot of people have run away from -questions due to the 
signal:noise ratio.

> Ok, thanks to i4b, my isdn connection is more or less up and running
> and I do my best to ignore the "File exists" error by ifconfig. But I
> still don't get the whole dilup setup done correctly. The world was
> just so much easier with a steady internet connection. :->

ppp(8) won't produce ``file exists'' message :*]

> How does one setup a DNS lookup? I am planning to use leafnode+ to
> fetch news for me. Leafnode+ is started via inetd with the following
> entry in /etc/inetd.conf:
> 
> ------- cut -------
> nntp    stream  tcp     nowait  news    /usr/local/sbin/leafnode leafnode
> ------- cut -------
> 
> Nothing special, I would say. Whenever I do a 'telnet localhost nntp',
> I get the following syslog message:
> 
> ------- cut -------
> Jan 20 20:55:07 arthur leafnode[671]: unable to parse server (server news.cs.uni-magdeburg.de has no =)
> ------- cut -------

I don't know how much like leafnode leafnode+ is, but with leafnode 
you need ``server = news.whatever''.  It sounds like you left out the 
``=''.

> Ok, so I put the ip address of this news.cs machine in /etc/hosts:
> 
> ------- cut -------
> 141.44.21.70            loriot loriot.cs.uni-magdeburg.de news news.cs.uni-magdeburg.de
> ------- cut -------
> 
> /etc/host.conf is of course
> 
> ------- cut -------
> hosts
> bind
> ------- cut -------
> 
> The above error message stays the same. That's why I thought having a
> little own named would be a nice idea. 
> 
> That's the try for /etc/resolv.conf:
> 
> ------- cut -------
> nameserver 127.0.0.1
> nameserver 141.44.1.2
> nameserver 141.44.1.1
> domain uni-magdeburg.de
> ------- cut -------

I wouldn't tend to mix 127.0.0.1 and other nameservers here.  Use 
forwarders in your named.conf instead.

[.....]
>         Roland

-- 
Brian <brian@Awfulhak.org>                        <brian@FreeBSD.org>
      <http://www.Awfulhak.org>;                   <brian@OpenBSD.org>
Don't _EVER_ lose your sense of humour !          <brian@FreeBSD.org.uk>




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isdn" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200001231219.MAA00978>