On Wed, 21 Mar 2007, Justin Hartman wrote:
Hi guys
Very strange problem which I'm sure is pretty easy to fix - if you
know how. I installed bind9 with lsb-base on a Debian Etch system. The
problem is that as soon as bind9 is installed I can no longer ping or
access external sites from the
Hi guys
Very strange problem which I'm sure is pretty easy to fix - if you
know how. I installed bind9 with lsb-base on a Debian Etch system. The
problem is that as soon as bind9 is installed I can no longer ping or
access external sites from the bind9 server.
For example I can't ping
Am Mittwoch, 21. März 2007 19:10 schrieb Justin Hartman:
Very strange problem which I'm sure is pretty easy to fix - if you
know how. I installed bind9 with lsb-base on a Debian Etch system. The
problem is that as soon as bind9 is installed I can no longer ping or
access external sites from
On 3/21/07, Oliver Jato [EMAIL PROTECTED] wrote:
you'll probably have to tell bind to use recursion for fetching adresses which
are not in his authority. in options, set allow-recursion { 127.0.0.1; };.
if you want others on your network to use your bind, too, also
add 192.168.1/24;, for
Am Mittwoch, 21. März 2007 19:48 schrieb Justin Hartman:
On 3/21/07, Oliver Jato [EMAIL PROTECTED] wrote:
you'll probably have to tell bind to use recursion for fetching adresses
which are not in his authority. in options, set allow-recursion {
127.0.0.1; };. if you want others on your
On 3/21/07, Oliver Jato [EMAIL PROTECTED] wrote:
sorry, i forgot that you'll have to add recursion yes; to enable recursion.
the allow-recursion part was only to filter for whom your bind will resolve
recursive queries. you'll have to add both inside the options { ... }; part
of your
On 3/21/07, Justin Hartman [EMAIL PROTECTED] wrote:
On 3/21/07, Oliver Jato [EMAIL PROTECTED] wrote:
sorry, i forgot that you'll have to add recursion yes; to enable
recursion.
the allow-recursion part was only to filter for whom your bind will
resolve
recursive queries. you'll have to add
Soma thanks for your input - by removing bind and playing with
resolv.conf it is apparent that this file was causing certain issues.
I have now installed resolvconf and after rebooting resolvconf
configured only one line in resolv.conf file as follows:
nameserver: 127.0.0.1
Prior to installing
On Wed, 21 Mar 2007, Justin Hartman wrote:
Soma thanks for your input - by removing bind and playing with
resolv.conf it is apparent that this file was causing certain issues.
I have now installed resolvconf and after rebooting resolvconf
configured only one line in resolv.conf file as
On 3/21/07, Jeff D [EMAIL PROTECTED] wrote:
so with a clean bind install you still are not able to do lookups?
Correct. Clean install
what does host google.com 127.0.0.1 give you?
$ host google.com 127.0.0.1
;; connection timed out; no servers could be reached
$ nslookup
google.com
Could this issue also not have something to do with the way in which
my interfaces is setup?
I'm thinking aloud here because I don't really know but in order for
me to be able to setup two nameservers I was assigned a new IP range
which I had to configure in the /etc/network/interfaces file.
My
On Wed, 21 Mar 2007, Justin Hartman wrote:
On 3/21/07, Jeff D [EMAIL PROTECTED] wrote:
so with a clean bind install you still are not able to do lookups?
Correct. Clean install
what does host google.com 127.0.0.1 give you?
$ host google.com 127.0.0.1
;; connection timed out; no servers
On 3/21/07, Jeff D [EMAIL PROTECTED] wrote:
ok, check /etc/bind/named.conf , make sure you have :
zone . {
type hint;
file /etc/bind/db.root;
};
Yes I do. I also have the following rdns entries directly below that:
zone 127.in-addr.arpa {
type master;
file
On Wed, 21 Mar 2007, Justin Hartman wrote:
On 3/21/07, Jeff D [EMAIL PROTECTED] wrote:
so with a clean bind install you still are not able to do lookups?
Correct. Clean install
what does host google.com 127.0.0.1 give you?
$ host google.com 127.0.0.1
;; connection timed out; no servers
On 3/21/07, Jeff D [EMAIL PROTECTED] wrote:
so with a clean bind install you still are not able to do lookups?
Correct. Clean install
what does host google.com 127.0.0.1 give you?
$ host google.com 127.0.0.1
;; connection timed out; no servers could be reached
$ nslookup
On 3/22/07, Jeff D [EMAIL PROTECTED] wrote:
Just out of curiosity, are you seeing any errors in your logs when you do
these look ups or when the server starts?
Where exactly would I find the right log files to see this info?
--
Regards
Justin Hartman
PGP Key ID: 102CC123
--
To UNSUBSCRIBE,
On 3/22/07, Jeff D [EMAIL PROTECTED] wrote:
Just out of curiosity, are you seeing any errors in your logs when you
do
these look ups or when the server starts?
Where exactly would I find the right log files to see this info?
/var/log/syslog
--
To UNSUBSCRIBE, email to [EMAIL
On Thu, 22 Mar 2007, Justin Hartman wrote:
On 3/22/07, Jeff D [EMAIL PROTECTED] wrote:
Just out of curiosity, are you seeing any errors in your logs when you do
these look ups or when the server starts?
Where exactly would I find the right log files to see this info?
--
Regards
Justin
There are absolutely zero errors in the syslog file on either startup
or when I do any look ups.
On 3/22/07, Julian De Marchi [EMAIL PROTECTED] wrote:
On 3/22/07, Jeff D [EMAIL PROTECTED] wrote:
Just out of curiosity, are you seeing any errors in your logs when you
do
these look ups or
Correction - /var/log/daemon.log does show an error relating to bind:
Mar 22 06:16:46 justinhartman lwresd[2413]: starting BIND 9.3.4
Mar 22 06:16:46 justinhartman lwresd[2413]: found 1 CPU, using 1 worker thread
Mar 22 06:16:46 justinhartman lwresd[2413]: loading configuration from
On Thu, 22 Mar 2007, Justin Hartman wrote:
Correction - /var/log/daemon.log does show an error relating to bind:
Mar 22 06:16:46 justinhartman lwresd[2413]: starting BIND 9.3.4
Mar 22 06:16:46 justinhartman lwresd[2413]: found 1 CPU, using 1 worker
Mar 22 06:16:46 justinhartman lwresd[2413]:
Would you believe it but bind9 had sweet nothing to do with the
problem. The issue lay in the interfaces configuration file all along.
In my email below I had configured eth0:0 but the IP address used in
this was actually the subnet ip. As soon as I removed this everything
went back to normal...
22 matches
Mail list logo
