J
jim
-----Original Message----- restarting DNS,
since to that interface.
AS after all, you
even sit on for others
to
That's what I indicated to you originally -- so really the
courseware (based on what you say above) doesn't address
the issue of multiple NICs.
And if you think it through a bit there could even be NICs that
don't support DNS -- the only thing the courseware (likely) refers
to is those NICs which will answer DNS queries.
There is NOTHING wrong with using a dynamic address for the
DNS server to forward requests, perform actual recursion itself,or
for other purposes than DNS.
It just won't "serve" on those dynamic IPs -- it actually can do that,
but it doesn't make much sense.
This guys problem is likely that his ISP is invalidating a LEGITIMATE
lease before it expires and then telling him that it is "his problem."
Thanks so much for your help, but I'm not near as
technically savvy as you are and am kindof lost. What
exactly is the "lease" and how do I fix this or what do I
tell my ISP? Appreciate it.
private MCTSure there are errors in the courseware, but
they work themselves out thru the trainers submitting errors to the error
log which we usually check for an update or thru our
newsgroup.
It's not that useful to use them blindly as a "reference" however.
--
Herb Martin
"Ace Fekay [MVP]"
message news:[email protected]...thoughts, then I offeredIn Herb Martin <[email protected]> posted their
minerestarting DNS,Well, one of the requirements of DNS is a static IP for proper
functionality. You're probably aware of this being familiar with the
courseware.
If it says this in the courseware it's just silly -- we are talking
about multiple NICs. More likely it says, or at least means, static
for the NIC on which DNS will operate.
[One of the reasons I seldom use the courseware.]
I see what you mean in your previous post. If the IP during that
lease time is being used by DNS, but when it changes, the DNS
service needs to be restarted to recognize the change and bind to
that interface.
It's probably not even DNS (maybe) but rather somehow re-starting
DNS was causing the DHCP client to renew -- IF it's doing what
I believe seems fairly clear.
E.G.: He has a 2 day lease; the cable modem (or DHCP server) re-inits
and loses the lease. Now his address is invalid but he has a
legitimate right to keep using it -- and NO REASON to renew.
The tip-off hear is that renewing the DHCP lease fixes his problem
without having to restart DNS.
I agree that renewing the lease will fix it instead of
sinceto that interface.it only makes sense, and at that point, DNS will bind
ASafter all, youfor the courseware, it loosely says it's a requirement,
evensit on for othersstated, we should have a consistent address for DNS to
toprivate MCTbe able to use the machine. Sure there are errors in the courseware, but
they work themselves out thru the trainers submitting errors to the error
log which we usually check for an update or thru our
newsgroup.So the courseware is good to use.
--
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
.