DNS Resolution - Domain devolution

  • Thread starter Thread starter Mike Cavanagh
  • Start date Start date
M

Mike Cavanagh

The way I understand the DNS, it will test the non-fully
qualifed hostname, the append the Primary DNS suffix, then
append the connection oriented suffix, the devolve the
Primary DNS suffix.

I need MS Client DNS resolution to devolve the Connection
Oriented DNS subdomain and not the Primary DNS subdomain.

Otherwise, I need DNS to test the connection oriented DNS
subdomain first, then test the Primary DNS subdomain
second.

Is either of these possible?
 
Not sure if there is a reg entry to change this or not. If you need it for
diag, you can use dig or nslookup and change the default domain to your
needs.
 
I need it for daily use in the Client PC.

Basically, the PC uses DHCP to get its IP/DNS settings.
The DNS suffix is associated with the Connection specific
entry, not the Primary DNS entry. Since the suffix can
change, I need it to be devolved, not the Primary DNS
suffix.

The way Windows does it, every query is slows down the
look ups and by the time it gets to the proper query,
things run slow. I have apps with MANY DNS lookups.

Another thought, is it possible to use a parameter to set
the Primary DNS suffix from a DHCP response.

Thanks,
Mike.
 
In
Mike Cavanagh said:
The way I understand the DNS, it will test the non-fully
qualifed hostname, the append the Primary DNS suffix, then
append the connection oriented suffix, the devolve the
Primary DNS suffix.

I need MS Client DNS resolution to devolve the Connection
Oriented DNS subdomain and not the Primary DNS subdomain.

Otherwise, I need DNS to test the connection oriented DNS
subdomain first, then test the Primary DNS subdomain
second.

Is either of these possible?
Click to expand...

On the DNS tab of TCP/IP properties select "Append these DNS suffixes (in
order)" then put what ever suffixes you want, in the order you want.
 
In
I need it for daily use in the Client PC.

Basically, the PC uses DHCP to get its IP/DNS settings.
The DNS suffix is associated with the Connection specific
entry, not the Primary DNS entry. Since the suffix can
change, I need it to be devolved, not the Primary DNS
suffix.

The way Windows does it, every query is slows down the
look ups and by the time it gets to the proper query,
things run slow. I have apps with MANY DNS lookups.

Another thought, is it possible to use a parameter to set
the Primary DNS suffix from a DHCP response.

Thanks,
Mike.
Click to expand...


It wouldn't be the Priamry DNS Suffix, but rather the Search Suffix, which
you can check in IP properties. Follow what Kevin said, and i fyou have
mutliple machines that need to be changed, it can be scripted.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================
 
Back
Top