DNS client settings

[Per Hagstrom]

Hey!

I think I know at least, that you are ONLY supposed to enter your internal
DNS server(s) on your workstations in your network.

Our situation is that our DNS manager only has one DNS server in the
network. And all the clients uses it as their primary DNS server AND the
ISP's DNS servers as their secondary...! (Due to DHCP)
I informed that I thought the best way is to ONLY have the internal DNS on
the clients and only let the DNS server itself do the Forwarding to the
ISP's DNS server.
The reply back was that if the internal DNS server goes down, workstations
can still resolve IP addresses on the internet, which I guess is a point.
(but not a good point?!)
BUT we have internal communication problems, where we have to do IPCONFIG /
FLUSHDNS all the time to be able to resolve internal server names.
My guess is that workstations sometimes jumps to the secondary DNS, and ends
up on the ISP's DNS, and now of a sudden they can't resolve internal names
anymore...

Could someone please confirm this with me. Even give me a link to a
Microsoft Article or something so I can back it up easier before I go to the
manager again.

Thanks!!

/ Per Hagstrom

 

[Per Hagstrom]

Lanwench,

Yeah, I already read that article, but it doesn't address my specific
problem about why you should ONLY have the internal DNS server(s) configured
on your workstations... and NOT enter any external DNS servers...

Thanks though!

/ Per


"Lanwench [MVP - Exchange]"

 

[Lanwench [MVP - Exchange]]

Because your computers need to rely on DNS to find each other, and if you
include your ISP's DNS server in their IP settings, it won't have that
information and you'll have tons of login problems.

Lanwench,

Yeah, I already read that article, but it doesn't address my specific
problem about why you should ONLY have the internal DNS server(s)
configured on your workstations... and NOT enter any external DNS
servers...

Thanks though!

/ Per


"Lanwench [MVP - Exchange]"

All servers and workstations should specify the internal
AD-integrated DNS server's IP address in their network settings. The
AD-integrated DNS server should be set up with forwarders to several
public DNS servers for external resolution.

See http://support.microsoft.com/default.aspx?scid=kb;en-us;300202
for more info.

 

[Per Hagstrom]

Yeah, we do have tons of problems...!
But I need black on white before I can go to my boss... so I was hoping
somebody could find a specific article about that...?
Else it's only gonna be MY opinion instead of having Microsoft backing me
up..!
Right now ipconfig /flushdns solves our "problems".... sigh.. heh!

/ Per


"Lanwench [MVP - Exchange]"

Because your computers need to rely on DNS to find each other, and if you
include your ISP's DNS server in their IP settings, it won't have that
information and you'll have tons of login problems.

Lanwench,

Yeah, I already read that article, but it doesn't address my specific
problem about why you should ONLY have the internal DNS server(s)
configured on your workstations... and NOT enter any external DNS
servers...

Thanks though!

/ Per


"Lanwench [MVP - Exchange]"

All servers and workstations should specify the internal
AD-integrated DNS server's IP address in their network settings. The
AD-integrated DNS server should be set up with forwarders to several
public DNS servers for external resolution.

See http://support.microsoft.com/default.aspx?scid=kb;en-us;300202
for more info.

Per Hagstrom wrote:
Hey!

I think I know at least, that you are ONLY supposed to enter your
internal DNS server(s) on your workstations in your network.

Our situation is that our DNS manager only has one DNS server in the
network. And all the clients uses it as their primary DNS server AND
the ISP's DNS servers as their secondary...! (Due to DHCP)
I informed that I thought the best way is to ONLY have the internal
DNS on the clients and only let the DNS server itself do the
Forwarding to the ISP's DNS server.
The reply back was that if the internal DNS server goes down,
workstations can still resolve IP addresses on the internet, which I
guess is a point. (but not a good point?!)
BUT we have internal communication problems, where we have to do
IPCONFIG / FLUSHDNS all the time to be able to resolve internal
server names. My guess is that workstations sometimes jumps to the
secondary DNS, and ends up on the ISP's DNS, and now of a sudden
they can't resolve internal names anymore...

