Basically, you run a DNS server on the public VLAN with both entries
for public and metadata IPs. For instance, according to "Apple
Training Series Xsan 2 Administration: A Guide to Designing,
Deploying, and Maintaining Xsan" by Robert Kite Ph.D., pages 67
"When creating DNS entries for the devices on the SAN, you must also
create a DNS entry
for each client’s private metadata interface. In the following image,
for example, the public
interface of the metadata controller mdc1.pretendco.san is
172.16.10.1, while the private
metadata interface of the metadata controller mdc1-
private.pretendco.san is 192.168.1.1. "
There is no need to run a DNS server on metadata VLAN and have DNS
servers listed in Ethernet port settings for metadata.
On Nov 4, 2009, at 3:27 AM, Fabien COMBERNOUS wrote:
David S. Long wrote:
Do you have DNS (forward and reverse entries) configured for your
MDCs? If not, that is likely the problem.
I have dns configured for mdc on the data network, but not on the
metadata network. Is it necessary to configure a dns on metadata
network ?
--
*Fabien COMBERNOUS*
/unix system engineer/
www.kezia.com <http://www.kezia.com/>
*Tel: +33 (0) 467 992 986*
Kezia Group
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xsan-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/xsan-users/email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xsan-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xsan-users/email@hidden
