That's what I get for being old school. I had an NT 4 domain that I had used underscores on years ago and had internal dns issues with our FreeBSD DNS server. I changed to dashes and never looked back. :-)
On Thu, Sep 18, 2008 at 3:27 PM, <[EMAIL PROTECTED]> wrote: > > "Jonathan Link" <[EMAIL PROTECTED]> wrote on 09/18/2008 03:25:05 PM: > > > DNS lookups. Underscores are not valid in DNS names. > > But they will work .. > > Z:\>nslookup admin_nt9 > Server: admnwdc001.wrk.ads.pha.phila.gov > Address: 10.64.7.53 > > Name: admin_nt9.wrk.ads.pha.phila.gov > Address: 10.64.13.3 > > > In Win2000 AD. This is internal only, of course. > > > > > On Thu, Sep 18, 2008 at 3:09 PM, Joe Heaton <[EMAIL PROTECTED]> wrote: > > Second question. Anyone know what could break using underscores in PC > > naming? i.e. loc_pcname > > > > Joe Heaton > > > > -----Original Message----- > > From: Phil Brutsche [mailto:[EMAIL PROTECTED] > > Sent: Thursday, September 18, 2008 11:45 AM > > To: NT System Admin Issues > > Subject: Re: new computers > > > > I've done it both ways. I usually try to have the AD objects created > > first. > > > > If you create the AD object first the machine will get the right GPOs > > right off the bat. It's less work that way, especially if you use > > software installation GPOs. The machine is 100% ready to go sooner. > > > > Joe Heaton wrote: > > > When you guys build new PCs, do you create the AD object first, or > > > simply join the domain from the PC afterwards? I've always created > > the > > > PC, then joined the domain, but our desktop guy just mentioned that > > our > > > manager wanted him to create the AD object first. My first instinct > > is > > > to say no, because then you're creating an AD object for something > > that > > > doesn't exist yet, but other than that, I didn't have a real reason. > > > Anyone have a better reason? > > > -- > > > > Phil Brutsche > > [EMAIL PROTECTED] > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > > > No virus found in this incoming message. > > Checked by AVG - http://www.avg.com > > Version: 8.0.169 / Virus Database: 270.6.21/1678 - Release Date: > > 9/18/2008 9:01 AM > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > > > > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
