This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C66EC0.120065F0
Content-Type: text/plain
Well our servers are backed up by IP or Client Name - looking at activity it
does not show the FQDN - but I guess it would show this in the log files
perhaps??
Regards
Simon Weaver
3rd Line Technical Support
Windows Domain Administrator
EADS Astrium Limited, B32AA IM (DCS)
Anchorage Road, Portsmouth, PO3 5PU
Email: <mailto:Simon.Weaver AT Astrium-eads DOT net> Simon.Weaver AT
Astrium-eads DOT net
-----Original Message-----
From: ckstehman AT pepco DOT com [mailto:ckstehman AT pepco DOT com]
Sent: 03 May 2006 14:43
To: David Rock
Cc: veritas-bu AT mailman.eng.auburn DOT edu;
veritas-bu-admin AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] FQDNs or Not ? [recommendations please]
Here's my two cents, I recommend using DNS all the way. We use DNS with
short names aliased to the FQDN. I do not recommend using HOST files.
They are a nightmare to administer.
=============================
Carl Stehman
Pepco Holdings, Inc.
202-331-6619
Pager 301-765-2703
ckstehman AT pepco DOT com
David Rock <dave-bu AT graniteweb DOT com>
Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu
05/02/2006 02:31 PM
Please respond to
David Rock <dave-bu AT graniteweb DOT com>
To
veritas-bu AT mailman.eng.auburn DOT edu
cc
Subject
Re: [Veritas-bu] FQDNs or Not ? [recommendations please]
* Rockey Reed <rockey_reed AT symantec DOT com> [2006-05-01 05:37]:
> > -----Original Message-----
> > From: veritas-bu-admin AT mailman.eng.auburn DOT edu
> > [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Ed
> > Wilts
> > Yes. Not just for for NetBackup, but in general, use FQDN whenever
> > possible.
> >
> In this area I cannot help but to disagree with Ed, for whom I have
> great respect. The use of FQDN is used too often to mask a poor DNS
> configuration. With NBU you need full forward and reverse lookup. When
> either is missing a short term solution would be the use of /etc/hosts
> files until your network team can fix the DNS by adding the servers IP
> address to both zones.
This sounds like an argument FOR using DNS, not against it. :-)
Don't forget, the question was about using FQDN, _not_ using DNS. Which
way you implement it doesn't really matter (although generally that DOES
mean using DNS).
Basically, using FQDN is a good idea because it creates genuinely
unique client names in NetBackup. Without this, you run a real risk of
having two client short names that are the same. You might not see this
in a single-company, single-site environment, but it is a real danger in
multi-customer or multi-site environments. How many exchange1 servers
are out there, I wonder?
Imagine in an outsourcing situation where you have to tell client B that
the name of their server will have to change because client A got there
first (exchange servers don't like having a NBU client name that is
different from their real name).
The ONLY downside I have come across when using FQDN is when you work
heavily in the CLI. It does get tiresome when typing a long FQDN on the
commandline to do a bplist or some other activity, but knowing the
clients are unique helps a lot. This can also be mitigated quite a bit
with scripting and other looping activities off of bpplclients, anyway.
--
David Rock
david AT graniteweb DOT com
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
This Email message and any attachment may contain information that is
proprietary, legally privileged, confidential and/or subject to copyright
belonging to Pepco Holdings, Inc. or its affiliates ("PHI"). This Email is
intended solely for the use of the person(s) to which it is addressed. If
you are not an intended recipient, or the employee or agent responsible for
delivery of this Email to the intended recipient(s), you are hereby notified
that any dissemination, distribution or copying of this Email is strictly
prohibited. If you have received this message in error, please immediately
notify the sender and permanently delete this Email and any copies. PHI
policies expressly prohibit employees from making defamatory or offensive
statements and infringing any copyright or any other legal right by Email
communication. PHI will not accept any liability in respect of such
communications.
This email is for the intended addressee only.
If you have received it in error then you must not use, retain, disseminate or
otherwise deal with it.
Please notify the sender by return email.
The views of the author may not necessarily constitute the views of EADS
Astrium Limited.
Nothing in this email shall bind EADS Astrium Limited in any contract or
obligation.
EADS Astrium Limited, Registered in England and Wales No. 2449259
Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
------_=_NextPart_001_01C66EC0.120065F0
Content-Type: text/html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.2900.2802" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=489224314-03052006><FONT face=Arial
color=#0000ff><STRONG><EM>Well our servers are backed up by IP or Client Name -
looking at activity it does not show the FQDN - but I guess it would show this
in the log files perhaps??</EM></STRONG></FONT></SPAN></DIV>
<DIV> </DIV>
<DIV> </DIV>
<P align=left><SPAN lang=en-gb><EM><FONT color=#3f6296><FONT size=2><FONT
face=Arial><FONT
color=#0000ff>Regards</FONT></FONT></FONT></FONT></EM></SPAN></P>
<P align=left><SPAN lang=en-gb><EM><FONT color=#3f6296><FONT size=2><FONT
face=Arial><FONT color=#0000ff>Simon
Weaver</FONT><BR></FONT></FONT></FONT><FONT
face=Arial color=#0000a0 size=2><STRONG>3rd Line Technical Support<BR>Windows
Domain Administrator</STRONG></FONT></EM><FONT face=Arial> </FONT></SPAN></P>
<P><SPAN lang=en-gb><I><FONT face=Arial color=#0000ff size=2>EADS Astrium
Limited, B32AA IM (DCS)</FONT></I></SPAN><SPAN lang=en-gb><BR><FONT face=Arial
color=#0000ff size=2><EM>Anchorage Road, Portsmouth, PO3
5PU</EM></FONT></SPAN></P>
<P><SPAN lang=en-gb><FONT face=Arial color=#0000ff size=2><EM>Email:
</EM></FONT><A href="mailto:Simon.Weaver AT Astrium-eads DOT net"><FONT
face=Arial
size=2><EM>Simon.Weaver AT Astrium-eads DOT net</EM></FONT></A></SPAN></P>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B>
ckstehman AT pepco DOT com [mailto:ckstehman AT pepco DOT com]
<BR><B>Sent:</B> 03 May 2006
14:43<BR><B>To:</B> David Rock<BR><B>Cc:</B>
veritas-bu AT mailman.eng.auburn DOT edu;
veritas-bu-admin AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> Re:
[Veritas-bu]
FQDNs or Not ? [recommendations please]<BR><BR></FONT></DIV><BR><FONT
face=sans-serif size=2>Here's my two cents, I recommend using DNS all the
way.
We use DNS with short names aliased to the FQDN. I do not
recommend using HOST files.</FONT> <BR><FONT face=sans-serif size=2>They are
a
nightmare to administer.</FONT> <BR><BR><BR><FONT face=sans-serif
size=2>=============================<BR>Carl Stehman <BR>Pepco Holdings,
Inc.<BR>202-331-6619<BR>Pager 301-765-2703<BR>ckstehman AT pepco DOT
com</FONT>
<BR><BR><BR>
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD width="40%"><FONT face=sans-serif size=1><B>David Rock
<dave-bu AT graniteweb DOT com></B> </FONT><BR><FONT
face=sans-serif
size=1>Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu</FONT>
<P><FONT face=sans-serif size=1>05/02/2006 02:31 PM</FONT>
<TABLE border=1>
<TBODY>
<TR vAlign=top>
<TD bgColor=white>
<DIV align=center><FONT face=sans-serif size=1>Please respond
to<BR>David Rock
<dave-bu AT graniteweb DOT
com></FONT></DIV></TR></TBODY></TABLE><BR></P>
<TD width="59%">
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD>
<DIV align=right><FONT face=sans-serif size=1>To</FONT></DIV>
<TD><FONT face=sans-serif
size=1>veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<TR vAlign=top>
<TD>
<DIV align=right><FONT face=sans-serif size=1>cc</FONT></DIV>
<TD>
<TR vAlign=top>
<TD>
<DIV align=right><FONT face=sans-serif size=1>Subject</FONT></DIV>
<TD><FONT face=sans-serif size=1>Re: [Veritas-bu] FQDNs or Not ?
[recommendations please]</FONT></TR></TBODY></TABLE><BR>
<TABLE>
<TBODY>
<TR vAlign=top>
<TD>
<TD></TR></TBODY></TABLE><BR></TR></TBODY></TABLE><BR><BR><BR><FONT
size=2><TT>* Rockey Reed <rockey_reed AT symantec DOT com> [2006-05-01
05:37]:<BR>> > -----Original Message-----<BR>> > From:
veritas-bu-admin AT mailman.eng.auburn DOT edu<BR>> >
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Ed
Wilts<BR>>
> Yes. Not just for for NetBackup, but in general, use FQDN
whenever<BR>> > possible.<BR>> > <BR>> In this area I
cannot help but to disagree with Ed, for whom I have<BR>> great respect.
The use of FQDN is used too often to mask a poor DNS<BR>>
configuration. With NBU you need full forward and reverse lookup.
When<BR>> either is missing a short term solution would be the use
of
/etc/hosts<BR>> files until your network team can fix the DNS by adding
the
servers IP<BR>> address to both zones.<BR><BR>This sounds like an argument
FOR using DNS, not against it. :-)<BR><BR>Don't forget, the question was
about
using FQDN, _not_ using DNS. Which<BR>way you implement it doesn't
really matter (although generally that DOES<BR>mean using
DNS).<BR><BR>Basically, using FQDN is a good idea because it creates
genuinely<BR>unique client names in NetBackup. Without this, you run a
real risk of<BR>having two client short names that are the same. You
might not see this<BR>in a single-company, single-site environment, but it is
a real danger in<BR>multi-customer or multi-site environments. How many
exchange1 servers<BR>are out there, I wonder?<BR>Imagine in an outsourcing
situation where you have to tell client B that<BR>the name of their server
will have to change because client A got there<BR>first (exchange servers
don't like having a NBU client name that is<BR>different from their real
name).<BR><BR>The ONLY downside I have come across when using FQDN is when
you
work<BR>heavily in the CLI. It does get tiresome when typing a long
FQDN
on the<BR>commandline to do a bplist or some other activity, but knowing
the<BR>clients are unique helps a lot. This can also be mitigated quite
a bit<BR>with scripting and other looping activities off of bpplclients,
anyway.<BR><BR>-- <BR>David
Rock<BR>david AT graniteweb DOT
com<BR>_______________________________________________<BR>Veritas-bu
maillist -
Veritas-bu AT mailman.eng.auburn DOT
edu<BR>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu<BR></TT></FONT><BR><BR><BR>This
Email message and any attachment may contain information that is proprietary,
legally privileged, confidential and/or subject to copyright belonging to
Pepco Holdings, Inc. or its affiliates ("PHI"). This Email is intended solely
for the use of the person(s) to which it is addressed. If you are not an
intended recipient, or the employee or agent responsible for delivery of this
Email to the intended recipient(s), you are hereby notified that any
dissemination, distribution or copying of this Email is strictly prohibited.
If you have received this message in error, please immediately notify the
sender and permanently delete this Email and any copies. PHI policies
expressly prohibit employees from making defamatory or offensive statements
and infringing any copyright or any other legal right by Email communication.
PHI will not accept any liability in respect of such communications.
</BLOCKQUOTE></BODY></HTML>
<table><tr><td bgcolor=#ffffff><font color=#000000>This email is for the
intended addressee only.<br>
If you have received it in error then you must not use, retain, disseminate or
otherwise deal with it.<br>
Please notify the sender by return email.<br>
The views of the author may not necessarily constitute the views of EADS
Astrium Limited.<br>
Nothing in this email shall bind EADS Astrium Limited in any contract or
obligation.<br>
<br>
EADS Astrium Limited, Registered in England and Wales No. 2449259<br>
Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS,
England<br>
</font></td></tr></table>
------_=_NextPart_001_01C66EC0.120065F0--
|
