Internal DNS resolution look up fails

Bit Twister

On Tue, 08 Jan 2008 11:54:22 +0100, herman.viaene@thuis.be wrote:
>
> Compared with mine, seems OK

That's good because it is working.

The post you responded to was about my solution and a resource for
anyone wanting to use goggle.com to find a working setup.


>> Here is a snippet from my /etc/hosts
>> $ head -4 /etc/hosts
>> 127.0.0.1 localhost.localdomain localhost
>> 192.168.1.11 fw.home.bogus fw
>> 192.168.1.130 wb.home.bogus wb
>> 192.168.1.131 beta.home.bogus beta
>>
>>
>
> In my /etc/hosts file I have only the localhost and my own machine name, and
> frankly, I do not see the sense in having others in this file. It's just a
> possible source of conflict with what you define in your DNS?????

I hear where you are coming from, but I have several distributions and
versions of distributions installed on two machines. Each install has a
separate ip address. That keeps ssh from complaining about possible
man-in-the-middle attacks, remove offending key from .ssh/known.hosts messages.

Only two installs have bind running. That is why I wrote the script to
create the home.(zone,reversed) files.

>> edt /var/lib/named/etc/named.conf

> Contents seems OK, bu are you sure this is the file that is actually used -

Yes, pretty sure, otherwise how would it have known to find home.zone. :-)

> or updated via MCC.

Hehehe, that would make a bunch of people happy on a bind update.

> In my setup the file is /etc/named.conf , I checked twice.

I can believe that is what you saw.

> I have indeed a /var/lib/named/etc/named.conf file, but I don't know
> where it comes from, and that's definitely the one that is used.

/var/lib/named/etc/named.conf came from the install. Check your
/etc/named.conf with the command:

ls -al /etc/named.conf

My 2008.0 bind install creates
$ ls -al /etc/named.conf
lrwxrwxrwx 1 root root 31 2008-01-06 06:24 /etc/named.conf ->
../var/lib/named/etc/named.conf

(munged to suppress line too long msg)

herman.viaene@thuis.be

Bit Twister wrote:

> On Tue, 08 Jan 2008 11:54:22 +0100, herman.viaene@thuis.be wrote:
>>
>> Compared with mine, seems OK
>
> That's good because it is working.
>
> The post you responded to was about my solution and a resource for
> anyone wanting to use goggle.com to find a working setup.
>

fine then

>
>> Contents seems OK, bu are you sure this is the file that is actually used
>> -
>
> Yes, pretty sure, otherwise how would it have known to find home.zone.
> :-)
>
>> or updated via MCC.
>
> Hehehe, that would make a bunch of people happy on a bind update.
>
>> In my setup the file is /etc/named.conf , I checked twice.
>
> I can believe that is what you saw.
>
>> I have indeed a /var/lib/named/etc/named.conf file, but I don't know
>> where it comes from, and that's definitely the one that is used.
>
> /var/lib/named/etc/named.conf came from the install. Check your
> /etc/named.conf with the command:
>
> ls -al /etc/named.conf
>
> My 2008.0 bind install creates
> $ ls -al /etc/named.conf
> lrwxrwxrwx 1 root root 31 2008-01-06 06:24 /etc/named.conf ->
> ../var/lib/named/etc/named.conf
>
well,well

ls -al /etc/named.conf
-rw-rw-r-- 1 root root 751 Jan 6 09:58 /etc/named.conf

and it's not made up!!! I run 2007.0, but I guess that is not the reason. It
probably comes from me. I have a backup partition for /etc and a few
others, so when I do a new install, I copy a bunch of files back, and that
often gets me up a lot quicker. It's possible I just have overwritten the
link???

Herman

--
Veel mensen danken hun goed geweten aan hun slecht geheugen. (G. Bomans)

Lots of people owe their good conscience to their bad memory (G. Bomans)

herman.viaene@thuis.be

Bit Twister wrote:

> On Tue, 08 Jan 2008 11:54:22 +0100, herman.viaene@thuis.be wrote:
>>
>> Compared with mine, seems OK
>
> That's good because it is working.
>
> The post you responded to was about my solution and a resource for
> anyone wanting to use goggle.com to find a working setup.
>

