dns/name resolution problems

yoda · 1 Nov 2006 at 11:54

oky... I got custom linux server on the network....
it's got DNS installed....
it's got squid installed
configured to link with external name servers and everything work fine for 'external' dns.... web browsing ect

However, internal is another matter...
The server has no name resolution for the other PC's on the network at all.
it's only when XP does it's own resolution that it actually starts to work.

How can I get samba to update the dns for internal PC's?

dangermouse · 1 Nov 2006 at 19:33

samba doesn't handle dns request afaik, i think it will do wins resolution though, you will probably be better off setting up the dns server to do internal dns lookups.

I've got BIND running here which does DNS for my home network and caches dns request for the internet.

yoda · 2 Nov 2006 at 09:16

I'm using bind... it does internet lookups fine but doesn't have any entries for local network.

How do i set it to resolve local network addresses?

and whats WINS? I never used it at all befor....

Una · 2 Nov 2006 at 09:43

You need to add zone records and such. To save typing it out briefly, here is a detailed guide:

http://evpc.biz/computing/Linux/using_BIND_as_a_local_DNS_server

Even though its for FC, the bind stuff/principle is the same.

uk_viper · 2 Nov 2006 at 10:00

which os you using,

can you show your resolv.conf , network interface config file e.g. /etc/ssconfig/network-scripts/ifcfg-eth0 (fedoras one) , gateway config file if yu have one

yoda · 2 Nov 2006 at 13:06

OS is LFS 6.1.1
Config files as follows....

resolv.conf

Code:

search silvercrown.net
nameserver 127.0.0.1
nameserver 192.168.1.9
nameserver 192.168.1.254
nameserver 195.184.228.6
nameserver 192.184.228.7

/etc/sysconfig/network-devices/ifconfig.eth0/ipv4

Code:

 ONBOOT=yes
SERVICE=ipv4-static
IP=192.168.1.3
GATEWAY=192.168.1.254
PREFIX=24
BROADCAST=192.168.1.255

named.conf

Code:

options {
	 directory "/etc/namedb";
	pid-file "/var/run/named.pid";
	statistics-file "/var/run/named.stats";
};
controls {
	 inet 127.0.0.1 allow { localhost; } keys { rndc_key; };
};
key "rndc_key" {
	 algorithm hmac-md5;
	 secret "bU2V8lsbMqS9Y/bvRwc+9bJqNnPOIWinGgBCRSspYXfCNukWeW57/TO7Fl9UssaHiCcGCHdWN1A4noMY+fPzZg==";
};
zone "." {
	 type hint;
	 file "root.hints";
};
zone "0.0.127.in-addr.arpa" {
	 type master;
	 file "pz/127.0.0";
};
#zone "silvercrown.net1" {
#		type master;
#		file "pz/silvercrown.net1.zone";
#		allow-update { key "rndckey"; };
#		allow-transfer { 192.168.1/24; };
#		notify yes;
#};
#zone "silvercrown.net2" {
#		type master;
#		file "pz/silvercrown.net2.zone";
#		allow-update { key "rndckey"; };
#		allow-transfer { 192.168.2/24; };
#		notify yes;
#};
 
// Bind 9 now logs by default through syslog (except debug).
// These are the default logging rules.
logging {
	 category default { default_syslog; default_debug; };
	 category unmatched { null; };
 
channel default_syslog {
	 syslog daemon;					 // send to syslog's daemon
										 // facility
	 severity info;					 // only send priority info
										 // and higher
};
channel default_debug {
	 file "named.run";				 // write to named.run in
										 // the working directory
										 // Note: stderr is used instead
										 // of "named.run"
										 // if the server is started
										 // with the '-f' option.
	 severity dynamic;				 // log at the server's
										 // current debug level
};
channel default_stderr {
	 stderr;							 // writes to stderr
	 severity info;					 // only send priority info
										 // and higher
};
channel null {
	 null;								// toss anything sent to
										 // this channel
};
};

I commented out those two zones because it wasn't resolving names properly...

Primary network is 192.168.1.XXX
Callcenter network is 192.168.2.XXX

it seems to have picked up the callcenter network....

daemon.log shows entries like

Code:

Nov 2 13:53:22 lamp1 named[4011]: listening on IPv4 interface eth0, 192.168.1.3#53
Nov 2 13:53:22 lamp1 named[4011]: listening on IPv4 interface eth1, 192.168.2.249#53
Nov 2 13:53:22 lamp1 named[4011]: listening on IPv4 interface lo, 127.0.0.1#53
Nov 2 13:53:22 lamp1 named[4011]: command channel listening on 127.0.0.1#953
Nov 2 13:53:22 lamp1 named[4011]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1
Nov 2 13:53:22 lamp1 named[4011]: running
Nov 2 14:07:05 lamp1 named[4011]: lame server resolving 'care-knight-exc.silvercrown.net' (in 'silvercrown.net'?): 69.57.152.61#53
Nov 2 14:07:05 lamp1 named[4011]: lame server resolving 'care-knight-exc.silvercrown.net' (in 'silvercrown.net'?): 12.96.164.246#53

Also, it's running along side a windows active directory system....

Thanks

uk_viper · 3 Nov 2006 at 10:41

is this for internal use only or does this go external aswell (people connect to it from outside)

if its for internal then you wont need a dns nameserver, if your using live ip addresses in some cases you wont need it although it should not affect samba shares

check your firewall settings, if your only using iptables try

Code:

iptables --flush

should open any blocked ports, also check /etc/hosts.allow and /etc/hosts.deny as they may cause restriction

yoda · 3 Nov 2006 at 10:50

internal server only...

software firewall not installed

I want it to make it's own internal list and cache the external ones

Basically, our active directory servers are on their way out.... to the point where it's slowing me down to use them....
Since I've got a LAMP website developement server I thaught I might as well use that....