Could someone please confirm this with me. Even give me a link to a
Microsoft Article or something so I can back it up easier before I
go to the manager again.

Thanks!!

/ Per Hagstrom

 

[Lanwench [MVP - Exchange]]

I don't know how more plainly anyone can state it. You put in external DNS
IPs....problems. You take them away...problems disappear.

Yeah, we do have tons of problems...!
But I need black on white before I can go to my boss... so I was
hoping somebody could find a specific article about that...?
Else it's only gonna be MY opinion instead of having Microsoft
backing me up..!
Right now ipconfig /flushdns solves our "problems".... sigh.. heh!

/ Per


"Lanwench [MVP - Exchange]"

Because your computers need to rely on DNS to find each other, and
if you include your ISP's DNS server in their IP settings, it won't
have that information and you'll have tons of login problems.

Lanwench,

Yeah, I already read that article, but it doesn't address my
specific problem about why you should ONLY have the internal DNS
server(s) configured on your workstations... and NOT enter any
external DNS servers...

Thanks though!

/ Per


"Lanwench [MVP - Exchange]"
message All servers and workstations should specify the internal
AD-integrated DNS server's IP address in their network settings.
The AD-integrated DNS server should be set up with forwarders to
several public DNS servers for external resolution.

See http://support.microsoft.com/default.aspx?scid=kb;en-us;300202
for more info.

Per Hagstrom wrote:
Hey!

I think I know at least, that you are ONLY supposed to enter your
internal DNS server(s) on your workstations in your network.

Our situation is that our DNS manager only has one DNS server in
the network. And all the clients uses it as their primary DNS
server AND the ISP's DNS servers as their secondary...! (Due to
DHCP) I informed that I thought the best way is to ONLY have the
internal DNS on the clients and only let the DNS server itself do
the Forwarding to the ISP's DNS server.
The reply back was that if the internal DNS server goes down,
workstations can still resolve IP addresses on the internet,
which I guess is a point. (but not a good point?!)
BUT we have internal communication problems, where we have to do
IPCONFIG / FLUSHDNS all the time to be able to resolve internal
server names. My guess is that workstations sometimes jumps to the
secondary DNS, and ends up on the ISP's DNS, and now of a sudden
they can't resolve internal names anymore...

Could someone please confirm this with me. Even give me a link to
a Microsoft Article or something so I can back it up easier
before I go to the manager again.

Thanks!!

/ Per Hagstrom

 

[Per Hagstrom]

I know, I know... heh!
But apparently that is not enough for me to tell...

....so I need black&white describing why...

Oh well.. I will continue to search the internet.. was just hoping somebody
could save me some time.. !

Thanks!

/ Per


"Lanwench [MVP - Exchange]"

I don't know how more plainly anyone can state it. You put in external DNS
IPs....problems. You take them away...problems disappear.

Yeah, we do have tons of problems...!
But I need black on white before I can go to my boss... so I was
hoping somebody could find a specific article about that...?
Else it's only gonna be MY opinion instead of having Microsoft
backing me up..!
Right now ipconfig /flushdns solves our "problems".... sigh.. heh!

/ Per


"Lanwench [MVP - Exchange]"

Because your computers need to rely on DNS to find each other, and
if you include your ISP's DNS server in their IP settings, it won't
have that information and you'll have tons of login problems.

Per Hagstrom wrote:
Lanwench,

Yeah, I already read that article, but it doesn't address my
specific problem about why you should ONLY have the internal DNS
server(s) configured on your workstations... and NOT enter any
external DNS servers...

Thanks though!

/ Per


"Lanwench [MVP - Exchange]"
message All servers and workstations should specify the internal
AD-integrated DNS server's IP address in their network settings.
The AD-integrated DNS server should be set up with forwarders to
several public DNS servers for external resolution.

See http://support.microsoft.com/default.aspx?scid=kb;en-us;300202
for more info.

Per Hagstrom wrote:
Hey!

I think I know at least, that you are ONLY supposed to enter your
internal DNS server(s) on your workstations in your network.

