Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Well, below I posted my dns server configuration. A very basic one that works though. I use it on my own home server.
The only difference I can see is that in your zone declaration you is a dot to finalize the name. However I am not sure if that causes the problem.
Anyway, I use this config to build up more complex configurations. This way I know that the basics work and the added configurations cause the problem.
In dhcpd.conf, I didn't put the secret of the key between quotes. Maybe the quotes are part of the key now, which probably doesn't match to the key in rndc.key.
Code:
key dhcpupdate {
algorithm hmac-md5;
secret <secret>;
};
options {
directory "/etc/named";
listen-on port 53 {
10.200.55.10;
127.0.0.1;
};
recursion yes;
allow-recursion {
127.0.0.1;
10.0.0.0/8;
};
allow-query {
127.0.0.1;
10.0.0.0/8;
};
};
zone "hulshoff.home" {
type master;
file "/etc/named/hulshoff.home.fwd.zone";
allow-update {
key dhcpupdate;
localhost;
};
};
zone "10.in-addr.arpa" {
type master;
file "/etc/named/hulshoff.home.rev.zone";
allow-update {
key dhcpupdate;
localhost;
};
};
zone "localhost" {
type master;
file "/etc/named/localhost.fwd.zone";
allow-update {
none;
};
};
zone "0.0.127.in-addr.arpa" {
type master;
file "/etc/named/localhost.rev.zone";
allow-update {
none;
};
};
zone "." {
type hint;
file "/etc/named/db.cache";
};
Well, below I posted my dns server configuration. A very basic one that works though. I use it on my own home server.
The only difference I can see is that in your zone declaration you is a dot to finalize the name. However I am not sure if that causes the problem.
Anyway, I use this config to build up more complex configurations. This way I know that the basics work and the added configurations cause the problem.
In dhcpd.conf, I didn't put the secret of the key between quotes. Maybe the quotes are part of the key now, which probably doesn't match to the key in rndc.key.
I don't know what the issue can be. I must be overlooking something in your config.
Your computers get a dhcp lease and your able to lookup systems with a static ipaddress (if you have defined them in your zone files) with nslookup?
I don't know what the issue can be. I must be overlooking something in your config.
Your computers get a dhcp lease and your able to lookup systems with a static ipaddress (if you have defined them in your zone files) with nslookup?
This is a small system, there is only one static ip computer, the DHCP/DNS server.
All the others get their IP assign by DHCP and they can ping each other by IP.
This is a nslookup run at the client: "nslookup engarde"
Code:
*** Can't find server name for address 192.168.1.75: Non-existent domain
*** Can't find server name for address 10.4.0.6: No response from server
*** Default servers are not available
Server: UnKnown
Address: 192.168.1.75
Name: engarde.engnet.com
Address: 192.168.1.75
I can ping engarde.engnet.com and engarde by name.
Before all this changes I could ping by name internet addresses, but now I can't.
Jose
This probably has to do with resolv.conf. You have to add your ISP's nameservers. Your DNS server needs to know where the DNS servers of the internet are.
The message regarding to non-existent domain could be, because the zone files are not correct. Can you post the zone files of the A and PTR records?
This probably has to do with resolv.conf. You have to add your ISP's nameservers. Your DNS server needs to know where the DNS servers of the internet are.
The message regarding to non-existent domain could be, because the zone files are not correct. Can you post the zone files of the A and PTR records?
[root@engarde master]# cat db.engnet.com.
Code:
$ORIGIN .
$TTL 86400 ; 1 day
engnet.com IN SOA engarde.engnet.com. administrator.conecodepr.com. (
2010030205 ; serial
43200 ; refresh (12 hours)
3600 ; retry (1 hour)
3600 ; expire (1 hour)
604800 ; minimum (1 week)
)
NS engarde.engnet.com.
$ORIGIN engnet.com.
engarde A 192.168.1.75
$TTL 1200 ; 20 minutes
proplus-demo A 192.168.1.155
[root@engarde master]# cat /etc/resolv.conf
Code:
search engnet.com
nameserver 192.168.1.75
Since I have forwarders that resolve internet addresses:
Code:
options {
# This was added for security purposes under BIND 9.
version "None of your business.";
directory "/var/named";
dump-file "/var/tmp/named_dump.db"; // _PATH_DUMPFILE
pid-file "/var/run/named.pid"; // _PATH_PIDFILE
statistics-file "/var/tmp/named.stats"; // _PATH_STATS
memstatistics-file "/var/tmp/named.memstats"; // _PATH_MEMSTATS
check-names master warn;
check-names slave warn;
check-names response warn;
notify yes;
datasize 20M;
allow-transfer {
any;
};
allow-query {
any;
};
forward only;
listen-on {
192.168.1.75;
};
forwarders {
192.168.0.80;
192.168.0.20;
192.168.0.1;
};
};
If I add to the named.conf the controls directive:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.