Hello,
OS: Fedora 14, x86_64, all the last updates from default repositories installed.
Several updates ago I noticed a strange phenomenon. We are using local zones on our DNS configuration (e.g., custom TLD .local). The following illustrates the problem:
/etc/resolv.conf:
Code:
search local
nameserver 10.10.0.1
The nameserver mentioned resolves all existing names in .local TLD and forwards all the other name resolution to the provider's DNS services.
Now test.local is a valid DNS A record resolving to an address 10.10.0.222 (and a correct rDNS record exists as well). Here are the results of several commands:
$ host test
test.local has address 10.10.0.222
$ host test.local
test.local has address 10.10.0.222
$ ping test
PING test.local (10.10.0.222) 56(84) bytes of data.
64 bytes from test.local (10.10.0.222): icmp_req=1 ttl=64 time=1.59 ms
64 bytes from test.local (10.10.0.222): icmp_req=2 ttl=64 time=16.2 ms
^C
--- test.local ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 1.591/8.932/16.274/7.342 ms
$ ping test.local
ping: unknown host test.local
The problem is detected only for the host names for which there are CNAME records at nameserver's configuration referring to. I.e., there is
test1 CNAME test.local.
entry in .local zone configuration file. For host names not referred by any CNAME record, both names are resolved (with and without .local) and used fine by all the programs.
May I ask for suggestions on how to fix this? Any help would be much appreciated. Only certain intranet computers are affected by this.