Our situation is that our DNS manager only has one DNS server in
the network. And all the clients uses it as their primary DNS
server AND the ISP's DNS servers as their secondary...! (Due to
DHCP) I informed that I thought the best way is to ONLY have the
internal DNS on the clients and only let the DNS server itself do
the Forwarding to the ISP's DNS server.
The reply back was that if the internal DNS server goes down,
workstations can still resolve IP addresses on the internet,
which I guess is a point. (but not a good point?!)
BUT we have internal communication problems, where we have to do
IPCONFIG / FLUSHDNS all the time to be able to resolve internal
server names. My guess is that workstations sometimes jumps to the
secondary DNS, and ends up on the ISP's DNS, and now of a sudden
they can't resolve internal names anymore...

Could someone please confirm this with me. Even give me a link to
a Microsoft Article or something so I can back it up easier
before I go to the manager again.

Thanks!!

/ Per Hagstrom

 

[Lanwench [MVP - Exchange]]

Sheesh, what do they want? A handwritten note from Mr. Gates?

See KB 247811, maybe?

I know, I know... heh!
But apparently that is not enough for me to tell...

...so I need black&white describing why...

Oh well.. I will continue to search the internet.. was just hoping
somebody could save me some time.. !

Thanks!

/ Per


"Lanwench [MVP - Exchange]"

I don't know how more plainly anyone can state it. You put in
external DNS IPs....problems. You take them away...problems
disappear.

Yeah, we do have tons of problems...!
But I need black on white before I can go to my boss... so I was
hoping somebody could find a specific article about that...?
Else it's only gonna be MY opinion instead of having Microsoft
backing me up..!
Right now ipconfig /flushdns solves our "problems".... sigh.. heh!

/ Per


"Lanwench [MVP - Exchange]"
message Because your computers need to rely on DNS to find each other, and
if you include your ISP's DNS server in their IP settings, it won't
have that information and you'll have tons of login problems.

Per Hagstrom wrote:
Lanwench,

Yeah, I already read that article, but it doesn't address my
specific problem about why you should ONLY have the internal DNS
server(s) configured on your workstations... and NOT enter any
external DNS servers...

Thanks though!

/ Per


"Lanwench [MVP - Exchange]"
in message All servers and workstations should specify the internal
AD-integrated DNS server's IP address in their network settings.
The AD-integrated DNS server should be set up with forwarders to
several public DNS servers for external resolution.

See
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202
for more info.

Per Hagstrom wrote:
Hey!

I think I know at least, that you are ONLY supposed to enter
your internal DNS server(s) on your workstations in your
network.

Our situation is that our DNS manager only has one DNS server in
the network. And all the clients uses it as their primary DNS
server AND the ISP's DNS servers as their secondary...! (Due to
DHCP) I informed that I thought the best way is to ONLY have the
internal DNS on the clients and only let the DNS server itself
do the Forwarding to the ISP's DNS server.
The reply back was that if the internal DNS server goes down,
workstations can still resolve IP addresses on the internet,
which I guess is a point. (but not a good point?!)
BUT we have internal communication problems, where we have to do
IPCONFIG / FLUSHDNS all the time to be able to resolve internal
server names. My guess is that workstations sometimes jumps to
the secondary DNS, and ends up on the ISP's DNS, and now of a
sudden they can't resolve internal names anymore...

Could someone please confirm this with me. Even give me a link
to a Microsoft Article or something so I can back it up easier
before I go to the manager again.

Thanks!!

/ Per Hagstrom

 

[Per Hagstrom]

naah.. not directly to the point in that article either..
Mr. Gates would probably do though... ! hehe!!

I guess this problem is too obvious for somebody to even write about.. heh..
?!
....oh well.. I guess I have to live with flushdns... sigh!

/ Per


"Lanwench [MVP - Exchange]"

Sheesh, what do they want? A handwritten note from Mr. Gates?

See KB 247811, maybe?

I know, I know... heh!
But apparently that is not enough for me to tell...

...so I need black&white describing why...

