[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: bind9 problems



-----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 connected computers resolve dns queries at the router? My goal is
> to make all computers on the local network automatically use my bind9
> server.
>> How are you exactly querying the router? Did you added the router's
>> local IP into the DNS zone?
>>
>>   
> With 'nslookup mylocaldomain.com 192.168.1.1'. I don't know much about
> DNS. I attach my zone files.
> 
Can you login to your router? Webinterface?
If the webinterface has a ping tool, try ping some name (google.com for
example). See if your router can resolve those names itself.
Try ping your servers IP too, can your router reach it?

if you can login, and have some sort of dig or nslookup, you should
check if it can reach your server (dig @serverIP somename). Check both,
with and without your servers ip as parameter.

During those checks, you maybe want enable your servers querylog and
check if anything arrives at your server. 'rndc querylog'
check var/log/daemon.log for messages (you should see something about
rndc, else you log somewhere else, check your bind config then)

What is the output if you use 'dig @192.168.1.1 mylocaldomain.com' at
your lenny server? Anything in the logfile?



Your ultimate goal is to give your server as dns during dhcp setup. This
can be a hard task depending on your router. Hosting dhcp server on the
server machine may be a easy and convient solution. You dont depend on
your router for lan setup anymore (and you can do fancy things with dhcp).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iF4EAREIAAYFAkxNsuUACgkQpjmLjrU66/5BhgD/d4OU/m/Dw1yr4e8TWglmEmey
uxsYgObgGQrJo8MupC0BAJuje4wef03GLtTBSesmMle3Z3HsFbaEz18eQ0+mXLqw
=PC10
-----END PGP SIGNATURE-----


Reply to: