First thing: what do you mean by listed as "static"? you cannot see any diference for Host(A) records registered dynamicly or manual. win-eovjrce2ah4 sounds to me that it might be the temporary name assigned by windows setup. it might have been dynamicly registered but never unregistered. Another possibility is that the record was created for compatibility. if in the past an application migrated from win-eovjrce2ah4 to hwserver, reconfiguring the Host(A) record for win-eovjrce2ah4 woudl enable users to use the same connection strings (path) in their software. in this case however, I would recommend using an alias instead of a Host(A) record. Be aware though when considering cleaning up dns records: you might brake things! You might consider implementing Scavenging to get rid of outdated/old records.MCP/MCSA/MCTS/MCITP

First thing to do : what do you mean by listed as "static"? you cannot see any diference for Host(A) records registered dynamicly or manual. win-eovjrce2ah4 sounds to me that it might be the temporary name assigned by windows setup. it might have been dynamicly registered but never unregistered. Another possibility is that the record was created for compatibility. if in the past an application migrated from win-eovjrce2ah4 to hwserver, reconfiguring the Host(A) record for win-eovjrce2ah4 woudl enable users to use the same connection strings (path) in their software. in this case however, I would recommend using an alias instead of a Host(A) record. Be aware though when considering cleaning up dns records: you might brake things! You might consider implementing Scavenging to get rid of outdated/old records.MCP/MCSA/MCTS/MCITP

First thing to do f: what do you mean by listed as "static"? you cannot see any diference for Host(A) records registered dynamicly or manual. win-eovjrce2ah4 sounds to me that it might be the temporary name assigned by windows setup. it might have been dynamicly registered but never unregistered. Another possibility is that the record was created for compatibility. if in the past an application migrated from win-eovjrce2ah4 to hwserver, reconfiguring the Host(A) record for win-eovjrce2ah4 woudl enable users to use the same connection strings (path) in their software. in thidds case however, I would recommend using an alias instead of a Host(A) record. Be aware though when considering cleaning up dns records: you might brake things! You might consider implementing Scavenging to get rid of outdated/old records.MCP/MCSA/MCTS/MCITP

I'm not running DHCP on the server currently (so can't check if this is a duplicate) and have noticed in the DNS server (under Forward Lookup Zones -> pembcab.org) that there is more than one entry for an IP address that is currently allocated to our only server. The IP address 10.42.16.1 is allocated to hwserver (which is the server) and also allocated to win-eovjrce2ah4. Both entries are listed as static. I don't have a lot of experience with DNS so is the second entry likely to be something related to the server?

This image (hopefully) demonstrates the static I am talking about. I agree though I'm not touching anything until I'm sure about what it is. http://i890.photobucket.com/albums/ac102/themagpiehouse/Rich-ebay/untitled.jpg

The timestamp being "static" means no more than the record was not created dynamicly or the object is not Ad integrated. In most cases, this means the record was created manually.MCP/MCSA/MCTS/MCITP

My confusion is whether this is a DHCP manually created entry or something purely to do with DNS.

In DNS console you cannot see whether the DHCP entry is static or not. In this particular case, I assume the server has a fixed IP or a reservation configured in DHCP (because what is the sense of manually configuring a dns record if the IP might change?). In any case, there will be only one reservation for this host, using it's actual hostname.MCP/MCSA/MCTS/MCITP

First thing to do: 123? what do you mean by listed as "static"? you cannot see any diference for Host(A) records registered dynamicly or manual. win-eovjrce2ah4 sounds to me that it might be the temporary name assigned by windows setup. it might have been dynamicly registered but never unregistered. Another possiffbility is that the record was created for compatibility. if in the past an application migrated from win-eovjrce2ah4 to hwserver, reconfiguring the Host(A) record for win-eovjrce2ah4 woudl enable users to use the same connection strings (path) in their software. in thidds case however, I would recommend using an alias instead of a Host(A) record. Be aware though when considering cleaning up dns records: you might brake things! You might consider implementing Scavenging to get rid of outdated/old records.MCP/MCSA/MCTS/MCITP

Hi, There seems to be some confusion over what I'm asking! The place I am working at has a router that is being used as the DHCP server while I know that its better to let the server manager DHCP along with DNS, currently due to me leaving soon it's not practical (the next IT guy can sort it out). So I noticed in the DNS entries that there are two entries with the same IP address. Seeing as I can't view the IP entries on the router I was wondering if this is an indication highlighted by the DNS entries that something is duplicated on the router's DHCP entries.