set Client DNS server when add client into Domain

[Guest]

Hi,

I want to set a clienthost's DNS server IPs after the client joined the
domain the first time.
How can I do this? Thanks

 

[Cary Shultz [MVP]]

-----Original Message-----
Hi,

I want to set a clienthost's DNS server IPs after the client joined the
domain the first time.
How can I do this? Thanks


.

Nospam,

Not sure that I am following!

If you want the INTERNAL DNS Server IP Address to be part
of the TCP/IP configuration for each client then I would
suggest that you take a look at DHCP. You would
configure the Options 003, 006 and 015 ( with 044 and 046
if using WINS ). Granted, there are others but these are
the big three / big five.

Here is the reason for my 'not following': you stated
that you "want to set the clienthost's DNS Server IPs
AFTER the client joined the domain the first time". The
*AFTER* is the part that confuses me. Please take a look
at the following two MSKB Articles:

WIN2000
http://support.microsoft.com/default.aspx?scid=KB;en-
us;247811

WINXP
http://support.microsoft.com/default.aspx?scid=kb;
[LN];314861

As you can see from the two articles, DNS is EXTREMELY
vital in this process.

Now, if you are talking about the FORWARDERS Tab ( in the
DNS MMC ) for resolution to outside ( aka external )
requests you would simply enter the two or three IP
Addresses from your ISP's DNS Servers ( assuming that
your ISP is handling this for you ). You would also have
to delete the "." Zone in your Forward Lookup Zone (
FLZ ). If you do not do this then you will not be able
to resolve/reach external DNS hosts.

HTH,

Cary

 

[Guest]

Hi

My client machines does not run dhcp right now.

Here's what I have so far:

My company has a DNS server say xyz.com (192.168.1.1), I have access to
add hostname into it.

Now I setup two AD DC hosts both running Windows2003 server, all win2000
clients.
host1.xyz.com: 10.1.1.10
host2.xyz.com : 10.1.1.11
Both hosts runs DNS server point to its 127.0.0.1 loopback interface
Unresolved host is dns forwarded to company DNS server 192.168.1.1

And I have a domain created on both dc hosts: addomain.xyz.com
addomain.xyz.com is 10.1.1.10 on company central DNS.

All my client hosts use static ip now, but in future some will use dhcp.
All hosts will have a company dns record: clienthost.xyz.com 10.1.1.50
I manually add client into company dns so unix client have a way to reach
these boxes.

In the AD DC DNS servers the DNS server will be
clienthost.addomain.xyz.com(10.1.1.50)

Question 1: See any problem in this setup? Is this common way to do this?

Question 2: how can I have addomain.xyz.com resolve to 10.1.1.10 and
10.1.1.11 in company's dns server?

Question 3: How can I force client to set its dns to 10.1.1.10 and 10.1.1.11
when a non domain static ip client host joins the domain?

I hope I'm clear on this. Thanks

-----Original Message-----
Hi,

I want to set a clienthost's DNS server IPs after the client joined the
domain the first time.
How can I do this? Thanks


.

Nospam,

Not sure that I am following!

If you want the INTERNAL DNS Server IP Address to be part
of the TCP/IP configuration for each client then I would
suggest that you take a look at DHCP. You would
configure the Options 003, 006 and 015 ( with 044 and 046
if using WINS ). Granted, there are others but these are
the big three / big five.

Here is the reason for my 'not following': you stated
that you "want to set the clienthost's DNS Server IPs
AFTER the client joined the domain the first time". The
*AFTER* is the part that confuses me. Please take a look
at the following two MSKB Articles:

WIN2000
http://support.microsoft.com/default.aspx?scid=KB;en-
us;247811

WINXP
http://support.microsoft.com/default.aspx?scid=kb;
[LN];314861

As you can see from the two articles, DNS is EXTREMELY
vital in this process.

Now, if you are talking about the FORWARDERS Tab ( in the
DNS MMC ) for resolution to outside ( aka external )
requests you would simply enter the two or three IP
Addresses from your ISP's DNS Servers ( assuming that
your ISP is handling this for you ). You would also have
to delete the "." Zone in your Forward Lookup Zone (
FLZ ). If you do not do this then you will not be able
to resolve/reach external DNS hosts.

HTH,

Cary

 

[Cary Shultz [MVP]]

in-line...

-----Original Message-----
Hi

My client machines does not run dhcp right now.