fine then

>
>> Contents seems OK, bu are you sure this is the file that is actually used
>> -
>
> Yes, pretty sure, otherwise how would it have known to find home.zone.
> :-)
>
>> or updated via MCC.
>
> Hehehe, that would make a bunch of people happy on a bind update.
>
>> In my setup the file is /etc/named.conf , I checked twice.
>
> I can believe that is what you saw.
>
>> I have indeed a /var/lib/named/etc/named.conf file, but I don't know
>> where it comes from, and that's definitely the one that is used.
>
> /var/lib/named/etc/named.conf came from the install. Check your
> /etc/named.conf with the command:
>
> ls -al /etc/named.conf
>
> My 2008.0 bind install creates
> $ ls -al /etc/named.conf
> lrwxrwxrwx 1 root root 31 2008-01-06 06:24 /etc/named.conf ->
> ../var/lib/named/etc/named.conf
>
well,well

ls -al /etc/named.conf
-rw-rw-r-- 1 root root 751 Jan 6 09:58 /etc/named.conf

and it's not made up!!! I run 2007.0, but I guess that is not the reason. It
probably comes from me. I have a backup partition for /etc and a few
others, so when I do a new install, I copy a bunch of files back, and that
often gets me up a lot quicker. It's possible I just have overwritten the
link???

Herman

--
Veel mensen danken hun goed geweten aan hun slecht geheugen. (G. Bomans)

Lots of people owe their good conscience to their bad memory (G. Bomans)

Bit Twister

On Tue, 08 Jan 2008 15:33:22 +0100, herman.viaene@thuis.be wrote:
>
> ls -al /etc/named.conf
> -rw-rw-r-- 1 root root 751 Jan 6 09:58 /etc/named.conf
>
> and it's not made up!!! I run 2007.0, but I guess that is not the reason. It
> probably comes from me. I have a backup partition for /etc and a few
> others, so when I do a new install, I copy a bunch of files back, and that
> often gets me up a lot quicker. It's possible I just have overwritten the
> link???

Hard to say. bind on 2008.0 is installed to run chrooted and I have no idea
about 2007.

Off hand I would say you wiped the link since you mentioned
/var/lib/named/etc/named.conf was on 2007.0.

Do bear in mind, I am a 5 day old newbie on bind.

Bit Twister

On Tue, 08 Jan 2008 15:33:22 +0100, herman.viaene@thuis.be wrote:
>
> ls -al /etc/named.conf
> -rw-rw-r-- 1 root root 751 Jan 6 09:58 /etc/named.conf
>
> and it's not made up!!! I run 2007.0, but I guess that is not the reason. It
> probably comes from me. I have a backup partition for /etc and a few
> others, so when I do a new install, I copy a bunch of files back, and that
> often gets me up a lot quicker. It's possible I just have overwritten the
> link???

Hard to say. bind on 2008.0 is installed to run chrooted and I have no idea
about 2007.

Off hand I would say you wiped the link since you mentioned
/var/lib/named/etc/named.conf was on 2007.0.

Do bear in mind, I am a 5 day old newbie on bind.

herman.viaene@thuis.be

Bit Twister wrote:

