Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
$TTL 3D
@ IN SOA bamod-aish.Torah-disciple.local. (
20090212; serial, todays date + todays serial #
8H ; refresh, seconds
2H ; retry, seconds
4W ; expire, seconds
1D ) ; minimum, seconds
;
bamod-aish IN A 192.168.7.1
netgear IN A 192.168.7.2
db.7.168.192
Code:
$TTL 3D
@ IN SOA bamod-aish.Torah-disciple.local.
20090212; serial, todays date + todays serial #
8H ; refresh, seconds
2H ; retry, seconds
4W ; expire, seconds
1D ; minimum, seconds
;
1 IN PTR bamod-aish.Torah-disciple.local.
2 IN PTR netgear.Torah-disciple.local.
I am getting a couple of errers on boot that I am including for completeness not because I think they are related. At some point I need to address them but dns is the issue at this time.
Code:
INIT: Entering runlevel: 2
Starting enhanced syslogd: rsyslogdchown: invalid group: 'root:adm"
.
.
.
Starting MTA:2009-02-15 03:41:51 Exim configuration errer in line 171 of /var/lib/exim4/config.autogererated.tmp: user uucp was not found
Invalid new configfile /var/lib/exim4/config.autogenerated
.
.
Stopping boot logger: bootlogd.
chgrp: invalid group: 'adm'
Once again thanks for helping me with this. One thing is for sure I am getting better with the command line this way.
Distribution: OpenBSD 4.5-beta, OS X 10.5.6, CentOS 4 & 5
Posts: 3,631
Thanked: 14
Where you should put your zone files depends what directory BIND is starting from. You could also use the fully-qualified path to the file in your config so there's no ambiguity. As for '8H' not being a valid number, the SOA values were typically listed in seconds. I believe recent versions of BIND will convert "friendly" syntax into seconds automatically, but perhaps your BIND is not that recent. Try converting all those values into their equivalent in seconds. Also, in your 7.168.192 zone file you forgot the () around the SOA values.
I'm out for a couple of hours, but you should be able to make progress by checking the syslog file (so weird, most systems use /var/log/messages or /var/log/daemon for named messages).
I guess I am flunking dns101. Syslog is reporting that there is some kind of error in the db. files at or near this line
Code:
86400 ) ; minimum, seconds
But I can't find it. I have compared it to the unchanged files that were installed in /etc/bind and I can't see any difference except the data involved.
My current files are exactly like the ones posted except that the time values have been changed to second values and the () have been inserted in there proper places. What am I missing? I guess maybe I need to step back and focus on something else for awhile.
Thanks for all the help. I have gotten farther this time than I did the last time I tried to setup dns.
Distribution: OpenBSD 4.5-beta, OS X 10.5.6, CentOS 4 & 5
Posts: 3,631
Thanked: 14
For one thing, stop trying to abbreviate the output of the files you're posting. Unless there are encryption keys or passwords in a file, there's no reason to withhold the contents. While you might think the rest of the file in inconsequential, it could actually have important information that you didn't realize was relevant.
Please post the entire named.conf (er, named.conf.local I guess), as well as the two zone files again with the most current information. If you post the entire file it's a lot easier to debug than guessing what might be wrong with the bits of the files you left out.
PS Also post the full output of named events in syslog, not just a brief snippet with your interpretation of what the error meant.
I have not looked at these this morning to see if a fress pair of eyes will allow me to see something I was overlooking last night.
Hear are the unedited files.
named.conf.local
Code:
//
// Do any local configuration here
//
// Consider adding the 1918 zones here, if they are not used in your
// organization
//include "/etc/bind/zones.rfc1918";
# ****** the following added per instructions ******
# allow dns updates from localhost with key "rndc-key"
#include "/etc/bind/rndc.key";
controls {
inet 127.0.0.1 allow { localhost; };
};
# defines Torah-disciple.local
zone "Torah-disciple.local" {
type master;
file "db.Torah-disciple.local";
# allow-update { key "rndc-key"; };
};
# defines our local subnet 192.168.7.0/24
zone "7.168.192.in-addr.arpa" {
type master;
notify no;
file "db.7.168.192";
# allow-update { key "rndc-key"; };
};
# end added section
db.Torah-disciple.local
Code:
;
; Zone file for Torah-disciple.local
;
; The full zone file
;
$TTL 3D
@ IN SOA bamod-aish.Torah-disciple.local. (
20090215; serial, todays date + todays serial #
28800 ; refresh, seconds
7200 ; retry, seconds
24200000 ; expire, seconds
86400 ) ; minimum, seconds
;
bamod-aish IN A 192.168.7.1
netgear IN A 192.168.7.2
DI-604 IN A 192.168.7.3
kingbee IN A 192.168.7.5
ROBIN IN A 192.168.7.6
water-logged IN A 192.168.7.7
xbox IN A 192.168.7.8
youngestbee-PC IN A 192.168.7.9
MEEEEEE IN A 192.168.7.10
distraction IN A 192.168.0.11
HP_Laserjet_4Si IN A 192.168.7.15
BRN-AAED98 IN A 192.168.7.16
HP_Laserjet_5000_Series IN A 192.168.7.17
db.7.168.192
Code:
$TTL 3D
@ IN SOA bamod-aish.Torah-disciple.local. (
20090215; serial, todays date + todays serial
22800 ; refresh, seconds
7200 ; retry, seconds
24200000 ; expire, seconds
86400 ) ; minimum, seconds
;
1 IN PTR bamod-aish.Torah-disciple.local.
2 IN PTR netgear.Torah-disciple.local.
3 IN PTR DI-604.Torah-disciple.local.
5 IN PTR kingbee.Torah-disciple.local.
6 IN PTR ROBIN.Torah-disciple.local.
7 IN PTR water-logged.Torah-disciple.local.
8 IN PTR xbox.Torah-disciple.local.
9 IN PTR youngestbee-PC.Torah-disciple.local.
10 IN PTR MEEEEEE.Torah-disciple.local.
11 IN PTR distraction.Torah-disciple.local.
15 IN PTR HP_Laserjet_4Si.Torah-disciple.local.
16 IN PTR BRN-AAED98.Torah-disciple.local.
17 IN PTR HP_Laserjet_5000_Series.Torah-disciple.local.
named lines from syslog after power-on this morning
Code:
Feb 15 22:51:34 bamod-aish named[1935]: starting BIND 9.5.0-P2 -u bind
Feb 15 22:51:34 bamod-aish named[1935]: found 1 CPU, using 1 worker thread
Feb 15 22:51:34 bamod-aish named[1935]: loading configuration from '/etc/bind/named.conf'
Feb 15 22:51:34 bamod-aish named[1935]: listening on IPv6 interfaces, port 53
Feb 15 22:51:34 bamod-aish named[1935]: listening on IPv4 interface lo, 127.0.0.1#53
Feb 15 22:51:34 bamod-aish named[1935]: listening on IPv4 interface eth1, 192.168.7.1#53
Feb 15 22:51:34 bamod-aish named[1935]: listening on IPv4 interface eth2, 192.168.3.1#53
Feb 15 22:51:35 bamod-aish named[1935]: default max-cache-size (33554432) applies
Feb 15 22:51:35 bamod-aish named[1935]: automatic empty zone: 254.169.IN-ADDR.ARPA
Feb 15 22:51:35 bamod-aish named[1935]: automatic empty zone: 2.0.192.IN-ADDR.ARPA
Feb 15 22:51:35 bamod-aish named[1935]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
Feb 15 22:51:35 bamod-aish named[1935]: automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Feb 15 22:51:35 bamod-aish named[1935]: automatic empty zone: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Feb 15 22:51:35 bamod-aish named[1935]: automatic empty zone: D.F.IP6.ARPA
Feb 15 22:51:35 bamod-aish named[1935]: automatic empty zone: 8.E.F.IP6.ARPA
Feb 15 22:51:35 bamod-aish named[1935]: automatic empty zone: 9.E.F.IP6.ARPA
Feb 15 22:51:35 bamod-aish named[1935]: automatic empty zone: A.E.F.IP6.ARPA
Feb 15 22:51:35 bamod-aish named[1935]: automatic empty zone: B.E.F.IP6.ARPA
Feb 15 22:51:35 bamod-aish named[1935]: default max-cache-size (33554432) applies: view _bind
Feb 15 22:51:35 bamod-aish named[1935]: command channel listening on 127.0.0.1#953
Feb 15 22:51:35 bamod-aish named[1935]: zone 0.in-addr.arpa/IN: loaded serial 1
Feb 15 22:51:35 bamod-aish named[1935]: zone 127.in-addr.arpa/IN: loaded serial 1
Feb 15 22:51:35 bamod-aish named[1935]: dns_rdata_fromtext: db.7.168.192:7: near eol: unexpected end of input
Feb 15 22:51:35 bamod-aish named[1935]: zone 7.168.192.in-addr.arpa/IN: loading from master file db.7.168.192 failed: unexpected end of input
Feb 15 22:51:35 bamod-aish named[1935]: zone 255.in-addr.arpa/IN: loaded serial 1
Feb 15 22:51:35 bamod-aish named[1935]: dns_rdata_fromtext: db.Torah-disciple.local:12: near eol: unexpected end of input
Feb 15 22:51:35 bamod-aish named[1935]: zone Torah-disciple.local/IN: loading from master file db.Torah-disciple.local failed: unexpected end of input
Feb 15 22:51:35 bamod-aish named[1935]: zone localhost/IN: loaded serial 2
Feb 15 22:51:35 bamod-aish named[1935]: running
Feb 15 22:51:39 bamod-aish named[1935]: received control channel command 'reconfig'
Feb 15 22:51:39 bamod-aish named[1935]: loading configuration from '/etc/bind/named.conf'
Feb 15 22:51:39 bamod-aish named[1935]: listening on IPv4 interface eth0, 192.168.1.101#53
Feb 15 22:51:39 bamod-aish named[1935]: default max-cache-size (33554432) applies
Feb 15 22:51:39 bamod-aish named[1935]: default max-cache-size (33554432) applies: view _bind
Feb 15 22:51:39 bamod-aish named[1935]: reloading configuration succeeded
Feb 15 22:51:39 bamod-aish named[1935]: dns_rdata_fromtext: db.7.168.192:7: near eol: unexpected end of input
Feb 15 22:51:39 bamod-aish named[1935]: zone 7.168.192.in-addr.arpa/IN: loading from master file db.7.168.192 failed: unexpected end of input
Feb 15 22:51:39 bamod-aish named[1935]: dns_rdata_fromtext: db.Torah-disciple.local:12: near eol: unexpected end of input
Feb 15 22:51:39 bamod-aish named[1935]: zone Torah-disciple.local/IN: loading from master file db.Torah-disciple.local failed: unexpected end of input
Feb 15 22:51:39 bamod-aish named[1935]: any newly configured zones are now loaded
Feb 15 22:51:40 bamod-aish dhcpd: Wrote 0 deleted host decls to leases file.
Feb 15 22:51:40 bamod-aish dhcpd: Wrote 0 new dynamic host decls to leases file.
Feb 15 22:51:40 bamod-aish dhcpd: Wrote 1 leases to leases file.
There it is.
I still don't see anything that looks wrong when compared to the files that were installed and are unedited.
Distribution: OpenBSD 4.5-beta, OS X 10.5.6, CentOS 4 & 5
Posts: 3,631
Thanked: 14
See, this is why I asked you to post the entire files. You have a couple more hosts with underscores '_' in their names. Change those all to dashes '-' and restart named.
I am not sure that I can change those printer names. They are set by the printers themselves. For that matter I am not even sure they are correct. A solution may be that if dhcp and dns don't care if the name they assign does not agree with the actual name of the machine, in that case I could use a different name, if not...
I will check on changing those names in the printers later when I have time, I have to change the ip's at somepoint anyway.
Distribution: OpenBSD 4.5-beta, OS X 10.5.6, CentOS 4 & 5
Posts: 3,631
Thanked: 14
You can easily test to see if that's the syntax problem. Just shut down dhcpd and comment out the underscore lines in your zone files (start the line with a semi-colon ';'), then restart named. If it starts without the errors in syslog, then you know that's your final problem.
Still getting the syntax error in the same place. I did add the line above in both zone files. I commented out the _ lines in the zone files and in the dhcp config file and shut down the dhcp server.
I compared the files with OpenOffice looking at the non-printing characters. Thought there might be one hidding there somewhere that shouldn't be, but no.
Grrrrrrr. Banging my head on the wall. Guess I'll go read the man pages.
Distribution: OpenBSD 4.5-beta, OS X 10.5.6, CentOS 4 & 5
Posts: 3,631
Thanked: 14
Try changing this:
PHP Code:
@ IN SOA bamod-aish.Torah-disciple.local. (
To this:
PHP Code:
@ IN SOA hostmaster.Torah-disciple.local. bamod-aish.Torah-disciple.local. (
I thought the e-mail address portion was optional, but perhaps it's not...
Edit: That's almost certainly it. It's an error on line 12 of your forward zone and line 7 of your reverse zone. In each case that's the end of your SOA record. It's missing a field.
Something is overwriting resolv.conf on reboot. I had my nameservers entered corectly but a reboot reset everthing and I am not sure where it is getting it from.
I think it is the settings from the plastic box router that makes up my testing network. Atleist the nameserver ip is the ip of said router.
Distribution: OpenBSD 4.5-beta, OS X 10.5.6, CentOS 4 & 5
Posts: 3,631
Thanked: 14
Quote:
Originally Posted by rbees
Cool: That fixed the syntax errors but I still get the
when I try # nslookup localhost 192.168.7.11
Don't use nslookup, it's deprecated. Use dig instead. The output is more useful for things like this:
Code:
$ dig @yournameserverip somehost
If you want to lookup a PTR record for an IP address, use the -x flag:
Code:
$ dig -x @yournameserverip someipaddress
Quote:
If I put a regular email there like nher@gmail.com is it going to send an email to that address? If so what would be in it?
No, you can't use an @ sign. Everything needs to be separated by periods. The e-mail address in the SOA is simply the address of who's responsible for running your DNS. For a home site it doesn't need to be a real e-mail address.
As for resolv.conf being overwritten, apparently you have configured your machine to get it's IP address from DHCP. Each Linux distribution has their own way to configure that, so I'll let someone else answer where that would be stored. You want to configure for a static IP.
Thanks again chort, sorry for the misspelling before.
As long as I reset everything in resolv.conf and then restart bind and dhcp nslookup is working fine (when I use the correct order) from the server. I was looking through the dhclient.conf and there are some options there that may correct the problem but I haven't been able to find any more than what it says in the config file about them. The man says nothing. It may also fix the issue I have with my linux boxes not reporting their name to the server.
No so from the client box connected to the server. If I use the ip of the server it resolves fine, but if I try with the server name it fails. Also if I inquire for the name of an ip it works but not the other way around unless I use the whole name.Torah-disciple.local. Perhaps this is normal?
I did look at resolv.conf in the client box and it contains, automatically set, the correct name servers and domain name.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.