Oh well.. I will continue to search the internet.. was just hoping
somebody could save me some time.. !

Thanks!

/ Per


"Lanwench [MVP - Exchange]"

I don't know how more plainly anyone can state it. You put in
external DNS IPs....problems. You take them away...problems
disappear.

Per Hagstrom wrote:
Yeah, we do have tons of problems...!
But I need black on white before I can go to my boss... so I was
hoping somebody could find a specific article about that...?
Else it's only gonna be MY opinion instead of having Microsoft
backing me up..!
Right now ipconfig /flushdns solves our "problems".... sigh.. heh!

/ Per


"Lanwench [MVP - Exchange]"
message Because your computers need to rely on DNS to find each other, and
if you include your ISP's DNS server in their IP settings, it won't
have that information and you'll have tons of login problems.

Per Hagstrom wrote:
Lanwench,

Yeah, I already read that article, but it doesn't address my
specific problem about why you should ONLY have the internal DNS
server(s) configured on your workstations... and NOT enter any
external DNS servers...

Thanks though!

/ Per


"Lanwench [MVP - Exchange]"
in message All servers and workstations should specify the internal
AD-integrated DNS server's IP address in their network settings.
The AD-integrated DNS server should be set up with forwarders to
several public DNS servers for external resolution.

See
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202
for more info.

Per Hagstrom wrote:
Hey!

I think I know at least, that you are ONLY supposed to enter
your internal DNS server(s) on your workstations in your
network.

Our situation is that our DNS manager only has one DNS server in
the network. And all the clients uses it as their primary DNS
server AND the ISP's DNS servers as their secondary...! (Due to
DHCP) I informed that I thought the best way is to ONLY have the
internal DNS on the clients and only let the DNS server itself
do the Forwarding to the ISP's DNS server.
The reply back was that if the internal DNS server goes down,
workstations can still resolve IP addresses on the internet,
which I guess is a point. (but not a good point?!)
BUT we have internal communication problems, where we have to do
IPCONFIG / FLUSHDNS all the time to be able to resolve internal
server names. My guess is that workstations sometimes jumps to
the secondary DNS, and ends up on the ISP's DNS, and now of a
sudden they can't resolve internal names anymore...

Could someone please confirm this with me. Even give me a link
to a Microsoft Article or something so I can back it up easier
before I go to the manager again.

Thanks!!

/ Per Hagstrom

 

[Per Hagstrom]

Brian,

Yepp... I know and that is our problem.. we have one internal DNS... as soon
as a workstation has problems communicating with it, it jumps to the
secondary.. which is our ISP's DNS... and THEN...no more communication with
the WHOLE internal network... yay.. !!
Additionally you can reset the client with ipconfig /flushdns... yay!! hehe!


BUT... what I really need is black&white describing this specific problem..
from a "high" enough source.. like Microsoft...

Thanks for trying to help me though.. !

/ Per

 

[Jonathan de Boyne Pollard]

PH> Our situation is that our DNS manager [...]

.... is a fool.

