Lookup of netapp failed with DNS server xxx: Input/output error.

[#1]

I see this error in my filer logs every 3 hours.

DNs is enabled

DNS server are correct

Domain is correct

dynaic updates are enabled

any input would be greatly apprecited.

DNS is enabled

DNS caching is enabled

58 cache hits
45 cache misses
2 cache entries
40 expired entries
40 cache replacements

IP Address                                     State   Last Polled                  Avg RTT Calls  Errs
-------------------------------------------------------------------------------------------------------------
xxx.xxx.xxx                                   UP      Thu May 24 16:34:14 SAST 201      22    46     0
xxx.xxx.xxx                                NO INFO                                    0     0     0

Default domain: xxx.org

Search domains: xxx.org

option dns:

dns.cache.enable             on         (value might be overwritten in takeover)

dns.domainname               xxx.org (value might be overwritten in takeover)

dns.enable                   on         (value might be overwritten in takeover)

dns.update.enable            on         (value might be overwritten in takeover)

dns.update.ttl               10m        (value might be overwritten in takeover)

resolv.conf:

#Regenerated by registry Thu May 24 11:04:29 GMT 2012

#Auto-generated by setup Wed Jan 26 08:07:40 GMT 2011

nameserver xxx.xxx.xxx

nameserver xxx.xxx.xxx

search xxx.org

using ISCSi and CIFS

[#2]

I guess it would help if you posted some info (anonymized as necessary).

Out from filer(s) CLI:

'dns info' .

'options dns'

and the contents from /etc/resolv.conf from the root volume (normally vol0) from your filer(s).

Which NAS protocols are you running?

[#3]

DNS is enabled

DNS caching is enabled

58 cache hits
45 cache misses
2 cache entries
40 expired entries
40 cache replacements

IP Address                                     State   Last Polled                  Avg RTT Calls  Errs
-------------------------------------------------------------------------------------------------------------
xxx.xxx.xxx                                   UP      Thu May 24 16:34:14 SAST 201      22    46     0
xxx.xxx.xxx                                NO INFO                                    0     0     0

Default domain: xxx.org

Search domains: xxx.org

option dns:

dns.cache.enable             on         (value might be overwritten in takeover)

dns.domainname               xxx.org (value might be overwritten in takeover)

dns.enable                   on         (value might be overwritten in takeover)

dns.update.enable            on         (value might be overwritten in takeover)

dns.update.ttl               10m        (value might be overwritten in takeover)

resolv.conf:

#Regenerated by registry Thu May 24 11:04:29 GMT 2012

#Auto-generated by setup Wed Jan 26 08:07:40 GMT 2011

nameserver xxx.xxx.xxx

nameserver xxx.xxx.xxx

search xxx.org

using ISCSi and CIFS

[#4]

Hi,

Unfortunately the original post got munged here and the error message is longer visible, nor do I remember it at the moment.  The setup looks ok, but I don't think you really need the "dns.update" options on. You do have a relatively high rate of errors v. calls listed in dns info output.  Since you masked all of the IP output, it is a little difficult to see where the DNS servers are in relation to your filers.  You may have bad connections, firewalls, etc, disrupting your dns lookups.  You might also want to check the logs on your DNS/DC machines to look for errors.  If the secondary server is always "DOWN", you may have connection problems there as well.

Can't say much more at the moment since the original error message seems to be gone.

[#5]

Hi ,

Is someone still watching this post i have same kinda error in my environment can anybody help me on this.

Thanks,

Nayab

[#6]

HI @all

I have the same issue at customer site.

Is it possible that the DNS Server must accept unsecure dynamic dns updates ?

Thanks

Andre

[#7]

I had one head in a cluster not giving the error while the other one was and the only difference was the one with the error had secure Dynamic DNS update turned on while the other had dynamic dns turned off.  I turned it off and it appears that the error has gone away.

[#8]

Storage ip is not ping but i am able to login by RML . network team is saying no issue from network team. in this situations what can i do , Please help me this is dns info output DNS is enabled DNS caching is enabled 18133 cache hits 40473 cache misses 56 cache entries 40367 expired entries 17673 cache replacements IP Address State Last Polled Avg RTT Calls Errs ------------------------------------------------------------------------------------------------------------- 10.254.250.1 DOWN Mon Jan 2 12:57:57 CET 2017 48 3176821 3157934 10.254.250.2 DOWN Mon Jan 2 12:58:05 CET 2017 42 3158003 3157875 Default domain: de.alpha.local Search domains: de.alpha.local alpha.local ifconfig -a e0a: flags=0xaf08867<broadcast,running,multicast,tcpcksum> mtu 1500 ether 02:a0:98:2c:00:d1 (auto-1000t-fd-up) flowcontrol full trunked vif1 e0b: flags=0xaf08867<broadcast,running,multicast,tcpcksum> mtu 1500 ether 02:a0:98:2c:00:d1 (auto-1000t-fd-up) flowcontrol full trunked vif1 e0c: flags=0x2708866<broadcast,running,multicast,tcpcksum> mtu 1500 ether 00:a0:98:2c:00:cf (auto-unknown-down) flowcontrol full e0d: flags=0x2708866<broadcast,running,multicast,tcpcksum> mtu 1500 ether 00:a0:98:2c:00:ce (auto-unknown-down) flowcontrol full e0P: flags=0x2348867<up,broadcast,running,multicast,tcpcksum,acp_port> mtu 1500 PRIVATE inet 192.168.2.232 netmask 0xfffffc00 broadcast 192.168.3.255 noddns ether 00:a0:98:2c:00:cc (auto-unknown-down) flowcontrol full lo: flags=0x1b48049<up,loopback,running,multicast,tcpcksum> mtu 8160 inet 127.0.0.1 netmask 0xff000000 broadcast 127.0.0.1 ether 00:00:00:00:00:00 (VIA Provider) losk: flags=0x40a400c9<up,loopback,running> mtu 9188 inet 127.0.20.1 netmask 0xff000000 broadcast 127.0.20.1 vif1: flags=0x22f48863<up,broadcast,running,multicast,tcpcksum> mtu 1500 inet 10.34.0.207 netmask 0xfffffe00 broadcast 10.34.1.255 partner vif1 (not in use) ether 02:a0:98:2c:00:d1 (Enabled interface groups) nfo enabled ping 10.34.0.207 10.34.0.207 is alive