[TriLUG] DNS server revisited

[Roy Vestal]

I get the IP of my cable modem when I dig web.home.linux, but I get 
"host web.home.linux not found: 3(NXDOMAIN)"

So I've missed something.

My resolv.conf:
domain home.linux
nameserver 192.168.0.1

Scott Lambdin wrote:
> Your workstation goes straight to the name server with this?  What is
> showing up in messages when you do a "host web.home.linux" on your
> workstation?
>
> home.linux.zone:
> #begin
> $TTL 900
> @       IN      SOA     ns.mydomain.local. my.email.address. (
>                        200809160 ; serial, todays date + todays serial #
>                        8H    ; refresh, seconds
>                        2H    ; retry, seconds
>                        4W    ; expire, seconds
>                        900 )   ; minimum, seconds
> ;
>                NS      ns    ; Inet Address of name server
> @                         IN   A  127.0.0.1
> ns                             IN   A  192.168.0.1
> server1.home.linux  IN   A  192.168.0.3
> web.home.linux       IN   A  192.168.0.2
> #EOF
> On Thu, Nov 6, 2008 at 9:30 PM, Roy Vestal <rvestal at trilug.org> wrote:
>
>   
>> OK, so I'm "resurrecting" this thread. Been reading and such and now I'm
>> at a point I think with help I can get it working the way I hope to get
>> it working.
>>
>> I want to be on my desktop (dhcp) and be able to browse to my webserver
>> (web.home.linux) and get it to go to the internal network. I know it can
>> be done, but I'm not sure what I've done wrong. My DNS works great outside.
>>
>> Here's the setup:
>>
>> Network:
>> simple home network:
>> Cable modem - dhcp
>> Brand X Cable Router w/4port switch and wireless
>> 192.168.0.0/255.255.255.0
>> internal network name: home.linux
>> DynDNS server connection for home website
>>
>> Webserver:
>> IP 192.168.0.2
>> hostname: web.home.linux
>>
>> FileServer1:
>> IP 192.168.0.3
>> server1.home.linux
>>
>> DNS/DHCP Server:
>> CentOS 5.2
>> bind w/bind-chroot 9.3.4-6.0.2
>> dhcp 3.0.5
>> IP 192.168.0.1
>> hostname dns.home.linux
>>
>> dhcpd.conf:
>> #begin
>> ddns-update-style interim;
>> default-lease-time 600;
>> max-lease-time 7200;
>> option subnet-mask 255.255.255.0;
>> option broadcast-address 192.168.147.255;
>> option routers 192.168.0.100;
>> option domain-name-servers 192.168.0.1;
>> option domain-name "home.linux";
>> subnet 192.168.147.0 netmask 255.255.255.0 {
>>        range 192.168.147.50 192.168.147.60;
>>        host web.home.linux {
>>             hardware ethernet 08:00:aa:bb:cc:dd;
>>             fixed-address 192.168.0.2;
>>        }
>>        host server1.home.linux {
>>             hardware ethernet 00:07:aa:bb:cc:dd;
>>             fixed-address 192.168.0.3;
>>        }
>> }
>> #EOF
>>
>> named.conf:
>> #begin
>> options {
>>        directory    "/var/named";
>>        query-source port 53;
>> allow-transfer {
>>        localhost;
>> };
>> };
>> zone "home.linux" {
>>        type master;
>>        file "home.linux.zone";
>> };
>> zone "localhost" {
>>        type master;
>>        file "localhost.zone";
>> };
>> zone "0.0.127.in-addr.arpa" {
>>        type master;
>>        file "127.0.0.rev";
>> };
>> zone "." in {
>>        type hint;
>>        file "root.db";
>> };
>> #EOF
>>
>> home.linux.zone:
>> #begin
>> $TTL 900
>> @       IN      SOA     ns.mydomain.local. my.email.address. (
>>                        200809160 ; serial, todays date + todays serial #
>>                        8H    ; refresh, seconds
>>                        2H    ; retry, seconds
>>                        4W    ; expire, seconds
>>                        900 )   ; minimum, seconds
>> ;
>>                NS      ns    ; Inet Address of name server
>> @                         IN   A  127.0.0.1
>> ns                             IN   A  192.168.0.1
>> server1.home.linux  IN   A  192.168.0.3
>> web.home.linux       IN   A  192.168.0.2
>> #EOF
>>
>> So, the local names don't work. The outside does. HELP!!
>>
>> TIA,
>> Roy
>> --
>> TriLUG mailing list        : http://www.trilug.org/mailman/listinfo/trilug
>> TriLUG FAQ  : http://www.trilug.org/wiki/Frequently_Asked_Questions
>>
>>     
>
>
>
>