> On Sun, 06 Jan 2008 10:18:34 +0100, herman.viaene@thuis.be wrote:
>
>> Back in MDK9.2 I got DNS working by manually fiddling the files.
>> Apparently now (2007.0 for me), these old files do not work anymore, so I
>> just used MCC - Network Services - DNS server, and it works!!!!
>>
>> The only problem I have with this tool is that it gives very little
>> feedback (first define a server, then add hosts one by one), and it DOES
>> NOT RESTART named , so you have to do that yourself after finishing your
>> changes.
>
> Tried, your suggestion, and was not about to add 20+ hosts,
> so I edited the forward and reverse files. Did a
> service named restart
> and found out named would not shutdown.
> Sorry I did not keep the message. It was misleading as to the problem.
> It was 5 am and was I chapped at yet another alligator biting my tail.
> chkconfig --del named
> reboot
> urpme bind
> urpmi bind --auto
>
>
> My forward/reverse files look as follows:
> $ head -17 /var/lib/named/var/named/master/home.zone
> $TTL 1D
> @ IN SOA wb.home.bogus. admin.wb.home.bogus. (
> 2008010601 ; Serial num yyymmddnn
> 1D ; Refresh
> 6H ; Retry
> 1W ; Expire
> 1H ; Minimum TTL
> )
> ; DNS Servers
> IN NS wb.home.bogus.
> ;
> ; Machine Names
> localhost A 127.0.0.1
> dnsmaster IN CNAME wb.home.bogus.
> fw.home.bogus. IN A 192.168.1.11
> wb.home.bogus. IN A 192.168.1.130
> beta.home.bogus. IN A 192.168.1.131
>
>

Compared with mine, seems OK

>
> $ head -14 /var/lib/named/var/named/reverse/home.reversed
> $TTL 1D
> @ IN SOA wb.home.bogus. wb.home.bogus.(
> 2008010601 ; Serial num yyymmddnn
> 8H ; Refresh
> 4H ; Retry
> 1W ; Expire
> 1D ; Minimum TTL
> )
> ;
> NS wb.home.bogus.
> ; Machine Ip addresses
> 11 IN PTR fw.home.bogus.
> 130 IN PTR wb.home.bogus.
> 131 IN PTR beta.home.bogus.
>
>

Idem

> Here is my install procedure and script to automagically generate the 2
> files. Note: I am using OpenDNS.com name servers in forwarders.
>
> Upside, the protect you from phishing scams by blocking the fraudulent
> sites from resolving on your network.
>
> Downside, They return 208.69.32.170 on a not found: 3(NXDOMAIN)
>

OK, I cannot comment on this.

> Here is a snippet from /etc/hosts
> $ head -4 /etc/hosts
> 127.0.0.1 localhost.localdomain localhost
> 192.168.1.11 fw.home.bogus fw
> 192.168.1.130 wb.home.bogus wb
> 192.168.1.131 beta.home.bogus beta
>
>

In my /etc/hosts file I have only the localhost and my own machine name, and
frankly, I do not see the sense in having others in this file. It's just a
possible source of conflict with what you define in your DNS?????

> $ cat /local/doc/bind_install.txt
snip..

> edt /var/lib/named/etc/named.conf
>
> And find forwarders and add/change these
>
> // http://opendns.com DNS servers
> forwarders { 208.67.222.222; 208.67.220.220; };
>
> And append these zones to the bottom:
>
> zone "home.bogus" IN {
> type master;
> file "master/home.zone";
> allow-update { none; };
> };
>
> zone "1.168.192.in-addr.arpa" IN {
> type master;
> file "reverse/home.reversed";
> allow-update { none; };
> };
>
> Click Save, Quit
>
>
Contents seems OK, bu are you sure this is the file that is actually used -
or updated via MCC.
In my setup the file is /etc/named.conf , I checked twice. I have indeed
a /var/lib/named/etc/named.conf file, but I don't know where it comes from,
and that's definitely the one that is used.
>

snip more......

--
Veel mensen danken hun goed geweten aan hun slecht geheugen. (G. Bomans)

Lots of people owe their good conscience to their bad memory (G. Bomans)

Bit Twister

On Tue, 08 Jan 2008 11:54:22 +0100, herman.viaene@thuis.be wrote:
>
> Compared with mine, seems OK

That's good because it is working.

The post you responded to was about my solution and a resource for
anyone wanting to use goggle.com to find a working setup.


>> Here is a snippet from my /etc/hosts
>> $ head -4 /etc/hosts
>> 127.0.0.1 localhost.localdomain localhost
>> 192.168.1.11 fw.home.bogus fw
>> 192.168.1.130 wb.home.bogus wb
>> 192.168.1.131 beta.home.bogus beta
>>
>>
>
> In my /etc/hosts file I have only the localhost and my own machine name, and
> frankly, I do not see the sense in having others in this file. It's just a
> possible source of conflict with what you define in your DNS?????