Here's what I have so far:

My company has a DNS server say xyz.com

(192.168.1.1), I have access to

add hostname into it.

Now I setup two AD DC hosts both running Windows2003 server, all win2000
clients.
host1.xyz.com: 10.1.1.10
host2.xyz.com : 10.1.1.11
Both hosts runs DNS server point to its 127.0.0.1 loopback interface
Unresolved host is dns forwarded to company DNS server

192.168.1.1


Opps. Sorry. Not following you ;-)

Your INTERNAL DNS Server has a 192.168.1.1 IP Address.
So far, so good. Your two Active Directory Domain
Controllers are running Windows Server 2003. They have a
10.1.1.10 and 10.1.1.11 IP Address. So, we are clearly
talking about at least two subnets involved. So far, so
good! And both of the 10.1.1 WIN2003 servers are running
WIN2003 DNS? What, then, is the DNS Server at the
192.168.1.1 IP Address?????

Here is a *potential* problem: both of your AD Domain
Controllers should point to the INTERNAL DNS Server, not
necessarily to their Loopback Address ( the 127.0.0.1 ).
Now, this is where WIN2003 may have changed something. I
am not all that familiar with 2003 as I have touched it
only a few times really quickly. However, I doubt that
this would have been changed.

And, the DNS Server running at IP Address 192.168.1.1: is
it a WIN2000 or WIN2003 DNS Server, or, as I suspect, is
it a BIND DNS Server? If it is a BIND DNS Server, what
version of BIND? And, are your WIN2003 AD DCs running
DNS as well? It does sound like it. You did
explicitedly state that they are running DNS.

And I have a domain created on both dc hosts: addomain.xyz.com
addomain.xyz.com is 10.1.1.10 on company central DNS.

Not sure at all what this is: is this a Child Domain or
is this simply a client? What is the "addomain" part of
the addomain.xyz.com? It sounds to me like a child
domain...

All my client hosts use static ip now, but in future some will use dhcp.
All hosts will have a company dns record:

clienthost.xyz.com 10.1.1.50

I trust that the IP Address given is simply an example
and that not all client hosts have a 10.1.1.50 IP Address
( as this will cause a lot of problems )! In fact, this
may be the easiest problem of all to troubleshoot in that
on each client you would receive a popup indicating an IP
Address conflict.

I manually add client into company dns so unix client have a way to reach
these boxes.

This is possible but DHCP would really make your life
easier. I hope that you do not have too many hosts to
manage. Is there a reason that you want to use static IP
Addresses? I mean, you can do things as you see fit. No
one can tell you how to run your environment. It just
seems like a bit of extra work that is subject to 'human
error' and DHCP might resolve that. If the problem is
that you do not want to run WIN2000 / WIN2003 DHCP then
consider your Firewall...

In the AD DC DNS servers the DNS server will be
clienthost.addomain.xyz.com(10.1.1.50)

Question 1: See any problem in this setup? Is this

common way to do this?


See in-line comments above.

Question 2: how can I have addomain.xyz.com resolve to 10.1.1.10 and
10.1.1.11 in company's dns server?

Not really clear as to what the "addomain" part is so I
can not really answer this. Do you possibly mean that
you want a client/host 'addomain' to have two IP
Addresses? Anyway, not sure that you can have multiple
IP Addresses for one client/host. That is, assuming that
this client has a single NIC. If a client/host has
multiple NICs, then it would be possible. However, there
might be other problems if this machine is a "client" pc
and not a "server". Also, not sure that that I am
following you. If 'addomain' is a host and you want it
to point to the DNS IP Addresses then you would have to
manually enter them. Again, I repeat: without DHCP you
have to manually enter everything!!!!! I have to strees
that all WIN2000 / WINXP Clients M U S T point to an
internal DNS Server ( and preferable one that allows
Dynamic Updates...). I am not entirely following your
set up atthis point. But, I do have a bit of a better
picture...Sorry ;-)

Question 3: How can I force client to set its dns to 10.1.1.10 and 10.1.1.11
when a non domain static ip client host joins the domain?

AFAIK, when you set up the non-domain client ( such as a
guest user bringing in a laptop for a presentation or
what not ) to have the static IP Address you would simply
have to manually enter in the DNS information as
well...Again, I strees that without DHCP you have to
MANUALLY enter everything....

Cary

I hope I'm clear on this. Thanks

