Link to home
Start Free TrialLog in
Avatar of hrtmath
hrtmathFlag for United States of America

asked on

Domain name changed to Default-First-Site-Name

In Active Directory Sites and Services, the hm.local entry, our local domain, that's just above the Servers entries, was changed to Default-First-Site-Name. Can I simply rename it back to hm.local and restart the DNS service?

It's causing problems adding new network printers and new computer setup, everything else works normally.

Tom
Avatar of LauraEHunterMVP
LauraEHunterMVP
Flag of United States of America image
AD Sites and Services does not list your domain name, it lists your site names. AD installs with a single site called Default-First-Site-Name, so the behavior you are describing is normal.

If you open AD Domains and Trusts and/or AD Users & Computers, I all but guarantee that you will see the domain name that you expect.
Avatar of hrtmath
hrtmath
Flag of United States of America image

ASKER

I did. I did some more research, and netlogon.dns has three 600 entries for our hm.local domain. Two entries are at the bottom of the list. Could the extra 600 entries confuse workstations attaching to the computer?

I read about how to rebuild the netlogon.dns file, but I don't want to mess with it unless it's the appropriate thing to do.

http://thelazyadmin.com/blogs/thelazyadmin/archive/2004/12/08/DNS-Tips-_2300_2-_2D00_-DNS-Resource-Record-Registration.aspx

netlogon.dns file contents:

hm.local. 600 IN A 205.178.118.9
gc._msdcs.hm.local. 600 IN A 205.178.118.9
DomainDnsZones.hm.local. 600 IN A 205.178.118.9
ForestDnsZones.hm.local. 600 IN A 205.178.118.9
_ldap._tcp.hm.local. 600 IN SRV 0 100 389 HM-01.hm.local.
_ldap._tcp.Default-First-Site-Name._sites.hm.local. 600 IN SRV 0 100 389 HM-01.hm.local.
_ldap._tcp.pdc._msdcs.hm.local. 600 IN SRV 0 100 389 HM-01.hm.local.
_ldap._tcp.gc._msdcs.hm.local. 600 IN SRV 0 100 3268 HM-01.hm.local.
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.hm.local. 600 IN SRV 0 100 3268 HM-01.hm.local.
_ldap._tcp.35806466-f6c3-44aa-942a-15440f44db20.domains._msdcs.hm.local. 600 IN SRV 0 100 389 HM-01.hm.local.
1bf20d7c-3484-4d54-8cdf-68da6c1d83dd._msdcs.hm.local. 600 IN CNAME HM-01.hm.local.
_kerberos._tcp.dc._msdcs.hm.local. 600 IN SRV 0 100 88 HM-01.hm.local.
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.hm.local. 600 IN SRV 0 100 88 HM-01.hm.local.
_ldap._tcp.dc._msdcs.hm.local. 600 IN SRV 0 100 389 HM-01.hm.local.
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.hm.local. 600 IN SRV 0 100 389 HM-01.hm.local.
_kerberos._tcp.hm.local. 600 IN SRV 0 100 88 HM-01.hm.local.
_kerberos._tcp.Default-First-Site-Name._sites.hm.local. 600 IN SRV 0 100 88 HM-01.hm.local.
_gc._tcp.hm.local. 600 IN SRV 0 100 3268 HM-01.hm.local.
_gc._tcp.Default-First-Site-Name._sites.hm.local. 600 IN SRV 0 100 3268 HM-01.hm.local.
_kerberos._udp.hm.local. 600 IN SRV 0 100 88 HM-01.hm.local.
_kpasswd._tcp.hm.local. 600 IN SRV 0 100 464 HM-01.hm.local.
_kpasswd._udp.hm.local. 600 IN SRV 0 100 464 HM-01.hm.local.
_ldap._tcp.DomainDnsZones.hm.local. 600 IN SRV 0 100 389 HM-01.hm.local.
_ldap._tcp.Default-First-Site-Name._sites.DomainDnsZones.hm.local. 600 IN SRV 0 100 389 HM-01.hm.local.
_ldap._tcp.ForestDnsZones.hm.local. 600 IN SRV 0 100 389 HM-01.hm.local.
_ldap._tcp.Default-First-Site-Name._sites.ForestDnsZones.hm.local. 600 IN SRV 0 100 389 HM-01.hm.local.
hm.local. 600 IN A 192.168.64.1
gc._msdcs.hm.local. 600 IN A 192.168.64.1
ForestDnsZones.hm.local. 600 IN A 192.168.64.1
DomainDnsZones.hm.local. 600 IN A 192.168.64.1
hm.local. 600 IN A 192.168.6.1
gc._msdcs.hm.local. 600 IN A 192.168.6.1
ForestDnsZones.hm.local. 600 IN A 192.168.6.1
DomainDnsZones.hm.local. 600 IN A 192.168.6.1
ASKER CERTIFIED SOLUTION
Avatar of LauraEHunterMVP
LauraEHunterMVP
Flag of United States of America image
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of hrtmath
hrtmath
Flag of United States of America image

ASKER

I figured it out. The DHCP server had an external DNS server listed as the first DNS server. So users had no general DNS problems, but the external DNS server had no reference to our local domain. Ergo local domain references didn't work. Changing the default DNS server to the IP address of the domain controller and rebooting the workstations fixed the problem.

Thanks for your help. I'll assign the points to you.

Tom