Re: ISP DNS

Tech-Archive recommends: Fix windows errors by optimizing your registry

I haven't work with BIND but you could use it with ad as long as the BIND
version is 8.2.x or higher.

--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services
"Andrew M. Saucci, Jr." <spam-only@xxxxxxxxxxxxxxxx> wrote in message
news:Ou7EiaNyHHA.4260@xxxxxxxxxxxxxxxxxxxxxxx
Does anyone produce a DNS that will run on an XP or 2000
workstation-- or even a Linux box that will integrate with a Windows-based
network? One of the problems with a Windows 2003 Server-based DNS is that
the software alone is close to $1000 just for 5 users. Even if I put that
on
a recycled workstation, it's still more than this particular client will
want to spend (sigh again).

"Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx> wrote in message
news:eWXKRJKyHHA.1188@xxxxxxxxxxxxxxxxxxxxxxx
If loosing connection to AD and Internet is unacceptable, then you need a
good reduncy DNS strategy, that means more Internal DNS servers at the
site.
You don't need a great and expensive Server to do DNS queries for a
couple
of users.

Note: Of course that I agree that you shouldn't use your ISP or router as
secondary DNS and there are many reasons not to do it - Security,
internal
resolution problems, etc...

If your client doesn't want to spend more money then IMO they should know
the alternatives and the risks that they're facing with that option.

There's no suitable ServerPriorityTimeLimit value, if you decrease that
value you'll have other problem regarding to time to perform the DNS
resolution, the client machine must wait for an answer from the primary
DNS
and after the computer client checks that no primary DNS it passes the
query
to the secondary DNS, of course that this operation takes some time, and
if
you decrease that value to very low your Internet access may become slow.

--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services
"Andrew M. Saucci, Jr." <spam-only@xxxxxxxxxxxxxxxx> wrote in message
news:OLuUZI%23xHHA.2172@xxxxxxxxxxxxxxxxxxxxxxx
When it does fail, though, the results are simply unacceptable.
I've
sat at incorrectly configured workstations that are locked tight
because
the
DNS was set wrong. Can anyone recommend a suitable
ServerPriorityTimeLimit
value that will not ever lock up the workstation or cause other
problems?

"Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx> wrote in message
news:%23m$JWM8xHHA.2172@xxxxxxxxxxxxxxxxxxxxxxx
Not necessarily.
If this server fails to respond for any reason, the DNS client will
switch
to the server listed in the alternate DNS server entry. The DNS client
will
continue to use this alternate DNS server until: fails to respond to a
DNS
query, or The ServerPriorityTimeLimit value is reached (15 minutes by
default).
This behavior sometimes may fail but there's a workaround
http://support.microsoft.com/kb/320760/en-us


--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services
"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:uPWNBR7xHHA.4128@xxxxxxxxxxxxxxxxxxxxxxx
Jorge Silva <jorgesilva_pt@xxxxxxxxxxx> wrote:
Hi
If your solution only relies on internet access and no budget for a
second DNS server, you could add as Secondary DNS server the ISP
DNS
server for internet resolution.
Note:
The client will only use the secondary DNS server when there's NO
RESPONSE from the primary DNS server. Even if the primary DNS
server
"doesn't know" the answer for a given query, that query won't fall
back to the secondary as long as the Primary still answers with a
neg
answer.

And when there's a problem with the primary (e.g., the server is
being
rebooted, or the connection flickers out for long enough, etc., the
clients will flip over to the secondary, and will not try the
primary
again. So your AD will be a mess.




Jorge Silva
MCSE, MVP Directory Services
"Andrew M. Saucci, Jr." <spam-only@xxxxxxxxxxxxxxxx> wrote in
message
news:%23eXNxwoxHHA.312@xxxxxxxxxxxxxxxxxxxxxxx
I have a client with multiple locations but one domain
controller, at the main warehouse. The executive office is at a
different location. The
locations are interconnected with a frame relay network. All the
Internet access comes from the warehouse, except that the
executives
are considered important enough to have a second Internet
connection
from the executive office. Until recently, the domain controller
ran
NT 4, so the executive office simply used the DNS of the ISP for
name resolution and the NT 4 server didn't care.

The complaints started when I replaced the NT 4 server with
an
Windows 2003 server running AD. At that point I insisted that the
workstations in the executive office had to have the DNS of the DC
and _ONLY_ the DNS of the DC in their TCP/IP configuration, not
only
because it
is what everyone who is anyone will recommend, but also because I
have seen
enough problems with other configurations to know that this is
correct. The
DNS on the DC has the DNS of the warehouse ISP as forwarders. My
client insisted that he had to have the executive office ISP's DNS
listed somehow,
because otherwise the Internet in the executive office would fail
when the DC was down (which is absolutely true). Then yesterday,
another consultant came in for a special project and said that the
ISP's DNS could be listed as
an alternate (sigh).

I said that what is really needed is a second DC at the
executive office that would have the executive office ISP's DNS
listed as forwarders.
They don't want to spend the money even for a tiny server that
would
do this
(five people work in the executive office). Short of a second
server,
which
I absolutely know would solve this, and short of manually changing
the DNS settings when needed (won't fly), how else can the
executive
office continue
to use Internet when the DC is down for maintenance?













.

Relevant Pages

  • Re: Internet Speed
    ... I think what we are trying to say is to use the DHCP from the SBS and NOT ... DNS and WINS point to the SBS. ... as the server IP address. ... it is recommend to configure all SBS client computers' IP and DNS ...
    (microsoft.public.windows.server.sbs)
  • Re: 70-294 next week
    ... to another DNS ... server for at least ... client, which then ... configuration on the client. ...
    (microsoft.public.cert.exam.mcse)
  • Re: Dual NIC vs Single NIC
    ... |> 135919 DNS Server Search Order Functionality in Windows ... Thank you for helping me to correct the misunderstand of DNS query ... Thank you again for your supplement about the client DNS cache issue. ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: Dual NIC vs Single NIC
    ... I will again argue that turning off the client DNS cache (0 refresh ... 261968 Explanation of the Server List Management Feature in the Domain ... Internet when the SBS server is offline. ...
    (microsoft.public.windows.server.sbs)
  • RE: Dynamic Update of A&PTR Records - Best Practice?
    ... The DNS server does not support the DNS dynamic update protocol; ... For Windows Server 2003-based computers, the primary full computer name is ... When one of these events triggers a DNS update, the DHCP Client service, ...
    (microsoft.public.windows.server.dns)