In a properly configured network, all of the proxy DNS servers whose IP
addresses are used by DNS Clients _must_ provide identical views of the DNS
namespace. Arranging for DNS Clients to fall back from a proxy DNS server
that provides an "internal" view (the organization's own DNS server) to a
proxy DNS server that provides an "external" view (the organization's ISP's
DNS server) is a simple recipe for disaster.

To achieve the stated goal of providing DNS service even in the event of a
single server outage, your DNS manager should have _more than just the one_
DNS server, therefore.

The failure modes that cause the disasters are obvious with a modicum of
thought. Fallback from the one proxy DNS server to the other can happen at
any time, and can (for example) be triggered by simple network congestion.
The result is that one cannot predict what view of the DNS namespace will be
presented to a DNS Client from moment to moment.

It is, however, the facts that the problems are happening right now, right in
front of his/her face; that an explanation, which can be easily verified with
some simple experimentation, of the cause of the problems and a remedy have
been provided; and that yet (reportedly) he/she is refusing to correct the
error and instead holding out for someone with a brand name to repeat exactly
the same explanation and remedy; that make your DNS manager a fool.

 

[Lanwench [MVP - Exchange]]

As it's perfectly demonstrable that using the ISP's DNS servers causes
problems, I can't imagine why this would turn into a political disaster.
Wait, never mind, anything can. I'd email the boss and tell him everything
you've read indicates that your current config "may" be "related" to the
network problems.

Yeah.. well see... the DNS Server isn't my responsibility... but my
bosses... but it causes our whole network big problems... and how
dare I criticize my boss.. ?? Without any black&white.. heh?!?!

I would feel way better to even mention anything again about it if I
had some black&white to pull out..

See my problem.. ?!

/ Per


"Lanwench [MVP - Exchange]"

Are you actually getting arguments against proper config from your
boss?

naah.. not directly to the point in that article either..
Mr. Gates would probably do though... ! hehe!!

I guess this problem is too obvious for somebody to even write
about.. heh.. ?!
...oh well.. I guess I have to live with flushdns... sigh!

/ Per


"Lanwench [MVP - Exchange]"
message Sheesh, what do they want? A handwritten note from Mr. Gates?

See KB 247811, maybe?


Hagstrom wrote:
I know, I know... heh!
But apparently that is not enough for me to tell...

...so I need black&white describing why...

Oh well.. I will continue to search the internet.. was just hoping
somebody could save me some time.. !

Thanks!

/ Per


"Lanwench [MVP - Exchange]"
in message I don't know how more plainly anyone can state it. You put in
external DNS IPs....problems. You take them away...problems
disappear.

Per Hagstrom wrote:
Yeah, we do have tons of problems...!
But I need black on white before I can go to my boss... so I was
hoping somebody could find a specific article about that...?
Else it's only gonna be MY opinion instead of having Microsoft
backing me up..!
Right now ipconfig /flushdns solves our "problems".... sigh..
heh!

/ Per


"Lanwench [MVP - Exchange]"
<[email protected]>
wrote in message Because your computers need to rely on DNS to find each other,
and if you include your ISP's DNS server in their IP settings,
it won't have that information and you'll have tons of login
problems.

Per Hagstrom wrote:
Lanwench,

Yeah, I already read that article, but it doesn't address my
specific problem about why you should ONLY have the internal
DNS server(s) configured on your workstations... and NOT
enter any external DNS servers...

Thanks though!

/ Per


"Lanwench [MVP - Exchange]"
<[email protected]>
wrote in message All servers and workstations should specify the internal
AD-integrated DNS server's IP address in their network
settings. The AD-integrated DNS server should be set up with
forwarders to several public DNS servers for external
resolution.

See
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202
for more info.

Per Hagstrom wrote:
Hey!

I think I know at least, that you are ONLY supposed to enter
your internal DNS server(s) on your workstations in your
network.

Our situation is that our DNS manager only has one DNS
server in the network. And all the clients uses it as their
primary DNS server AND the ISP's DNS servers as their
secondary...! (Due to DHCP) I informed that I thought the
best way is to ONLY have the internal DNS on the clients
and only let the DNS server itself do the Forwarding to the
ISP's DNS server. The reply back was that if the internal
DNS server goes down, workstations can still resolve IP
addresses on the internet, which I guess is a point. (but
not a good point?!) BUT we have internal communication
problems, where we have to do IPCONFIG / FLUSHDNS all the
time to be able to resolve internal server names. My guess
is that workstations sometimes jumps to the secondary DNS,
and ends up on the ISP's DNS, and now of a sudden they
can't resolve internal names anymore...

Could someone please confirm this with me. Even give me a
link to a Microsoft Article or something so I can back it
up easier before I go to the manager again.

Thanks!!

/ Per Hagstrom

 

[Per Hagstrom]

Haaaah!!

I got me a good laugh out of that one!!

You are explaining it very well.. thanks.. !
I sure wish I had a white paper addressing NOT to include ISP DNS on the
workstations though..
What a mess this is... you can't imagine... !

Thanks!!

/ Per

 

[Per Hagstrom]

Oh yeah.. this is a big mess.. !!
It is kinda one of these,
A-boss-who-lets-everyone-think-it's-setup-right-because-they-know-best
deals... heh!
You can't argue with one of those... the only thing I can think of would be
to show black&white, these are the facts... !

Too bad there are no big warnings about this though.. !?

/ Per


"Lanwench [MVP - Exchange]"

As it's perfectly demonstrable that using the ISP's DNS servers causes
problems, I can't imagine why this would turn into a political disaster.
Wait, never mind, anything can. I'd email the boss and tell him everything
you've read indicates that your current config "may" be "related" to the
network problems.

Yeah.. well see... the DNS Server isn't my responsibility... but my
bosses... but it causes our whole network big problems... and how
dare I criticize my boss.. ?? Without any black&white.. heh?!?!

I would feel way better to even mention anything again about it if I
had some black&white to pull out..

See my problem.. ?!

/ Per


"Lanwench [MVP - Exchange]"

Are you actually getting arguments against proper config from your
boss?

Per Hagstrom wrote:
naah.. not directly to the point in that article either..
Mr. Gates would probably do though... ! hehe!!

I guess this problem is too obvious for somebody to even write
about.. heh.. ?!
...oh well.. I guess I have to live with flushdns... sigh!

/ Per


"Lanwench [MVP - Exchange]"
message Sheesh, what do they want? A handwritten note from Mr. Gates?

See KB 247811, maybe?


Hagstrom wrote:
I know, I know... heh!
But apparently that is not enough for me to tell...

...so I need black&white describing why...

Oh well.. I will continue to search the internet.. was just hoping
somebody could save me some time.. !

Thanks!

/ Per


"Lanwench [MVP - Exchange]"
in message I don't know how more plainly anyone can state it. You put in
external DNS IPs....problems. You take them away...problems
disappear.

Per Hagstrom wrote:
Yeah, we do have tons of problems...!
But I need black on white before I can go to my boss... so I was
hoping somebody could find a specific article about that...?
Else it's only gonna be MY opinion instead of having Microsoft
backing me up..!
Right now ipconfig /flushdns solves our "problems".... sigh..
heh!

/ Per


"Lanwench [MVP - Exchange]"
<[email protected]>
wrote in message Because your computers need to rely on DNS to find each other,
and if you include your ISP's DNS server in their IP settings,
it won't have that information and you'll have tons of login
problems.

Per Hagstrom wrote:
Lanwench,

Yeah, I already read that article, but it doesn't address my
specific problem about why you should ONLY have the internal
DNS server(s) configured on your workstations... and NOT
enter any external DNS servers...

Thanks though!

/ Per


"Lanwench [MVP - Exchange]"
<[email protected]>
wrote in message All servers and workstations should specify the internal
AD-integrated DNS server's IP address in their network
settings. The AD-integrated DNS server should be set up with
forwarders to several public DNS servers for external
resolution.

See
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202
for more info.

Per Hagstrom wrote:
Hey!

I think I know at least, that you are ONLY supposed to enter
your internal DNS server(s) on your workstations in your
network.

Our situation is that our DNS manager only has one DNS
server in the network. And all the clients uses it as their
primary DNS server AND the ISP's DNS servers as their
secondary...! (Due to DHCP) I informed that I thought the
best way is to ONLY have the internal DNS on the clients
and only let the DNS server itself do the Forwarding to the
ISP's DNS server. The reply back was that if the internal
DNS server goes down, workstations can still resolve IP
addresses on the internet, which I guess is a point. (but
not a good point?!) BUT we have internal communication
problems, where we have to do IPCONFIG / FLUSHDNS all the
time to be able to resolve internal server names. My guess
is that workstations sometimes jumps to the secondary DNS,
and ends up on the ISP's DNS, and now of a sudden they
can't resolve internal names anymore...

Could someone please confirm this with me. Even give me a
link to a Microsoft Article or something so I can back it
up easier before I go to the manager again.

Thanks!!

/ Per Hagstrom

 

[Per Hagstrom]

Latest updates...!

Alright... I have now provided a higher boss with as much info as I could
think of... and now they talked through the whole mess... without including
me in the discussion... sooo... now they agreed to.. setup a second internal
DNS, BUT to keep the ISP's DNS as a backup... ! maaaan.. .!
First thought was.. oh joy.. they once again think they have it right.. but
now we are just getting half as much problems.. but still problems when
clients happen to "failover" to the third DNS entry...

But then I also remember something about, only the 2 first DNS entries are
used.. or something like that?
Could someone fill me in there?
Is this new setup maybe in fact gonna work, because the 2 first DNS entries
are internal and the third and fourth which are external in fact are not
gonna get in use anyways.. ?

Thanks!

(the-never-ending-story... heh!)

/ Per

 

[Lanwench [MVP - Exchange]]

Yes you can argue, you just have to do it right. If he's being stubborn, go
to his boss. This is a pretty major stupidity on his part.

Oh yeah.. this is a big mess.. !!
It is kinda one of these,
A-boss-who-lets-everyone-think-it's-setup-right-because-they-know-best
deals... heh!
You can't argue with one of those... the only thing I can think of
would be to show black&white, these are the facts... !

Too bad there are no big warnings about this though.. !?

/ Per


"Lanwench [MVP - Exchange]"

As it's perfectly demonstrable that using the ISP's DNS servers
causes problems, I can't imagine why this would turn into a
political disaster. Wait, never mind, anything can. I'd email the
boss and tell him everything you've read indicates that your current
config "may" be "related" to the network problems.

Yeah.. well see... the DNS Server isn't my responsibility... but my
bosses... but it causes our whole network big problems... and how
dare I criticize my boss.. ?? Without any black&white.. heh?!?!

I would feel way better to even mention anything again about it if I
had some black&white to pull out..

See my problem.. ?!

/ Per


"Lanwench [MVP - Exchange]"
message Are you actually getting arguments against proper config from your
boss?

Per Hagstrom wrote:
naah.. not directly to the point in that article either..
Mr. Gates would probably do though... ! hehe!!

I guess this problem is too obvious for somebody to even write
about.. heh.. ?!
...oh well.. I guess I have to live with flushdns... sigh!

/ Per


"Lanwench [MVP - Exchange]"
in message Sheesh, what do they want? A handwritten note from Mr. Gates?

See KB 247811, maybe?


Hagstrom wrote:
I know, I know... heh!
But apparently that is not enough for me to tell...

...so I need black&white describing why...

Oh well.. I will continue to search the internet.. was just
hoping somebody could save me some time.. !

Thanks!

/ Per


"Lanwench [MVP - Exchange]"
<[email protected]>
wrote in message I don't know how more plainly anyone can state it. You put in
external DNS IPs....problems. You take them away...problems
disappear.

Per Hagstrom wrote:
Yeah, we do have tons of problems...!
But I need black on white before I can go to my boss... so I
was hoping somebody could find a specific article about
that...? Else it's only gonna be MY opinion instead of having
Microsoft backing me up..!
Right now ipconfig /flushdns solves our "problems".... sigh..
heh!

/ Per


"Lanwench [MVP - Exchange]"
<[email protected]>
wrote in message Because your computers need to rely on DNS to find each
other, and if you include your ISP's DNS server in their IP
settings, it won't have that information and you'll have
tons of login problems.

Per Hagstrom wrote:
Lanwench,

Yeah, I already read that article, but it doesn't address my
specific problem about why you should ONLY have the internal
DNS server(s) configured on your workstations... and NOT
enter any external DNS servers...

Thanks though!

/ Per


"Lanwench [MVP - Exchange]"
<[email protected]>
wrote in message
All servers and workstations should specify the internal
AD-integrated DNS server's IP address in their network
settings. The AD-integrated DNS server should be set up
with forwarders to several public DNS servers for external
resolution.

See
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202
for more info.

Per Hagstrom wrote:
Hey!

I think I know at least, that you are ONLY supposed to
enter your internal DNS server(s) on your workstations in
your network.

Our situation is that our DNS manager only has one DNS
server in the network. And all the clients uses it as
their primary DNS server AND the ISP's DNS servers as
their secondary...! (Due to DHCP) I informed that I
thought the best way is to ONLY have the internal DNS on
the clients and only let the DNS server itself do the
Forwarding to the ISP's DNS server. The reply back was
that if the internal DNS server goes down, workstations
can still resolve IP addresses on the internet, which I
guess is a point. (but not a good point?!) BUT we have
internal communication problems, where we have to do
IPCONFIG / FLUSHDNS all the time to be able to resolve
internal server names. My guess is that workstations
sometimes jumps to the secondary DNS, and ends up on the
ISP's DNS, and now of a sudden they can't resolve
internal names anymore...

Could someone please confirm this with me. Even give me a
link to a Microsoft Article or something so I can back it
up easier before I go to the manager again.

Thanks!!

/ Per Hagstrom

 

[Ace Fekay [MVP]]

In

Hey!

I think I know at least, that you are ONLY supposed to enter your
internal DNS server(s) on your workstations in your network.

Our situation is that our DNS manager only has one DNS server in the
network. And all the clients uses it as their primary DNS server AND
the ISP's DNS servers as their secondary...! (Due to DHCP)
I informed that I thought the best way is to ONLY have the internal
DNS on the clients and only let the DNS server itself do the
Forwarding to the ISP's DNS server.
The reply back was that if the internal DNS server goes down,
workstations can still resolve IP addresses on the internet, which I
guess is a point. (but not a good point?!)
BUT we have internal communication problems, where we have to do
IPCONFIG / FLUSHDNS all the time to be able to resolve internal
server names.
My guess is that workstations sometimes jumps to the secondary DNS,
and ends up on the ISP's DNS, and now of a sudden they can't resolve
internal names anymore...

Could someone please confirm this with me. Even give me a link to a
Microsoft Article or something so I can back it up easier before I go
to the manager again.

Thanks!!

/ Per Hagstrom

291382 - Frequently Asked Questions About Windows 2000 DNS and Windows
Server 2003 DNS:
http://support.microsoft.com/?id=291382

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

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

 

[Per Hagstrom]

That's a pretty good one in fact.. at least tells you; No! You shouldn't use
your ISP's DNS on the workstations...
I think I will try that!

Anyone knows how many DNS entries you can enter on a workstation and if they
all are effective or not?

Thanks a lot!

/ Per




"Ace Fekay [MVP]"

 

[Ace Fekay [MVP]]

In

That's a pretty good one in fact.. at least tells you; No! You
shouldn't use your ISP's DNS on the workstations...
I think I will try that!

Anyone knows how many DNS entries you can enter on a workstation and
if they all are effective or not?

Thanks a lot!

/ Per

No prob.

As many DNS servers as you want, but they all MUST be a DNS server that
hosts a copy of the AD zone info ONLY, for obvious reasons. Listing extras
is for fault tolerance only, not for different zone information. Use a
forwarder for efficient outside resolution.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

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

 

[TIM ROBERTS]

You are correct, Once the client get no answer from the DNS server it will
jump to the secondary DNS server listed and stay there. If the DNS manager
is worried about this then have him install a second DNS server. List this
in DHCP options 06. he has a very good point, but he also is forgetting that
if the internal DNS goes down that its better to resovle internal than
external. With current setup, logons would be slow to the domain. Its
really that old say rob paul to pay peter.
"Ace Fekay [MVP]"

 

[Ace Fekay [MVP]]

In

You are correct, Once the client get no answer from the DNS server it
will jump to the secondary DNS server listed and stay there. If the
DNS manager is worried about this then have him install a second DNS
server. List this in DHCP options 06. he has a very good point, but
he also is forgetting that if the internal DNS goes down that its
better to resovle internal than external. With current setup, logons
would be slow to the domain. Its really that old say rob paul to pay
peter. "Ace Fekay [MVP]"

Thanks for the confirmation Tim.
--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

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