<div>
we have no workstations connecting to this directly. our clients use the FQDN from the WAN so that's not an issue. It's more for when our developers VPN in and try to access links. <br />
<br />
So you're saying as long as they're win2k or better clients they don't even need globalnames? regular dns or AD will handle it?
</div>


<div>
only you can realy answer if global names are needed.... but if you didnt require wins previously, its unlikely you'd need globalnames now.<br />
I wouldnt have though VPN connections would require them either - as your VPN clients would get their internal addresses from DHCP (along with domain suffix) as well.<br />

</div>


<div>
we're not using DHCP. I'm not sure if they required WINS or they just installed it from habit. I'm taking over an existing environment. The only connections are from switches, servers (win2k8), and VPN clients (XP or better).
</div>


<div>
yer fair enough.... &nbsp;its hard when coming into a new environment that someone else has admined...<br />
How are the VPN clients being allocated IP's etc if its not from DHCP ? I would have thought what-ever is allocating them their IP details will also be able to allocate a dns name ?<br />

</div>


<div>
Our firewall assigns them private IPs not used anywhere else in our network (we choose the range).
</div>


<div>
ok - so i take it the firewall, for whatever reason, cant/wont allocate a default dns name?<br />
i havent run into that situation before - so yes, you may have to go down that path. (but because i havent experienced, i cant say for 100 sure) - looks like you just going to have to test without and test with and see!<br />

</div>


<div>
thanks for your help. this may be an issue with our FW, true. I'll check with them. THanks.
</div>


<div>
<div class="content wysiwyg-content">
I have a new Windows Server 2008 domain environment along with AD Integrated DNS. <br />
<br />
I have configured the GLOBALNAMES zone to replace NetBIOS. However I can't decide what that's for (if anything) besides computer names. For example, should I add webpage cnames there? <br />
<br />
In DNS domain forward lookup zone I have myserver-ilo with the ip address of the HP iLO card in it. If you go to http://myserver-ilo.mydomain.com&nbsp;you'll get the page. But want to be able to leave out the mydomain.com piece. So should I add the CNAME record for myserver-ilo that points to the FQDN record in the regular forward lookup zone or in the GlobalNames zone? I think it works either way. I just want to make sure I'm doing it correctly. <br />
<br />
Thanks!
</div>
</div>


I have a new Windows Server 2008 domain environment along with AD Integrated DNS. 

I have configured the GLOBALNAMES zone to replace NetBIOS. However I can't decide what that's for (if anything) besides computer names. For example, should I add webpage cnames there? 

In DNS domain forward lookup zone I have myserver-ilo with the ip address of the HP iLO card in it. If you go to http://myserver-ilo.mydomain.com you'll get the page. But want to be able to leave out the mydomain.com piece. So should I add the CNAME record for myserver-ilo that points to the FQDN record in the regular forward lookup zone or in the GlobalNames zone? I think it works either way. I just want to make sure I'm doing it correctly. 

Thanks!

Create CNAMES in DNS or GlobalNames in Windows Server 2008

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.