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.
|