Date: Mon, 11 Oct 2004 23:42:20 +0930 From: Adam <leahya@internode.on.net> To: <freebsd-current@freebsd.org> Subject: BIND9 DNS problem Message-ID: <BD90CADC.2AE%leahya@internode.on.net>
next in thread | raw e-mail | index | archive | help
Hey guys,
I am a ammeture user of FreeBSD, and recently have had to do a fresh
install, I chose to install the 5.3-BETA7 release, as seen in this uname -a;
FreeBSD lush 5.3-BETA7 FreeBSD 5.3-BETA7 #0: Sat Oct 2 21:01:00 UTC 2004
root@wv1u.samsco.home:/usr/obj/usr/src/sys/GENERIC i386
I encountered no problems until it came to installing DNS, which happened to
be BIND9, I have no experience in bind9 but attempted to give it a go, with
what documentation I had. I figured out how to implement a key, and have
done that successfully, I then went about setting up named.conf and my zone
files (forward and reverse).
When I try and query the machine from both it's external and internal IP, I
get no response for that zone what so ever, however when I attempt to query
the machine using localhost/loopback I get a proper answer.
Does anybody have a solution to this problem? It seems quite odd.
Below are my named.conf (well a section of) and forward zone file
Both these files differ very little if any, from previous working versions
in BIND8
Help would be much appreciated
Start of named.conf
*/
* use a pseudo-random unprivileged UDP port by default.
*/
// query-source address * port 53;
};
// If you enable a local name server, don't forget to enter 127.0.0.1
// first in your /etc/resolv.conf so this server will be queried.
// Also, make sure to enable it in /etc/rc.conf.
zone "." {
type hint;
file "named.root";
};
zone "0.0.127.IN-ADDR.ARPA" {
type master;
file "master/localhost.rev";
};
// RFC 3152
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" {
type master;
file "master/localhost-v6.rev";
};
// RFC 1886 -- deprecated
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.INT" {
type master;
file "master/localhost-v6.rev";
};
// NB: Do not use the IP addresses below, they are faked, and only
// serve demonstration/documentation purposes!
//
// Example slave zone config entries. It can be convenient to become
// a slave at least for the zone your own domain is in. Ask
// your network administrator for the IP address of the responsible
// primary.
//
// Never forget to include the reverse lookup (IN-ADDR.ARPA) zone!
// (This is named after the first bytes of the IP address, in reverse
// order, with ".IN-ADDR.ARPA" appended.)
//
// Before starting to set up a primary zone, make sure you fully
// understand how DNS and BIND works. There are sometimes
// non-obvious pitfalls. Setting up a slave zone is simpler.
//
// NB: Don't blindly enable the examples below. :-) Use actual names
// and addresses instead.
key "rndc-key" {
algorithm hmac-md5;
secret "qXvnhRHiFR2EeaYamNk6Tw==";
};
controls {
inet 127.0.0.1 port 953
allow { 127.0.0.1; } keys { "rndc-key"; };
};
zone "superslag.net" {
type master;
file "master/superslag-net";
};
zone "0.0.10.in-addr.arpa" {
type master;
file "master/superslag-net-rev";
};
/*
End of named.conf
Start of zone file
*/
$TTL 86400
@ IN SOA lush-ns1.bugman.cx. lush.superslag.net. (
2004101103 ; Serial
7200 ; Refresh
1800 ; Retry
2592000 ; Expire
86400) ; TTL
;
; Name Servers
;
IN NS lush-ns1.bugman.cx.
IN NS lush-ns2.bugman.cx.
;
; Well known services
;
localhost IN A 127.0.0.1
@ IN MX 10 mail
www IN A 150.101.14.5
mail IN A 150.101.14.5
lush IN A 150.101.14.5
webmail IN A 150.101.14.5
/*
End of Zone file
Thanks Guys
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BD90CADC.2AE%leahya>