andykemper
asked on
Server Name in DHCP Services keeps renaming itself to the host name *.mshome.net
On DHCP services in Win SBS2003 SP2. I create, register, and authorize a new DHCP server name. Eveything seems to work correctly as far as DHCP services work. For some unkown reason at some point the servername domain will change to "myservername".mshome.net
The network fuctionality does not seem to be affected in any way. Clients still receive DHCP addresses alright. On a client system, when doing an nslookup I see my name server show up correctly. Correct = "sbs1.dci.local"
But for some reason I see the name server keep renaming it'self in the DHCP window to the name "sbs1.mshome.net"
I can assure you there is only one name server on my network. I have tried deleting and recreating my DHCP registered server name and scope. For the first few hours it looks correct as sbs1.dci.local. Later on for some reason, it will change to sbs1.mshome.net. I can't figure out for the life of me why it does this. The name change does not prevent authorized clients from getting on the network. When I do nslookup on the clients and servers it shows correctly sbs1.dci.local.
I can't understand why the name changes to *.mshome.net on the DHCP services window. A reboot does not make any difference. Should I be concerned about this? If this is a problem, how do I fix it, other than routinely rebuilding and reauthorizing my DHCP server name and scope?
The network fuctionality does not seem to be affected in any way. Clients still receive DHCP addresses alright. On a client system, when doing an nslookup I see my name server show up correctly. Correct = "sbs1.dci.local"
But for some reason I see the name server keep renaming it'self in the DHCP window to the name "sbs1.mshome.net"
I can assure you there is only one name server on my network. I have tried deleting and recreating my DHCP registered server name and scope. For the first few hours it looks correct as sbs1.dci.local. Later on for some reason, it will change to sbs1.mshome.net. I can't figure out for the life of me why it does this. The name change does not prevent authorized clients from getting on the network. When I do nslookup on the clients and servers it shows correctly sbs1.dci.local.
I can't understand why the name changes to *.mshome.net on the DHCP services window. A reboot does not make any difference. Should I be concerned about this? If this is a problem, how do I fix it, other than routinely rebuilding and reauthorizing my DHCP server name and scope?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you,
I am glad others have had this problem too and have already researched the issue before hand. I was worried it might be due to hacking attempt.
I am glad others have had this problem too and have already researched the issue before hand. I was worried it might be due to hacking attempt.
Probably your server has more than one record, and when you open the DHCP console it is looking up the "incorrect"/default name.