-----Original Message-----
Hi,

I want to set a clienthost's DNS server IPs after the client joined the
domain the first time.
How can I do this? Thanks


.

Nospam,

Not sure that I am following!

If you want the INTERNAL DNS Server IP Address to be part
of the TCP/IP configuration for each client then I would
suggest that you take a look at DHCP. You would
configure the Options 003, 006 and 015 ( with 044 and 046
if using WINS ). Granted, there are others but these are
the big three / big five.

Here is the reason for my 'not following': you stated
that you "want to set the clienthost's DNS Server IPs
AFTER the client joined the domain the first time". The
*AFTER* is the part that confuses me. Please take a look
at the following two MSKB Articles:

WIN2000
http://support.microsoft.com/default.aspx?scid=KB;en-
us;247811

WINXP
http://support.microsoft.com/default.aspx?scid=kb;
[LN];314861

As you can see from the two articles, DNS is EXTREMELY
vital in this process.

Now, if you are talking about the FORWARDERS Tab ( in the
DNS MMC ) for resolution to outside ( aka external )
requests you would simply enter the two or three IP
Addresses from your ISP's DNS Servers ( assuming that
your ISP is handling this for you ). You would also have
to delete the "." Zone in your Forward Lookup Zone (
FLZ ). If you do not do this then you will not be able
to resolve/reach external DNS hosts.

HTH,

Cary

.

 

[Guest]

Here's my enviroment, I controls many subnet within my company and need to
run static ip on unix and windows hosts.
I want to have all the windows hosts to resolve their DNS from my AD server
also running DNS.

Comment inline...

in-line...

(192.168.1.1), I have access to
192.168.1.1


Opps. Sorry. Not following you ;-)

Your INTERNAL DNS Server has a 192.168.1.1 IP Address.
So far, so good. Your two Active Directory Domain
Controllers are running Windows Server 2003. They have a
10.1.1.10 and 10.1.1.11 IP Address. So, we are clearly
talking about at least two subnets involved. So far, so
good! And both of the 10.1.1 WIN2003 servers are running
WIN2003 DNS? What, then, is the DNS Server at the
192.168.1.1 IP Address?????

192.168.1.1 is just an example of my company's central DNS server.

Here is a *potential* problem: both of your AD Domain
Controllers should point to the INTERNAL DNS Server, not
necessarily to their Loopback Address ( the 127.0.0.1 ).

What kind of problem are we talking about?
I'm already doing DNS forwarding from these two hosts for hostname that they
can't resovle.

Now, this is where WIN2003 may have changed something. I
am not all that familiar with 2003 as I have touched it
only a few times really quickly. However, I doubt that
this would have been changed.

And, the DNS Server running at IP Address 192.168.1.1: is
it a WIN2000 or WIN2003 DNS Server, or, as I suspect, is
it a BIND DNS Server? If it is a BIND DNS Server, what
version of BIND? And, are your WIN2003 AD DCs running
DNS as well? It does sound like it. You did
explicitedly state that they are running DNS.

It's running BIND, but I don't know what version.

Not sure at all what this is: is this a Child Domain or
is this simply a client? What is the "addomain" part of
the addomain.xyz.com? It sounds to me like a child
domain...

addomain is my Active directory domain name.
It's not a child domain.
For example: if my company domain is abc.com, I'll regiest addomain in
company's central dns. addomain.abc.com is just for AD.

clienthost.xyz.com 10.1.1.50

I trust that the IP Address given is simply an example
and that not all client hosts have a 10.1.1.50 IP Address
( as this will cause a lot of problems )! In fact, this
may be the easiest problem of all to troubleshoot in that
on each client you would receive a popup indicating an IP
Address conflict.

Yes, it's just an example, no worry here.

I manually add client into company dns so unix client have a way to reach
these boxes.

This is possible but DHCP would really make your life
easier. I hope that you do not have too many hosts to
manage. Is there a reason that you want to use static IP
Addresses? I mean, you can do things as you see fit. No
one can tell you how to run your environment. It just
seems like a bit of extra work that is subject to 'human
error' and DHCP might resolve that. If the problem is
that you do not want to run WIN2000 / WIN2003 DHCP then
consider your Firewall...

In the AD DC DNS servers the DNS server will be
clienthost.addomain.xyz.com(10.1.1.50)

Question 1: See any problem in this setup? Is this

common way to do this?


See in-line comments above.

