Archived from groups: microsoft.public.win2000.dns (
More info?)
Thanks so much for your time and Patience !! I may
actually be getting it.
>-----Original Message-----
>"Dave McDuell" <anonymous@discussions.microsoft.com>
wrote in message
>news:1fc9001c4589c$984d6d10$a301280a@phx.gbl...
>> Thanks for all the info. I'm a little confused by what
>> seems to a 2 conflicting staements, though. In the
first
>> part of my oringinal post, I say I have 2 dns entries in
>> each client -- one set to my local dns server and one
set
>> to my isp's dns server. Your response is that clients
>> should be "configured as above".
>
>As above in "my explantion": The local DNS ONLY,
>leave out the ISP.
>
>Sorry for the confusion.
>
>> Later you state that clients should only point to
internal
>> dns server set. If this is true then the clients use
the
>> forwarders configured on the internal dns server set to
>> resolve names not found directly on the internal dns
>> server set ??
>
>Maybe I moved the paragraphs around trying to make it
>more clear and screwed it up.
>
>> It seems dns can take 10 words to explain and a lifetime
>> to master.
>
>Actually, when you "get it" you get it. The weird thing
>about DNS is actually the opposite -- with the GUI it is
>so easy to get simple setups correct that many people who
>don't really understand it thing that they do.
>
>I know this was true for me -- the first time I ever
played
>with DNS I used the MS GUI and 20 minutes later had
>a production setup working.
>
>Boy did I have a lot to learn, but none of it was really
that
>hard.
>
>--
>Herb Martin
>
>
>>
>> Thanks
>>
>>
>> >-----Original Message-----
>> >"Dave McDuell" <anonymous@discussions.microsoft.com>
>> wrote in message
>> >news:1f7fa01c457d3$6b0bd4f0$a401280a@phx.gbl...
>> >> This may be same or similar to other post-sorry.
>> >>
>> >> I have a dns server on my network which has entries
>> >> for "local" servers. I have 2 dns entries in my
client
>> >> network setup, one for the local dns server and one
for
>> my
>> >> isp's.
>> >
>> >All internal clients should be configures as above.
>> >
>> >>If I put the isp dns entry as my primary one, I
>> >> can't ping local servers by their full dns names.
If I
>> >
>> >And this will occur unles the INTERNAL servers are
>> >configured to use the ISP DNS (or equivalent external
>> >DNS servers) as FORWARDERS.
>> >
>> >> move my local dns server up to the top, I can ping
OK.
>> >
>> >Don't do that -- even though it "seems" to work it is
>> >unreliably and the source of many "intermittant
errors",
>> >often giving admins the mistaken impression that name
>> >resolution or Active Directory are unreliable since
they
>> >don't understand the real problem.
>> >
>> >> Why is this ? I thought if the primary one cannot
>> resolve
>> >> the name, the client would try the second one ??
>> >
>> >No. Clients assume that EVERY DNS server will return
>> >the same -- and the correct -- answer, even if that
>> is "Name
>> >not found." (aka, negative response.)
>> >
>> >> If the answer is to delete the "." entry in my
forward
>> >> lookup zones and put forwarder info there, I don't
see
>> >> a "." entry. Or is the "." entry a generic term for
>> >> something else ??
>> >
>> >If you don't have a "." root zone on your DNS servers
then
>> >you can skip that step and just configure the FORWARDER
>> >property sheet.
>> >
>> >Those who have the "." zone (yes, literally that name)
>> have
>> >their forwarders configuration GREYED out and DISABLED.
>> >
>> >If yours is enable then you can just configure it.
>> >
>> >While we are on the subject, make sure that ALL of your
>> >clients are configured to point ONLY to the internal
DNS
>> >server (set).
>> >
>> >Clients include DCs, DNS servers themselves, and in
other
>> >"internal server."
>> >
>> >(Even my ISA box which is part of my firewall is
>> a "member"
>> >machine of the internal domain and must override the
>> automatic
>> >setting it gets from the ISP when it does DHCP client
>> etc...)
>> >
>> >
>> >
>> >
>> >--
>> >Herb Martin
>> >
>> >
>> >>
>> >> Thanks
>> >
>> >
>> >.
>> >
>
>
>.
>
Facebook
Twitter
Instagram