ncsd is known to cache even uncacheable DNS entries (where TTL "time to live"  = 0).  (Edit Dec 17, mark link as wrong:) For the full, sad story (from 2002 until today) see: 151929 – DNS: TTL (time-to-live) support in DNS cache  You can disable DNS caching in /etc/nsswitch.conf (remove "cache" from the "hosts:" line): hosts:      files dns  or lower the cache interval in /etc/nscd.conf from the default of 3600 seconds, e.g.:  Cheers  -- Peter
Hi There,  I have registered the Isilon cluster into the DNS and made the necessary delegation entries.The issue here is, when I ping any of the SmartConnect zones from a Windows host registered to the DNS, I get  a response from different nodes in the Pool like below : =====================WINDOWS===================================== C:\Users\Administrator>ping nfs.ep.petronas.com.my Pinging nfs.ep.petronas.com.my [10.1.15.223] with 32 bytes of data:Reply from 10.1.15.223: bytes=32 time<1ms TTL=64Reply from 10.1.15.223: bytes=32 time<1ms TTL=64Reply from 10.1.15.223: bytes=32 time<1ms TTL=64Reply from 10.1.15.223: bytes=32 time<1ms TTL=64 Ping statistics for 10.1.15.223:    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:    Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\Users\Administrator>ping nfs.ep.petronas.com.my Pinging nfs.ep.petronas.com.my [10.1.15.222] with 32 bytes of data:Reply from 10.1.15.222: bytes=32 time<1ms TTL=64Reply from 10.1.15.222: bytes=32 time<1ms TTL=64Reply from 10.1.15.222: bytes=32 time<1ms TTL=64Reply from 10.1.15.222: bytes=32 time<1ms TTL=64 Ping statistics for 10.1.15.222:    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:    Minimum = 0ms, Maximum = 0ms, Average = 0ms  However, when I do the same from a Linux Host. I get a response form same node everytime i perform a ping like below;  =====================LINUX======================================= --- nfs.ep.petronas.com.my ping statistics ---3 packets transmitted, 3 received, 0% packet loss, time 2002msrtt min/avg/max/mdev = 0.159/0.169/0.177/0.013 ms[root[NAME]-PSD-REP06 /]# ping nfs.ep.petronas.com.myPING nfs.ep.petronas.com.my (10.1.15.221) 56(84) bytes of data.64 bytes from 10.1.15.221: icmp_seq=1 ttl=64 time=0.162 ms64 bytes from 10.1.15.221: icmp_seq=2 ttl=64 time=0.183 ms64 bytes from 10.1.15.221: icmp_seq=3 ttl=64 time=0.195 ms --- nfs.ep.petronas.com.my ping statistics ---3 packets transmitted, 3 received, 0% packet loss, time 2001msrtt min/avg/max/mdev = 0.162/0.180/0.195/0.013 ms[root[NAME]-PSD-REP06 /]# ping nfs.ep.petronas.com.myPING nfs.ep.petronas.com.my (10.1.15.221) 56(84) bytes of data.64 bytes from 10.1.15.221: icmp_seq=1 ttl=64 time=0.156 ms64 bytes from 10.1.15.221: icmp_seq=2 ttl=64 time=0.181 ms64 bytes from 10.1.15.221: icmp_seq=3 ttl=64 time=0.190 ms64 bytes from 10.1.15.221: icmp_seq=4 ttl=64 time=0.177 ms64 bytes from 10.1.15.221: icmp_seq=5 ttl=64 time=0.171 ms  Is  there a particular reason for this behaviour ? This Unix host has already been registred to the DNS host and the /etc/resolve.conf file updated. I also had observed that, when I perform a nslookup lookup of the smartconnect zone, I am returned with IPs of different nodes within the pool. Please help me out here, I really have no idea what the issue is. Is this the normal behaviour of Linux machine? The host is running on RedHat 5.8  My worry here is, if I were to mount 10 nfs shares here, all the NFS shares will be mouted to only one node. Please advise. Thankjs
SmartConnect only resolves to one node