When you start talking about doing things like home VPN servers (or any home server for that matter), sooner or later you run up against a thorny problem: how can I make sure I can always connect to my home network remotely? Having (or knowing) what your home IP address is gives you a lot of flexibility though because if you know it, you can register domain names and have them point to it.For example, let’s say I wanted to expose a server (named “dwarf”) on my home network to the internet.In this post we will discuss some of the implementation details around the Network Name (“Net Name”) resource and its behavior in Windows Server 2008 R2.The purpose of Network Name is to allow clients to be able to resolve the DNS name to an IP Address to establish a connection to it. The scenario is this, I have a domain controller running Win2K3 which provides DNS and DHCP services to my small network.Clients are getting their DHCP addresses assigned correctly within scope and the DNS entry is getting registered. In the DHCP leases table, all the DHCP entries have the 'pen' icon indicating that their waiting to update DNS. In the DHCP log, it is full of the following entries: 30,11/14/06,, DNS Update Request,220.127.116.11,accounts01local,, 11,11/14/06,, Renew,10.0.0.12,accounts01local,* mac*, 31,11/14/06,, DNS Update Failed,10.0.0.12,accounts01local,-1, Working through the log, every DHCP lease is failing to update the DNS record.Then, create a host record for the hostname you want to use, something like “yourname.yourdomain.com”.
Hi Everyone, I have a 2003 AD DC running DNS services.During DNS registration we present a mapping between the network name and its provider IP addresses over some physical adapter that can reach a DNS server.Below is an example of a standard Network Name resource.I also have a 2008R2 as an additional DC also running DNS. When a computer or object is added to DNS, it only goes into Forward Lookup Zone, and does not create an associated PTR record. One of the great things I like about the (not so) new Windows 2008 R2 Powershell modules is that we can now more easily manage the core Microsoft Networking services (DNS, DHCP).