Home

Using DHCP Custom option 135 to add dns suffix

%3CLINGO-SUB%20id%3D%22lingo-sub-85120%22%20slang%3D%22en-US%22%3EUsing%20DHCP%20Custom%20option%20135%20to%20add%20dns%20suffix%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-85120%22%20slang%3D%22en-US%22%3E%3CP%3EHi.%20We%20have%20two%20domains%20that%20are%20trusted%20both%20ways.%20We%20are%20in%20the%20process%20of%20moving%20users%20from%20DomainA%20to%20DomainB%20using%20ADMT.%20But%20the%20user%20that%20are%20moved%20from%20DomainA%20to%20DomainB%20must%20be%20able%20to%20access%20resources%20in%20their%20original%20domain%20(in%20this%20case%20DomainA).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBy%20setting%20the%20DNS%20suffinx%20manually%20on%20the%20adapter%20our%20POC%20shows%20that%20it%20works.%20Now%20I%20have%20to%20find%20at%20way%20to%20do%20so%20for%20everyone%20that%20are%20moved.%20I%20have%20been%20looking%20at%20my%20DHCP%20server%20and%20Google%20and%20found%20out%20the%20the%20option%2035%20and%20119%20is%20not%20suited%20for%20this.%20But%20there%20are%20articles%20talking%20about%20option%20135%2C%20a%20custom%20option%20to%20add%20more%20dns%20suffix's.%20Are%20there%20anyone%20that%20are%20using%20this%20option%20and%20can%20say%20%22It%20works%3F%22%20or%20should%20I%20just%20go%20the%20group%20policys%20way%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20reason%20not%20going%20the%20group%20policy%20way%20is%20that%20all%20computers%20are%20in%20one%20OU%2C%20not%20structured%20by%20location%20and%20I%20only%20need%20to%20apply%20the%20dns%20suffix%20to%20the%20users%20in%20UK%20(migrated%20from%20DomainA).%20Another%20option%20could%20be%20to%20add%20it%20on%20the%20users%20since%20we%20have%20those%20devided%20in%20to%20org%20OU's.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20let%20me%20know%20if%20anyone%20has%20used%20the%20135%20with%20success%20or%20failure.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-85120%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EActive%20Directory%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Jesper Stein
Contributor

Hi. We have two domains that are trusted both ways. We are in the process of moving users from DomainA to DomainB using ADMT. But the user that are moved from DomainA to DomainB must be able to access resources in their original domain (in this case DomainA).

 

By setting the DNS suffinx manually on the adapter our POC shows that it works. Now I have to find at way to do so for everyone that are moved. I have been looking at my DHCP server and Google and found out the the option 35 and 119 is not suited for this. But there are articles talking about option 135, a custom option to add more dns suffix's. Are there anyone that are using this option and can say "It works?" or should I just go the group policys way?

 

The reason not going the group policy way is that all computers are in one OU, not structured by location and I only need to apply the dns suffix to the users in UK (migrated from DomainA). Another option could be to add it on the users since we have those devided in to org OU's.

 

But let me know if anyone has used the 135 with success or failure.

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
35 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
29 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
9 Replies