active directory - Clarification needed on DNS suffix not matching the FQDNS of the domain -
i've got problem local actual machine dns suffix configuration info mismatching ad managed computer info record called "dns name". i'd know takes precedence , whether chosen dns suffix should follow dns choose domain, or whether should follow choose network (dns). our ad suffixes , chosen dhcp-assigned dns suffixes different.
takes lead?
hklm\system\currentcontrolset\services\tcpip\parameters\domain hklm\system\currentcontrolset\services\tcpip\parameters\nv domain
how came about:
we have separate dns managing dhcp objects, default prefix. ms dns subzone of larger primary dns. of our desktops started propagating errant dns info ad didn't match actual fqdn, causing tools fail when trying resolve newly generate ad dns entries.
for example below: dhcp objects receive dhcp.domain.com suffix
resolvable fqdn: computer.dhcp.domain.com became: computer.ou.ad.domain.com
the latter mismatched fqdn, matches ad dns scheme , not resolve.
we manually set 2 registry entries above example.domain.com , rebooted. ad objects update correct suffix applied.
since domain , nv domain must match according ms technical specifications, follow ad domain suffix , dns suffixes must match if right?
we looking @ rollout span many devices we're looking avoid issues later on if ad , dns need better aligned now.
recap - of these best?
is correct? (what use now)
[ad] ad domain = ou.ad.domain.com
[registry] domain = dhcp.domain.com
[registry] nv domain = dhcp.domain.com
[dns] fqdn suffix = dhcp.domain.com
or more correct (using ms guidance on matter)
[ad] domain = ou.ad.domain.com
[registry] domain = ou.ad.domain.com
[registry] nv domain = ou.ad.domain.com
[dns] fqdn suffix = ou.ad.domain.com
thanks , guidance...especially if can make cleaner presentation.
Comments
Post a Comment