TruCluster DNS slave and client

From: Goetzman, Dan (Dan_Goetzman@bmc.com)
Date: Thu Oct 03 2002 - 09:25:26 EDT

• Next message: O'Brien, Pat: "SUMMARY LONG ATTEMPT: NFS server getting "NFS3 Server servername is not responding" message"
• Previous message: William Skulley: "npasswd on Tru64 5.1?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Hello Tru64 admins,

 Running TruCluster 5.1 pk#3 for a HA fileserver. We had problems the other
day reaching our DNS server and I noticed that NFS serving was not impacted
(good), but mountd needs to talk to the DNS server and hung until the
connection to the DNS server was restored (not good).

 So, I was thinking maybe I should make the cluster a DNS slave and have it
resolve to itself. Anyone doing this, is this a good idea?

 I found a statement in the TruCluster docs that all members in the cluster
have to have the same DNS config and if the cluster is a DNS server, it
cannot be a DNS client. Is this true?

 Any help on this appreciated...

Dan Goetzman

• Next message: O'Brien, Pat: "SUMMARY LONG ATTEMPT: NFS server getting "NFS3 Server servername is not responding" message"
• Previous message: William Skulley: "npasswd on Tru64 5.1?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:55 EDT