I hear where you are coming from, but I have several distributions and
versions of distributions installed on two machines. Each install has a
separate ip address. That keeps ssh from complaining about possible
man-in-the-middle attacks, remove offending key from .ssh/known.hosts messages.

Only two installs have bind running. That is why I wrote the script to
create the home.(zone,reversed) files.

>> edt /var/lib/named/etc/named.conf

> Contents seems OK, bu are you sure this is the file that is actually used -

Yes, pretty sure, otherwise how would it have known to find home.zone. :-)

> or updated via MCC.

Hehehe, that would make a bunch of people happy on a bind update.

> In my setup the file is /etc/named.conf , I checked twice.

I can believe that is what you saw.

> I have indeed a /var/lib/named/etc/named.conf file, but I don't know
> where it comes from, and that's definitely the one that is used.

/var/lib/named/etc/named.conf came from the install. Check your
/etc/named.conf with the command:

ls -al /etc/named.conf

My 2008.0 bind install creates
$ ls -al /etc/named.conf
lrwxrwxrwx 1 root root 31 2008-01-06 06:24 /etc/named.conf ->
../var/lib/named/etc/named.conf

(munged to suppress line too long msg)

herman.viaene@thuis.be

Bit Twister wrote:

> On Tue, 08 Jan 2008 11:54:22 +0100, herman.viaene@thuis.be wrote:
>>
>> Compared with mine, seems OK
>
> That's good because it is working.
>
> The post you responded to was about my solution and a resource for
> anyone wanting to use goggle.com to find a working setup.
>

fine then

>
>> Contents seems OK, bu are you sure this is the file that is actually used
>> -
>
> Yes, pretty sure, otherwise how would it have known to find home.zone.
> :-)
>
>> or updated via MCC.
>
> Hehehe, that would make a bunch of people happy on a bind update.
>
>> In my setup the file is /etc/named.conf , I checked twice.
>
> I can believe that is what you saw.
>
>> I have indeed a /var/lib/named/etc/named.conf file, but I don't know
>> where it comes from, and that's definitely the one that is used.
>
> /var/lib/named/etc/named.conf came from the install. Check your
> /etc/named.conf with the command:
>
> ls -al /etc/named.conf
>
> My 2008.0 bind install creates
> $ ls -al /etc/named.conf
> lrwxrwxrwx 1 root root 31 2008-01-06 06:24 /etc/named.conf ->
> ../var/lib/named/etc/named.conf
>
well,well

ls -al /etc/named.conf
-rw-rw-r-- 1 root root 751 Jan 6 09:58 /etc/named.conf

and it's not made up!!! I run 2007.0, but I guess that is not the reason. It
probably comes from me. I have a backup partition for /etc and a few
others, so when I do a new install, I copy a bunch of files back, and that
often gets me up a lot quicker. It's possible I just have overwritten the
link???

Herman

--
Veel mensen danken hun goed geweten aan hun slecht geheugen. (G. Bomans)

Lots of people owe their good conscience to their bad memory (G. Bomans)

herman.viaene@thuis.be

Bit Twister wrote:

> On Sun, 06 Jan 2008 10:18:34 +0100, herman.viaene@thuis.be wrote:
>
>> Back in MDK9.2 I got DNS working by manually fiddling the files.
>> Apparently now (2007.0 for me), these old files do not work anymore, so I
>> just used MCC - Network Services - DNS server, and it works!!!!
>>
>> The only problem I have with this tool is that it gives very little
>> feedback (first define a server, then add hosts one by one), and it DOES
>> NOT RESTART named , so you have to do that yourself after finishing your
>> changes.
>
> Tried, your suggestion, and was not about to add 20+ hosts,
> so I edited the forward and reverse files. Did a
> service named restart
> and found out named would not shutdown.
> Sorry I did not keep the message. It was misleading as to the problem.
> It was 5 am and was I chapped at yet another alligator biting my tail.
> chkconfig --del named
> reboot
> urpme bind
> urpmi bind --auto
>
>
> My forward/reverse files look as follows:
> $ head -17 /var/lib/named/var/named/master/home.zone
> $TTL 1D
> @ IN SOA wb.home.bogus. admin.wb.home.bogus. (
> 2008010601 ; Serial num yyymmddnn
> 1D ; Refresh
> 6H ; Retry
> 1W ; Expire
> 1H ; Minimum TTL
> )
> ; DNS Servers
> IN NS wb.home.bogus.
> ;
> ; Machine Names
> localhost A 127.0.0.1
> dnsmaster IN CNAME wb.home.bogus.
> fw.home.bogus. IN A 192.168.1.11
> wb.home.bogus. IN A 192.168.1.130
> beta.home.bogus. IN A 192.168.1.131
>
>

