Am 15.02.2014 22:37, schrieb SW:
> Yes, you are correct. That is the cause of the problem. A quick entry of my
> machine in the hosts file sorted that one out!
>
> I'm just baffled why I have never experienced this issue before
because you did not care about network details
if your used nameserver would be sane you would not
get timeouts instead of a clear NXDOMAIN
[root@srv-rhsoft:~]$ host 192.168.0.10
Host 10.0.168.192.in-addr.arpa. not found: 3(NXDOMAIN)
your timeout looks like your DNS is trying to reslove the
PTR for a private address with your forwarder or asking
the root servers instead response NXDOMAIN
a sane nameserver has these adresses registered
_____________________________________________________________________
[root@srv-rhsoft:~]$ cat /var/named/chroot/var/named/named.empty
$TTL 86400
@ IN SOA localhost. root.localhost. (
2 ; Serial
3600 ; Refresh
3600 ; Retry
3628800 ; Expire
3600 ; negativer TTL-Cache
);
IN NS localhost.
_____________________________________________________________________
zone "1.10.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "2.10.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "3.10.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "4.10.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "5.10.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "6.10.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "7.10.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "8.10.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "9.10.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "16.172.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "17.172.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "18.172.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "19.172.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "20.172.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "21.172.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "22.172.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "23.172.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "24.172.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "25.172.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "26.172.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "27.172.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "28.172.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "29.172.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "30.172.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "31.172.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "0.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "127.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "254.169.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "2.0.192.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "100.51.198.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "113.0.203.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "255.255.255.255.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "3.168.192.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "4.168.192.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "5.168.192.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "6.168.192.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "7.168.192.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "8.168.192.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "9.168.192.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "10.168.192.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
