• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 683
  • Last Modified:

Domain suffix search order problems

I have a domain who has a suffix search order set in the default domain policy, which is enforced and pushed down to all workstations and it has always worked.  I just added a new domain name to the list, it is one that we just created a trust with last week, and the new domain is not showing up in the ipconfig /all list.  It is odd.  it is listed the same as the other domains, no spaces and seperated by commas.  The domain is there, and the one way trust is active and validated, but it will just not show up.  I have rebooted workstations, ran a gpupdate /force and /sync, no changes.  ANy thoughts?  I am confused as to what it might be
1 Solution
What happens if you edit the suffix order and place the latest suffix higher in the list?  Do you see a change on the client (after policy re-application delay has been taken into account)?
nrthelpAuthor Commented:
I made some slight modifications the order, and moved the missing domain later in the line, and after a reboot of a new client (VM I just imaged, for a test) and it now is showing up in the new location.  Which is quite odd, but I guess I count my blessings on this one.  Good thoughts.

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now