Anyone else figure out the heck to resolve this?
08:56:23 CDT [ratbert: rshd_0]: DNS server for domain "wcg.net" not responding : Connection timed out.
MY blinkin DNS servers are working just fine...all of 30,000 miles of fiber hardware, routers, and customers have no problems with it either.
Why only the NetApp, and a reboot isnt an option.
On Wed, 28 Apr 1999, Mohler, Jeff wrote:
Anyone else figure out the heck to resolve this?
08:56:23 CDT [ratbert: rshd_0]: DNS server for domain "wcg.net" not responding : Connection timed out.
MY blinkin DNS servers are working just fine...all of 30,000 miles of fiber hardware, routers, and customers have no problems with it either.
Why only the NetApp, and a reboot isnt an option.
I've seen (and grumbled) about this a couple of times before.
In our case I *think* the problem may be because we have some /26 subnets where we were not authoritative for the reverse mappings; that was being done by our campus networking folk. So when our ATM connection to the rest of the campus melted down we couldn't reach their nameservers and that may have been why we started getting those messages. A workaround was to add 'hosts: files dns' to /etc/nsswitch.conf and put all our local hosts in /etc/hosts. That's not a good solution, since it's easy to get the hosts data and your DNS data out of sync...
But without any netapp-side DNS debugging tools (AFAIK) it's hard to know exactly what the problem is.
But without any netapp-side DNS debugging tools (AFAIK) it's hard to know exactly what the problem is.
For what sort of tools are you looking? An RFE (15458) has been filed, but it contains only your mail message, no further details.
I've improved the error messages for the NetCache 3.3.1 and the ONTAP 5.3 release, to give more details (and to shut up about DNS servers not in the appliance's domain - for a NetCache box, reporting *all* failed DNS lookups really fills the log file up with gunk, given that the chances that at least one DNS server out there on the Big Wide Internet is down are pretty good; if you want the option to report about "foreign" DNS server, let us know, so we can add that as an option).
On Wed, 28 Apr 1999, Jim Davis wrote:
Is nslookup a possibility? That (and perhaps traceroute) would complement the ping and netstat commands pretty nicely.
And if your on a quest to bloat the software some more, could you look into ypcat and ypmatch. I'm having trouble generating any output with these commands using 5.2.1P2.
Tom
hrm. ypmatch doesn't seem to work properly for me, but ypcat works just fine on 5.1.2 (note these both require rc_toggle_basic). 5.2.1 boxes aren't up right now to check them..
Of course there's the issue of the evil surrounding filer NIS dependencies, but I digress..
..kg..
On Wed, 28 Apr 1999 tkaczma@gryf.net wrote:
And if your on a quest to bloat the software some more, could you look into ypcat and ypmatch. I'm having trouble generating any output with these commands using 5.2.1P2.
Tom
-
guy＠netapp.com -
Jim Davis -
kg -
Mohler, Jeff -
tkaczma＠gryf.net