Compared with mine, seems OK

>
> $ head -14 /var/lib/named/var/named/reverse/home.reversed
> $TTL 1D
> @ IN SOA wb.home.bogus. wb.home.bogus.(
> 2008010601 ; Serial num yyymmddnn
> 8H ; Refresh
> 4H ; Retry
> 1W ; Expire
> 1D ; Minimum TTL
> )
> ;
> NS wb.home.bogus.
> ; Machine Ip addresses
> 11 IN PTR fw.home.bogus.
> 130 IN PTR wb.home.bogus.
> 131 IN PTR beta.home.bogus.
>
>

Idem

> Here is my install procedure and script to automagically generate the 2
> files. Note: I am using OpenDNS.com name servers in forwarders.
>
> Upside, the protect you from phishing scams by blocking the fraudulent
> sites from resolving on your network.
>
> Downside, They return 208.69.32.170 on a not found: 3(NXDOMAIN)
>

OK, I cannot comment on this.

> Here is a snippet from /etc/hosts
> $ head -4 /etc/hosts
> 127.0.0.1 localhost.localdomain localhost
> 192.168.1.11 fw.home.bogus fw
> 192.168.1.130 wb.home.bogus wb
> 192.168.1.131 beta.home.bogus beta
>
>

In my /etc/hosts file I have only the localhost and my own machine name, and
frankly, I do not see the sense in having others in this file. It's just a
possible source of conflict with what you define in your DNS?????

> $ cat /local/doc/bind_install.txt
snip..

> edt /var/lib/named/etc/named.conf
>
> And find forwarders and add/change these
>
> // http://opendns.com DNS servers
> forwarders { 208.67.222.222; 208.67.220.220; };
>
> And append these zones to the bottom:
>
> zone "home.bogus" IN {
> type master;
> file "master/home.zone";
> allow-update { none; };
> };
>
> zone "1.168.192.in-addr.arpa" IN {
> type master;
> file "reverse/home.reversed";
> allow-update { none; };
> };
>
> Click Save, Quit
>
>
Contents seems OK, bu are you sure this is the file that is actually used -
or updated via MCC.
In my setup the file is /etc/named.conf , I checked twice. I have indeed
a /var/lib/named/etc/named.conf file, but I don't know where it comes from,
and that's definitely the one that is used.
>

snip more......

--
Veel mensen danken hun goed geweten aan hun slecht geheugen. (G. Bomans)

Lots of people owe their good conscience to their bad memory (G. Bomans)

Bit Twister

On Tue, 08 Jan 2008 15:33:22 +0100, herman.viaene@thuis.be wrote:
>
> ls -al /etc/named.conf
> -rw-rw-r-- 1 root root 751 Jan 6 09:58 /etc/named.conf
>
> and it's not made up!!! I run 2007.0, but I guess that is not the reason. It
> probably comes from me. I have a backup partition for /etc and a few
> others, so when I do a new install, I copy a bunch of files back, and that
> often gets me up a lot quicker. It's possible I just have overwritten the
> link???

Hard to say. bind on 2008.0 is installed to run chrooted and I have no idea
about 2007.

Off hand I would say you wiped the link since you mentioned
/var/lib/named/etc/named.conf was on 2007.0.

Do bear in mind, I am a 5 day old newbie on bind.