|
General software and network General OS-independent software and network questions, X11, MTA, routing, etc. |
|
Thread Tools | Display Modes |
|
|||
DNS problem- name server record
System: FreeBSD 7.0-RELEASE
I'm using BIND from the base system and I'm having a problem, first here is the relevant entry from named.conf: Code:
zone "wes.internal" { type master; file "master/wes.internal"; }; zone "1.168.192.in-addr.arpa" { type master; file "master/1.168.192.in-addr.arpa"; Code:
$TTL 1h @ IN SOA starburst.wes.internal. hostmaster.wes.internal. ( 20080707 ; Serial 1d ; Refresh 2h ; Retry 1000h ; Expire 2d ; Minimum ) IN NS starburst.wes.internal. localhost IN A 127.0.0.1 starburst IN A 192.168.1.1 Code:
$TTL 1h @ IN SOA starburst.wes.internal. hostmaster.wes.internal. ( 20080707 ; Serial 1d ; Refresh 2h ; Retry 1000h ; Expire 2d ; Minimum ) IN NS starburst.wes.internal. 1 IN PTR starburst.wes.internal. Code:
starburst named[752]: zone 1.168.192.in-addr.arpa/IN: has no NS records starburst named[752]: zone wes.internal/IN: has no NS records |
|
|||
You haven't defined the A record for the nameserver
Code:
IN NS starburst.wes.internal. EDIT: See http://daemonforums.org/showpost.php?p=3927&postcount=9 for an example.
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump |
|
|||
I thought I defined the A record with the following:
Code:
starburst IN A 192.168.1.1 |
|
|||
Anyone?
I've looked at the handbook and the DNS chapter in 'Absolute FreeBSD' 2nd Ed. and I can't see what I've done wrong. |
|
|||
You defined an A record for the wes.internal zone, but you haven't defined the A record for your reverse zone.
That is what named is complaining about Code:
tarburst named[752]: zone 1.168.192.in-addr.arpa/IN: has no NS records
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump |
|
|||
Thanks for getting back to me, I still don't quite understand though; I thought A records were for forward zones only and the equivalent PTR records for reverse zones. Also, if you look at the named error message it isn't just complaining about the reverse zone, it does about the forward one too.
However, I seem to have fixed the problem by adding the zone name to the NS entries in both my forward and reverse zone files: Forward zone file Code:
wes.internal. IN NS starburst.wes.internal. Code:
1.168.192.in-addr.arpa. IN NS starburst.wes.internal. |
|
|||
Yes, you are right. There shouldn't be A records in the reverse zone. I have been using tinydns from Daniel Bernstein for years and there you only have a singe file for all zones. I probably should stop answering BIND questions
On OpenBSD with BIND 9.3.4 the following named.conf works Code:
zone "wes.internal" { type master; file "master/wes.internal" ; }; zone "1.168.192.in-addr.arpa" { type master; file "master/1.168.192.in-addr.arpa"; }; Code:
$TTL 1h @ IN SOA ns.starburst.wes.internal. hostmaster.wes.internal. ( 20080707 ; Serial 1d ; Refresh 2h ; Retry 1000h ; Expire 2d ; Minimum ) IN NS ns.wes.internal. ns IN A 192.168.1.1 starburst IN A 192.168.1.1 supernova IN A 192.168.1.2 The file "master/1.168.192.in-addr.arpa": Code:
$TTL 1h @ IN SOA ns.wes.internal. shostmaster.wes.internal. ( 20080707 ; Serial 1d ; Refresh 2h ; Retry 1000h ; Expire 2d ; Minimum ) IN NS ns.wes.internal. 1 IN PTR starburst.wes.internal. 2 IN PTR supernova.wes.internal. Code:
$ dig +norecurse -t ns wes.internal @127.0.0.1 ; <<>> DiG 9.3.4 <<>> +norecurse -t ns wes.internal @127.0.0.1 ; (1 server found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47311 ;; flags: qr aa ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; QUESTION SECTION: ;wes.internal. IN NS ;; ANSWER SECTION: wes.internal. 3600 IN NS ns.wes.internal. ;; ADDITIONAL SECTION: ns.wes.internal. 3600 IN A 192.168.1.1 ;; Query time: 2 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Tue Jun 10 02:48:54 2008 ;; MSG SIZE rcvd: 63 Code:
dig -t ns 1.168.192.in-addr.arpa @127.0.0.1 ; <<>> DiG 9.3.4 <<>> -t ns 1.168.192.in-addr.arpa @127.0.0.1 ; (1 server found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41557 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; QUESTION SECTION: ;1.168.192.in-addr.arpa. IN NS ;; ANSWER SECTION: 1.168.192.in-addr.arpa. 3600 IN NS ns.wes.internal. ;; ADDITIONAL SECTION: ns.wes.internal. 3600 IN A 192.168.1.1 ;; Query time: 1 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Tue Jun 10 02:55:42 2008 ;; MSG SIZE rcvd: 85 Code:
$ dig -t axfr wes.internal @127.0.0.1 ; <<>> DiG 9.3.4 <<>> -t axfr wes.internal @127.0.0.1 ; (1 server found) ;; global options: printcmd wes.internal. 3600 IN SOA ns.starburst.wes.internal. hostmaster.wes.internal. 20080707 86400 7200 3600000 172800 wes.internal. 3600 IN NS ns.wes.internal. ns.wes.internal. 3600 IN A 192.168.1.1 starburst.wes.internal. 3600 IN A 192.168.1.1 supernova.wes.internal. 3600 IN A 192.168.1.2 wes.internal. 3600 IN SOA ns.starburst.wes.internal. hostmaster.wes.internal. 20080707 86400 7200 3600000 172800 ;; Query time: 1 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Tue Jun 10 03:02:06 2008 ;; XFR size: 6 records (messages 1)
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump |
|
|||
Hello again, this is very odd...
I copied your zone file examples into mine and they worked fine. I then edited my zone files back to how they were when I was having the problem- and it now works!! Here are the current contents of my zone files: Forward zone: Code:
$TTL 1h @ IN SOA starburst.wes.internal. hostmaster.wes.internal. ( 20080707 ; Serial 1d ; Refresh 2h ; Retry 1000h ; Expire 2d ; Minimum ) IN NS starburst.wes.internal. starburst IN A 192.168.1.1 Code:
$TTL 1h @ IN SOA starburst.wes.internal. shostmaster.wes.internal. ( 20080707 ; Serial 1d ; Refresh 2h ; Retry 1000h ; Expire 2d ; Minimum ) IN NS starburst.wes.internal. 1 IN PTR starburst.wes.internal. |
|
|||
Quote:
You could have entered some control character by accident. Next time you have a similar issue you can use cat -e to check for for the human eye invisible weird characters.
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump |
|
|||
Thanks, thats useful to know, in fact I still have the old problem zone files so I'll run that command on them to see if it comes up with anything.
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Boot problem. Geometry problem? | gulanito | FreeBSD Installation and Upgrading | 0 | 3rd July 2009 03:03 AM |
Lost FreeBSD boot record (when installing Ubuntu) | TomAmundsen | FreeBSD General | 6 | 19th January 2009 09:41 PM |
Sun Java System Web Server - Active Server Pages (yes ASP) | hopla | FreeBSD General | 0 | 26th September 2008 08:22 AM |