Question 2: how can I have addomain.xyz.com resolve to 10.1.1.10 and
10.1.1.11 in company's dns server?

Not really clear as to what the "addomain" part is so I
can not really answer this. Do you possibly mean that
you want a client/host 'addomain' to have two IP
Addresses? Anyway, not sure that you can have multiple
IP Addresses for one client/host. That is, assuming that
this client has a single NIC. If a client/host has
multiple NICs, then it would be possible. However, there
might be other problems if this machine is a "client" pc
and not a "server". Also, not sure that that I am
following you. If 'addomain' is a host and you want it
to point to the DNS IP Addresses then you would have to
manually enter them. Again, I repeat: without DHCP you
have to manually enter everything!!!!! I have to strees
that all WIN2000 / WINXP Clients M U S T point to an
internal DNS Server ( and preferable one that allows
Dynamic Updates...). I am not entirely following your
set up atthis point. But, I do have a bit of a better
picture...Sorry ;-)

Question 3: How can I force client to set its dns to 10.1.1.10 and 10.1.1.11
when a non domain static ip client host joins the domain?

AFAIK, when you set up the non-domain client ( such as a
guest user bringing in a laptop for a presentation or
what not ) to have the static IP Address you would simply
have to manually enter in the DNS information as
well...Again, I strees that without DHCP you have to
MANUALLY enter everything....

Cary

I hope I'm clear on this. Thanks

-----Original Message-----
Hi,

I want to set a clienthost's DNS server IPs after the
client joined the
domain the first time.
How can I do this? Thanks


.
Nospam,

Not sure that I am following!

If you want the INTERNAL DNS Server IP Address to be part
of the TCP/IP configuration for each client then I would
suggest that you take a look at DHCP. You would
configure the Options 003, 006 and 015 ( with 044 and 046
if using WINS ). Granted, there are others but these are
the big three / big five.

Here is the reason for my 'not following': you stated
that you "want to set the clienthost's DNS Server IPs
AFTER the client joined the domain the first time". The
*AFTER* is the part that confuses me. Please take a look
at the following two MSKB Articles:

WIN2000
http://support.microsoft.com/default.aspx?scid=KB;en-
us;247811

WINXP
http://support.microsoft.com/default.aspx?scid=kb;
[LN];314861

As you can see from the two articles, DNS is EXTREMELY
vital in this process.

Now, if you are talking about the FORWARDERS Tab ( in the
DNS MMC ) for resolution to outside ( aka external )
requests you would simply enter the two or three IP
Addresses from your ISP's DNS Servers ( assuming that
your ISP is handling this for you ). You would also have
to delete the "." Zone in your Forward Lookup Zone (
FLZ ). If you do not do this then you will not be able
to resolve/reach external DNS hosts.

HTH,

Cary

.

 

[Enkidu]

DHCP would be the simplest way to solve your problems. Why don't you
use it?

From what you say your AD is in no way connected AD-wise to the
central office AD. Is this so?

Cheers,

Cliff

Here's my enviroment, I controls many subnet within my company and need to
run static ip on unix and windows hosts.
I want to have all the windows hosts to resolve their DNS from my AD server
also running DNS.

Comment inline...

in-line...

(192.168.1.1), I have access to
192.168.1.1


Opps. Sorry. Not following you ;-)

Your INTERNAL DNS Server has a 192.168.1.1 IP Address.
So far, so good. Your two Active Directory Domain
Controllers are running Windows Server 2003. They have a
10.1.1.10 and 10.1.1.11 IP Address. So, we are clearly
talking about at least two subnets involved. So far, so
good! And both of the 10.1.1 WIN2003 servers are running
WIN2003 DNS? What, then, is the DNS Server at the
192.168.1.1 IP Address?????

192.168.1.1 is just an example of my company's central DNS server.

Here is a *potential* problem: both of your AD Domain
Controllers should point to the INTERNAL DNS Server, not
necessarily to their Loopback Address ( the 127.0.0.1 ).

What kind of problem are we talking about?
I'm already doing DNS forwarding from these two hosts for hostname that they
can't resovle.

Now, this is where WIN2003 may have changed something. I
am not all that familiar with 2003 as I have touched it
only a few times really quickly. However, I doubt that
this would have been changed.

