named forcing a dial-up

named forcing a dial-up

Post by Marius Flag » Fri, 17 May 2002 00:52:01



Hi there

I guess this question has been answered thousand times before, but here
goes:

I'm running linux on my LAN, and it's acting as a nameserver for the
network. Now and then (maybe every 10 minutes?) it forces a dial-up on the
isdn-router we've got running. The isdn-router is at 192.168.1.1 and the
dns server is at 192.168.1.2. The default gw for the dns server is of
course .1. How do I prevent the dns server from sending these packets now
and then? I just want it to act as a dns for the LAN and as a caching
nameserver.

I'm running the bind-version that ships with slack8.0 (bind8, maybe?)

Marius

 
 
 

named forcing a dial-up

Post by Andreas Thala » Fri, 17 May 2002 03:31:03


On Wed, 15 May 2002 17:52:01 +0200, Marius Flage


>Hi there

>I guess this question has been answered thousand times before, but here
>goes:

>I'm running linux on my LAN, and it's acting as a nameserver for the
>network. Now and then (maybe every 10 minutes?) it forces a dial-up on the
>isdn-router we've got running. The isdn-router is at 192.168.1.1 and the
>dns server is at 192.168.1.2. The default gw for the dns server is of
>course .1. How do I prevent the dns server from sending these packets now
>and then? I just want it to act as a dns for the LAN and as a caching
>nameserver.

>I'm running the bind-version that ships with slack8.0 (bind8, maybe?)

>Marius

Hi Marius,

Im not sure, but try to set "heartbeat-interval 0;" in the options
section of your /etc/named.conf. If you have configured a slave zone,
you have to set it to "dialup yes;". As I can remember, this worked fine
for me.

Example:

options {

        [...some options stuff...]

        forward only;
        forwarders { xx.xx.xx.xx; } ;
        heartbeat-interval 0;
        };

zone "xx.xx.xx.xx.in-addr.arpa" IN {
       type slave;
       type forward;
       dialup yes;
       masters { xx.xx.xx.xx; };
       file "db.xx.xx.xx.xx";
       };

HTH
Andreas

 
 
 

named forcing a dial-up

Post by Marius Flag » Fri, 17 May 2002 06:02:11



> Im not sure, but try to set "heartbeat-interval 0;" in the options
> section of your /etc/named.conf. If you have configured a slave zone,
> you have to set it to "dialup yes;". As I can remember, this worked fine
> for me.

I have no slave zones.

I now have this in my named.conf:

options {
        directory "/var/named";
        forward only;
        forwarders ( 193.212.1.10; );
        listen-on { 127.0.0.1; 192.168.1.1;};
        heartbeat-interval 0;

Quote:};

zone "." IN {
        type hint;
        file "named.ca";

Quote:};

zone "localhost" IN {
        type master;
        file "localhost.zone";
        allow-update { none; };

Quote:};

zone "0.0.127.in-addr.arpa" IN {
        type master;
        file "named.local";
        allow-update { none; };

Quote:};

zone "local.lan" {
        type master;
        file "local.lan";

Quote:};

zone "1.168.192.in-addr.arpa" {
        type master;
        file "192.168.1";

Quote:};

Is this an ok setting for a dial-up box? I just want to server 192.168.1
and a fake domain "local.lan".

But, now I'm getting the following in my /var/log/messages:
May 15 23:00:26 gw named[1285]: ns_req: no address for root server

Any idea?

Marius

 
 
 

named forcing a dial-up

Post by Marius Flag » Fri, 17 May 2002 06:42:04



> But, now I'm getting the following in my /var/log/messages:
> May 15 23:00:26 gw named[1285]: ns_req: no address for root server

I figured this one out myself. Had to put the forwarders-option -before-
the forward only option. :) Duh..

Marius

 
 
 

named forcing a dial-up

Post by Andreas Thala » Fri, 17 May 2002 18:13:46


On Wed, 15 May 2002 23:02:11 +0200, Marius Flage



>> Im not sure, but try to set "heartbeat-interval 0;" in the options
>> section of your /etc/named.conf. If you have configured a slave zone,
>> you have to set it to "dialup yes;". As I can remember, this worked fine
>> for me.

>I have no slave zones.

>I now have this in my named.conf:

>options {
>        directory "/var/named";
>    forward only;
>    forwarders ( 193.212.1.10; );

                  ^^^^            ^^^^
I think these are the wronng brackets. Change this line to:

        forwarders { 193.212.1.10; };

Quote:>    listen-on { 127.0.0.1; 192.168.1.1;};
>    heartbeat-interval 0;
>};

[...]

Quote:>Is this an ok setting for a dial-up box? I just want to server 192.168.1
>and a fake domain "local.lan".

looks o.k.

Quote:>But, now I'm getting the following in my /var/log/messages:
>May 15 23:00:26 gw named[1285]: ns_req: no address for root server

now it should work fine.

bye
Andreas

 
 
 

named forcing a dial-up

Post by Andreas Thala » Fri, 17 May 2002 18:19:49


On Wed, 15 May 2002 23:42:04 +0200, Marius Flage



>> But, now I'm getting the following in my /var/log/messages:
>> May 15 23:00:26 gw named[1285]: ns_req: no address for root server

>I figured this one out myself. Had to put the forwarders-option -before-
>the forward only option. :) Duh..

>Marius

Works in my setup even if I put in in my named.conf as I posted
yesterday. I think you have misspelled it ( see last article Ive
posted)
 
 
 

1. 2.3 -> 2.7 via Dial-up (Re: CVS over 'dropping' dial-ups)

You are better off borrowing/buying/stealing a CD and loading a fresh 2.7
install.
From what I've heard, there are issues with upgrading via CVS.  Plus, it's
_SLOW_.
Trust me. If you don't have the cash (US $30, I believe) you could probably
ask
somebody to copy their 2.7 CD for you (hint,hint).  Of course, buying the CD
makes
OBSD 2.8 and higher a possibility, which is a Good Thing.

Good luck.

2. Let's Face It: IBM O

3. force dial-up

4. Help! promiscous mode

5. how to force dial-up?

6. Signal 11

7. Shape Ups,Men's Shape Ups,Men's Skechers Shape Ups - new styles!

8. Networking tools ?

9. Dial-up OK, Name Resolution NG

10. Dial-up Proxy & Dial-up SMTP .

11. Linux as dial-up ppp server for Win95 dial-up problem

12. Dial ups during connecting pop3 accounts

13. Unix based dial-ups