New on LowEndTalk? Please Register and read our Community Rules.
Help setting up Bind9, what am I doing wrong?
Hi Guys,
What am I doing wrong here? I've always used a 3rd party DNS service, however seeing as I have a packet of domains I would like to learn to put them on my own DNS. I have the following setup:
Webserver
DNS Server1
DNS Server2
Any pointers as to where i'm screwing up would be great, I have included the files from ukdns below:
named.conf
// This is the primary configuration file for the BIND DNS server named.
//
// Please read /usr/share/doc/bind9/README.Debian.gz for information on the
// structure of BIND configuration files in Debian, *BEFORE* you customize
// this configuration file.
//
// If you are just adding zones, please do that in /etc/bind/named.conf.local
include "/etc/bind/named.conf.options";
include "/etc/bind/named.conf.local";
include "/etc/bind/named.conf.default-zones";
zone "windcube.tv" { type master; file "/etc/bind/zones/windcube/windcube.tv.db"; };
windcube.tv.db
$TTL 100
IN SOA ukdns.windcube.info. hostmaster.windcube.tv. (
2012010102
14400
3600
1209600
86400 )
windcube.tv. 14400 IN NS us1dns.windcube.info.
windcube.tv. 14400 IN NS ukdns.windcube.info.
localhost 14400 IN A 127.0.0.1
windcube.tv. 14400 IN A 209.141.47.204
www 14400 IN A 209.141.47.204
resolve.conf
search windcube.info nameserver 195.49.147.84
Comments
did you try checking with intodns.com?
Err.. what problem did you encounter with BIND, actually?
giving out your detailed config value without telling what your problem is, won't help as much.
Sorry if I missed something.
You shouldn't need this
search windcube.tv
search
Search list for host-name lookup.
The search list is normally determined from the local domain name; by default, it contains only the local domain name. This may be changed by listing the desired domain search path following the search keyword with spaces or tabs separating the names. Resolver queries having fewer than ndots dots (default is 1) in them will be attempted using each component of the search path in turn until a match is found. For environments with multiple subdomains please read options ndots:n below to avoid man-in-the-middle attacks and unnecessary traffic for the root-dns-servers. Note that this process may be slow and will generate a lot of network traffic if the servers for the listed domains are not local, and that queries will time out if no server is available for one of the domains.
The search list is currently limited to six domains with a total of 256 characters.
A Record needed to be added for the DNS servers.
Then it was a file permissions error on the zones.
/goes off now to read how to lock down where the queries can be called from
Carry on, as you were..... ignore the idiot in the room.
// crawls back blushingly
I can't believe I stayed up until almost 9am to track down a permission problem :P
Just for asthetics really: you shouldn't need an entry for localhost IN A 127.0.0.1; this may (should) already be handled by /etc/hosts