Windows Vista Tips

Windows Vista Tips > Newsgroups > Windows Server > DNS Server > RE: DHCP and Domain suffix search order

Reply
Thread Tools Display Modes

RE: DHCP and Domain suffix search order

 
 
FiZi
Guest
Posts: n/a

 
      05-15-2009
Wow I apologize for my spelling. I clearly should have re-read what I typed.
Wish I could go back and delete/edit my post.

I've corrected my typo's, spelling and thoughts below:


We've got a multiple domain setup where we have a root domain (let's say
fizi.ca with DC's) and two sub-domains for faculty and students (let's say
students.fizi.ca and faculty.fizi.ca both with DC's).

We're working on implementing DNS Scavenging and cleaning up our mess of a
DNS server. Our DHCP server and DNS servers are located in the 'fizi.ca'
domain.

When we setup new faculty desktops we create them under 'faculty.fizi.ca'
and when we setup student lab desktops we create them under
'students.fizi.ca' and so those computers A records are placed in the
appropriate domain and can resolve any of our other servers. When a user
comes to our campus and connects to our wireless or plugs intothe wall they
will have their A records created under 'fizi.ca'.

I just altered our wireless DHCP Scopes and setup a new sub domain (no DC's)
called public.fizi.ca. New computers connecting to our wireless are now
placing their A Records into 'public.fizi.ca' which is exactly what we want.
The problem we're having is we put servers related to students under
'students.fizi.ca' and servers for staff under 'faculty.fizi.ca'. Some of
those servers can't be resolved by their machine name when connected via
wireless. As an example we have a print server for students with a FQDN of
'printserver.students.fizi.ca'. When I connect to wireless and attempt to
ping 'printserver' or access '\\printserver' it fails to resolve. If I type
in the FQDN everything is happy. The server has a A record and a PTR record.

I configured option 134 "Hostname resolution order" to "0x2 hosts->dns" and
configured option 135 "Domain suffix search order" with "fizi.ca,
students.fizi.ca and faculty.fizi.ca". Shouldn't this solve the problem of
'printserver' not being resolvable? Or have I missed a step? I was hoping not
to have to create CNAME records in 'fizi.ca' for all our servers.
 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Domain Suffix Search Order. Windows Server 2003 R2 DNS,DHCP averied Server Networking 1 03-26-2008 07:35 PM
Re: Domain Suffix Search Order is missing from DHCP on several servers Kevin D. Goodknecht Sr. [MVP] DNS Server 2 01-10-2007 10:49 PM
DHCP Options - 135 Domain suffix search order Ricky Server Networking 0 09-14-2006 10:37 PM
DHCP option "135 Domain Suffix Search Order" is missing hfernandes2001 Windows Server 4 04-26-2006 07:51 PM
dhcp client suffix search order news.microsoft.com DNS Server 1 07-03-2005 01:10 AM



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59