Hi,
i am using latest stable debian on a box within my network and have installed bind9 on it. The DNS server has Zens dns servers as forwarders, and i have modified the zone file for my domain to point to my internal ip addresses.
this is the contents of my resolv.conf:
this means i can type in www.mydomain.com within the network and it correctly resolves to the internal IP rather than external (as it would using any other DNS server).
i have told bind to never update the record for my domain so presumably my internal mappings will stay:
on typing in nslookup www.google.com for example i get a response from my dns server with the ip addresses.
However this doesnt work for nslookup www.yahoo.com for some reason - the zen dns servers answer after a while (i presume mine times out?)
within a web browser of any comp on the network using that dns server yahoo.com cannot be reached half the time, however yahoo.co.uk, google.com, jolt etc work fine.
i can only presume there are other websites which it will fail to resolve, but i cant work out why some would work fine yet others struggle. it makes initially browsing to yahoo very slow.
any ideas much appreciated.
thanks
i am using latest stable debian on a box within my network and have installed bind9 on it. The DNS server has Zens dns servers as forwarders, and i have modified the zone file for my domain to point to my internal ip addresses.
this is the contents of my resolv.conf:
Code:
nameserver 127.0.0.1
nameserver 212.23.3.100
domain mydomain.comthis means i can type in www.mydomain.com within the network and it correctly resolves to the internal IP rather than external (as it would using any other DNS server).
i have told bind to never update the record for my domain so presumably my internal mappings will stay:
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";
zone "mydomain.com" {
type master;
file "/etc/bind/db.mydomain";
# allow-update {
# 192.168.2/24;
# 127/8;
# };
allow-query {
192.168.2/24;
127/8;
};
};
zone "2.168.192.in-addr.arpa" {
type master;
file "/etc/bind/db.192.168.2";
# allow-update {
# 192.168.2/24;
# 127/8;
# };
allow-query {
192.168.2/24;
127/8;
};
};on typing in nslookup www.google.com for example i get a response from my dns server with the ip addresses.
Code:
Server: 127.0.0.1
Address: 127.0.0.1#53
Non-authoritative answer:
www.google.com canonical name = www.l.google.com.
Name: www.l.google.com
Address: 64.233.161.99
Name: www.l.google.com
Address: 64.233.161.104
Name: www.l.google.com
Address: 64.233.161.147However this doesnt work for nslookup www.yahoo.com for some reason - the zen dns servers answer after a while (i presume mine times out?)
Code:
Server: 212.23.3.100
Address: 212.23.3.100#53
Non-authoritative answer:
www.yahoo.com canonical name = www.yahoo.akadns.net.
Name: www.yahoo.akadns.net
Address: 68.142.197.86
Name: www.yahoo.akadns.net
Address: 68.142.197.67
Name: www.yahoo.akadns.net
Address: 68.142.197.68
Name: www.yahoo.akadns.net
Address: 68.142.197.69
Name: www.yahoo.akadns.net
Address: 68.142.197.76
Name: www.yahoo.akadns.net
Address: 68.142.197.78
Name: www.yahoo.akadns.net
Address: 68.142.197.81
Name: www.yahoo.akadns.net
Address: 68.142.197.83within a web browser of any comp on the network using that dns server yahoo.com cannot be reached half the time, however yahoo.co.uk, google.com, jolt etc work fine.
i can only presume there are other websites which it will fail to resolve, but i cant work out why some would work fine yet others struggle. it makes initially browsing to yahoo very slow.
any ideas much appreciated.
thanks