Re: Slow DNS Lookup (4TH POSTING)
Sorry about the size of this....but here's my config files:
named.conf:
options {
directory "/var/cache/bind";
// If there is a firewall between you and nameservers you want
// to talk to, you might need to uncomment the query-source
// directive below. Previous versions of BIND always asked
// questions using port 53, but BIND 8.1 and later use an
unprivileged
// port by default.
// query-source address * port 53;
// forward first;
forwarders {
206.75.216.200;
206.75.216.210;
};
};
// reduce log verbosity on issues outside our control
logging {
category lame-servers { null; };
category cname { null; };
};
// prime the server with knowledge of the root servers
zone "." {
type hint;
file "/etc/bind/db.root";
};
// be authoritative for the localhost forward and reverse zones, and for
// broadcast zones as per RFC 1912
zone "0.0.127.in-addr.arpa" {
type master;
file "/etc/bind/db.127.0.0";
};
// add entries for other zones below here
zone "emergeknowledge.com" {
notify no;
type master;
file "/etc/bind/db.emerge";
};
+++++++++++++++++++++++++++++++++++++++++++++++++++
db.root file:
lists the root nameservers....not necessary to post i suppose
+++++++++++++++++++++++++++++++++++++++++++++++++++
db.emerge file:
@ IN SOA ns.emergeknowledge.com. admin.emergeknowledge.com. (
1 ; serial
8H ; refresh
2H ; retry
1W ; expire
1D) ; minimum, TTL
NS ns
MX 10 mail.emergeknowledge.com.
localhost A 127.0.0.1
ns A 64.59.157.18
MX 10 mail.emergeknowledge.com.
test A 64.59.157.18
MX 10 mail.emergeknowledge.com.
stats A 64.59.157.18
MX 10 mail.emergeknowledge.com.
mail A 64.59.157.18
MX 10 mail.emergeknowledge.com.
www CNAME ns
emergeknowledge.com. A 64.59.157.18
MX 10 mail.emergeknowledge.com.
ftp A 64.59.157.18
MX 10 mail.emergeknowledge.com.
+++++++++++++++++++++++++++++++++++++++++++++++++++
db.127.0.0 file:
$TTL 3D
@ IN SOA ns.emergeknowledge.com. admin.emergeknowledge.com. (
1 ; serial
8H ; refresh
2H ; retry
4W ; expire
1D) ; minimum ttl
NS ns.emergeknowledge.com.
1 PTR localhost.
thanks
leonard
Reply to: