name resolution not working on new dhcp/dns server

rbees · 06-27-2009, 11:03 PM

Ladies & Gents,

OK, I moved the dhcp/dns/nat server I have been setting up to my main network. Lesson 1. do more testing.

It seams that I don't have local name resolution working when I thought I did. It does work somewhat with the one machine that migrated with the server in that the server name is recognized and resolved. Checking resolve.conf on the server reveals that my local name server is not there. I inserted it and did "/etc/init.d/networking restart" and it was gone.

The hosts file on the one working machine contains my local.only domain name and associated ip while the other machines don't have this info in that file. I did add it on my laptop but that didn't fix the problem.

Checking the bind config file through webmin reports no errors.

I have another problem that may be related. All my linux boxes and an xp box obtain their ip correctly, they are set static by my dhcp config, but 3 vista and 2 xbox's are unable to get an ip. If they are set manually they work but it puzzles me why they don't pick them up via dhcp.

I know the connection problem is not a hardware issue because 2 of the vista boxes run linux and pull their ip just fine in linux but don't in vista. Is their some specific setting for ip discovery that is needed by vista? Yes I do know that vista has connection issues but all of this hardware was working together before I brought the new server online.

Any insite is aprecieated

thanks

OdinnBurkni · 06-28-2009, 07:08 AM

Hi.
Just for curiosity, how is the dhcp setup? Can you show the dhcpd.conf file?

Regards,
Odinn Burkni

rbees · 06-28-2009, 12:09 PM

Thanks OdinnBurkni

It will take me a little bit to post the dhcp.conf because the server has no gui so it means transfering it via floppy to a box that I can post it with.

Hear are some more observations that I have made since my last post.

The new server is doing some things that the old one didn't. Namely dns and assigned static ip's to most of my local machines. The server is striped down with no gui installed.

I am able to ping google by name through the server but I am unable to ping anything on my local network, weather by ip or name, including the server itself.

Looking through the log files this morning I can see where ip's are offered to the different vista and xbox's by their associated mac or from the dynamic range depending on the contitions but they are not being accepted by them.

I have been looking through my arnos-firewall config for some kind of mistake but don't see one. Thought that might be be the problem, but it is clearly not the case for the ip problem. It may however be the cause of the dns problem.

Another observation is that page loading seams substantially slower than it use to be. I suspect my dns is not working correctly in it's cacheing mode.

rbees · 06-28-2009, 01:16 PM

The dhcpd.conf file.

I have made a few changes to it attempting to get things to work. For instarce the zone Torah-disiple.local now has the ip 192.168.7.1 where it had 127.0.0.1 when I first brought it online. Also the ipfowarding option was commented out and I uncommented it. Neither of these changes had any effect on the vista and xbox's. Just reminds me why I left wincrap behind.

Quote:

server-identifier bamod-aish;
authoritative;
ddns-update-style interim;
#include "/etc/bind/rndc.key";

zone Torah-disiple.local. {
primary 192.168.7.1;
# key "rndc-key";
}

option domain-name "Torah-disiple.local";
option domain-name-servers 192.168.7.1, 24.247.15.53, 24.247.24.53;
default-lease-time 21600;
max-lease-time 43200;
log-facility local7;

subnet 192.168.7.0 netmask 255.255.255.224 {
range 192.168.7.20 192.168.7.31;
option routers 192.168.7.1;
option ip-forwarding off;
zone 7.168.192.in-addr.arpa. {
primary bamod-aish.Torah-disiple.local;
# key "rndc-key";
}
zone Torah_disiple.local. {
primary bamod-aish.Torah-disiple.local;
# key "rndc-key";
}
}

# static addresses
host Netgear-wireless {
hardware ethernet 00:18:4d:22:c8:63;
fixed-address 192.168.7.2;
}
host DI-604 {
hardware ethernet 00:40:05:2a:f3:84;
fixed-address 192.168.7.3;
}
host Kingbee {
hardware ethernet 00:1a:73:3f:3e:3b;
fixed-address 192.168.7.5;
}
host ROBIN {
hardware ethernet 00:0c:76:15:7b:d0;
fixed-address 192.168.7.6;
}
host RBees {
hardware ethernet 00:0c:76:15:7b:d0;
fixed-address 192.168.7.6;
}
host waterlogged {
hardware ethernet 00:21:63:6b:76:ae;
fixed-address 192.168.7.7;
}
host xbox {
hardware ethernet 00:17:fa:6e:98:28;
fixed-address 192.168.7.8;
}
host youngestbee-PC {
hardware ethernet 00:1f:e1:7d:e7:dd;
fixed-address 192.168.7.9;
}
# host youngestbee {
# hardware ethernet 00:1f:e1:7d:e7:dd;
# fixed-address 192.168.7.9;
# }
host MEEEEEE {
hardware ethernet 00:0d:3a:af:7f:41;
fixed-address 192.168.7.10;
}
host HP-4Si {
hardware ethernet 08:00:09:6a:ca:ed;
fixed-address 192.168.7.15;
}
host BRN-AAED98 {
hardware ethernet 00:80:77:aa:ed:98;
fixed-address 192.168.7.16;
}
host HP-5000 {
hardware ethernet 00:01:e6:64:7d:da;
fixed-address 192.168.7.17;
}
host distraction {
hardware ethernet 00:13:20:54:30:db;
fixed-address 192.168.7.11;
}

rbees · 07-02-2009, 04:27 PM

I did get the dhcp issue fixed. See this thread
http://www.linuxquestions.org/questi...rectly-736697/

I am still having dns issues though.

chrism01 · 07-03-2009, 02:29 AM

This may seem a bit off the wall, but you do know disiple <> disciple http://dictionary.reference.com/dic?...&search=search ?
Possibly a typo??

rbees · 07-03-2009, 05:44 AM

One of these days I will learn to spell, maybe. They say it is hard to teach old dogs new tricks. Seams to be true in my case.

Anyway I corrected the spelling errors in the dhcpd.conf file and that seams to have fixed the dns issue.

Thanks