And, the DNS Server running at IP Address 192.168.1.1: is
it a WIN2000 or WIN2003 DNS Server, or, as I suspect, is
it a BIND DNS Server? If it is a BIND DNS Server, what
version of BIND? And, are your WIN2003 AD DCs running
DNS as well? It does sound like it. You did
explicitedly state that they are running DNS.

It's running BIND, but I don't know what version.

Not sure at all what this is: is this a Child Domain or
is this simply a client? What is the "addomain" part of
the addomain.xyz.com? It sounds to me like a child
domain...

addomain is my Active directory domain name.
It's not a child domain.
For example: if my company domain is abc.com, I'll regiest addomain in
company's central dns. addomain.abc.com is just for AD.

clienthost.xyz.com 10.1.1.50

I trust that the IP Address given is simply an example
and that not all client hosts have a 10.1.1.50 IP Address
( as this will cause a lot of problems )! In fact, this
may be the easiest problem of all to troubleshoot in that
on each client you would receive a popup indicating an IP
Address conflict.

Yes, it's just an example, no worry here.

I manually add client into company dns so unix client have a way to reach
these boxes.

This is possible but DHCP would really make your life
easier. I hope that you do not have too many hosts to
manage. Is there a reason that you want to use static IP
Addresses? I mean, you can do things as you see fit. No
one can tell you how to run your environment. It just
seems like a bit of extra work that is subject to 'human
error' and DHCP might resolve that. If the problem is
that you do not want to run WIN2000 / WIN2003 DHCP then
consider your Firewall...

In the AD DC DNS servers the DNS server will be
clienthost.addomain.xyz.com(10.1.1.50)

Question 1: See any problem in this setup? Is this

common way to do this?


See in-line comments above.

Question 2: how can I have addomain.xyz.com resolve to 10.1.1.10 and
10.1.1.11 in company's dns server?

Not really clear as to what the "addomain" part is so I
can not really answer this. Do you possibly mean that
you want a client/host 'addomain' to have two IP
Addresses? Anyway, not sure that you can have multiple
IP Addresses for one client/host. That is, assuming that
this client has a single NIC. If a client/host has
multiple NICs, then it would be possible. However, there
might be other problems if this machine is a "client" pc
and not a "server". Also, not sure that that I am
following you. If 'addomain' is a host and you want it
to point to the DNS IP Addresses then you would have to
manually enter them. Again, I repeat: without DHCP you
have to manually enter everything!!!!! I have to strees
that all WIN2000 / WINXP Clients M U S T point to an
internal DNS Server ( and preferable one that allows
Dynamic Updates...). I am not entirely following your
set up atthis point. But, I do have a bit of a better
picture...Sorry ;-)

Question 3: How can I force client to set its dns to 10.1.1.10 and 10.1.1.11
when a non domain static ip client host joins the domain?

AFAIK, when you set up the non-domain client ( such as a
guest user bringing in a laptop for a presentation or
what not ) to have the static IP Address you would simply
have to manually enter in the DNS information as
well...Again, I strees that without DHCP you have to
MANUALLY enter everything....

Cary

I hope I'm clear on this. Thanks




-----Original Message-----
Hi,

I want to set a clienthost's DNS server IPs after the
client joined the
domain the first time.
How can I do this? Thanks


.
Nospam,

Not sure that I am following!

If you want the INTERNAL DNS Server IP Address to be part
of the TCP/IP configuration for each client then I would
suggest that you take a look at DHCP. You would
configure the Options 003, 006 and 015 ( with 044 and 046
if using WINS ). Granted, there are others but these are
the big three / big five.

Here is the reason for my 'not following': you stated
that you "want to set the clienthost's DNS Server IPs
AFTER the client joined the domain the first time". The
*AFTER* is the part that confuses me. Please take a look
at the following two MSKB Articles:

WIN2000
http://support.microsoft.com/default.aspx?scid=KB;en-
us;247811

WINXP
http://support.microsoft.com/default.aspx?scid=kb;
[LN];314861

As you can see from the two articles, DNS is EXTREMELY
vital in this process.

Now, if you are talking about the FORWARDERS Tab ( in the
DNS MMC ) for resolution to outside ( aka external )
requests you would simply enter the two or three IP
Addresses from your ISP's DNS Servers ( assuming that
your ISP is handling this for you ). You would also have
to delete the "." Zone in your Forward Lookup Zone (
FLZ ). If you do not do this then you will not be able
to resolve/reach external DNS hosts.

HTH,

Cary


.