Thanks to you all! I ended up using a local dhcp server.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c4ec04d.1060...@gmail.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am 26.07.10 15:35, schrieb Panayiotis Karabassis:
> Sorry but I am somewhat of a newbie.
>
> Camaleón wrote:
>> I'm not sure what are your goals with this step because the router
>> hasn't to resolve local dns queries, but bind9 :-?
>>
> Don't co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am 26.07.10 15:17, schrieb Miles Fidelman:
> Panayiotis Karabassis wrote:
>> The DNS server seems to be working fine when accessed directly (i.e.
>> through nslookup or by setting it as the primary nameserver for the
>> computer manually throught /et
On Mon, 26 Jul 2010 16:35:08 +0300, Panayiotis Karabassis wrote:
> Sorry but I am somewhat of a newbie.
>
> Camaleón wrote:
>> I'm not sure what are your goals with this step because the router
>> hasn't to resolve local dns queries, but bind9 :-?
>>
> Don't connected computers resolve dns que
Panayiotis Karabassis wrote:
Two thoughts come to mind:
1. see if you can traceroute the nameserver from somewhere off your
local network (make sure to traceroute to port 53)
The nameserver is not visible to the external world. Should I forward
the port?
2. look at your router config - see
Miles Fidelman wrote:
Perhaps a silly thought, but home routers are usually configured to
access an external nameserver not one on the local network. Perhaps
it can't reach the nameserver.
I was thinking the same thing.
Two thoughts come to mind:
1. see if you can traceroute the nameserver
Sorry but I am somewhat of a newbie.
Camaleón wrote:
I'm not sure what are your goals with this step because the router hasn't
to resolve local dns queries, but bind9 :-?
Don't connected computers resolve dns queries at the router? My goal is
to make all computers on the local network automa
On Mon, 26 Jul 2010 14:56:53 +0300, Panayiotis Karabassis wrote:
> I have setup a local DNS server on my home network (bind9 on debian
> lenny).
>
> The DNS server seems to be working fine when accessed directly (i.e.
> through nslookup or by setting it as the primary nameserver for the
> compute
Panayiotis Karabassis wrote:
I have setup a local DNS server on my home network (bind9 on debian
lenny).
The DNS server seems to be working fine when accessed directly (i.e.
through nslookup or by setting it as the primary nameserver for the
computer manually throught /etc/resolv.conf).
So
Hi,
are you maybe using your router as forwarder in your bind9 configuration?
regards
On Monday 26 July 2010 13:56:53 Panayiotis Karabassis wrote:
> Hi!
>
> I have setup a local DNS server on my home network (bind9 on debian lenny).
>
> The DNS server seems to be working fine when accessed dir
Manuel Hofer wrote:
Hi,
are you maybe using your router as forwarder in your bind9 configuration?
regards
Thank you for your reply. No, I am using my ISP's nameservers.
A little more info. I followed the article at [1]. Minus the stuff about
chroot. If it would help I can post the related
Hi!
I have setup a local DNS server on my home network (bind9 on debian lenny).
The DNS server seems to be working fine when accessed directly (i.e.
through nslookup or by setting it as the primary nameserver for the
computer manually throught /etc/resolv.conf).
So I tried setting it as the
Hi.
I work for a DNS-provider with a six-digit number of zones in our main
nameserver.
The main nameserver is running Debian etch, kept up to date with security
patches from security.debian.org.
After the by now well-known OpenSSL security upgrade (openssl 0.9.8c-4etch1
-> 0.9.8c-4etch3) and a r
13 matches
Mail list logo
