I did join my XP clients to the domain. I could ping them via their NetBios
name (mobile1, mobile2) but not using FQDN (mobile1.office.kelly.net,
mobile2.office.kelly.net).
I remember that Dynamic updates may have been grayed out during the DNS
process.
Is their a preferred order of install when setting up a DC with DHCP and DNS?
Should I do DNS first manually or just doing it with AD installation? Should
I do DHCP before or after AD and/or DNS?
Could I use the process I described to setup a SOHO, and would it be
considered practical or good practice? If not, what do I need to change for
"best practice" install?
Any help would be appreciated.
"pestocat" wrote:
> Kelly,
> Try this reference
> http://support.microsoft.com/default...b;en-us;323380 It gives you
> all the setup instructions you need. It help me.
>
>
> "kelly" <(E-Mail Removed)> wrote in message
> news:34F75E59-EE28-4D44-B2F5-(E-Mail Removed)...
> > DHCP rolled out fine
> > Clients were able to talk via ping
> > Clients were able to get out to internet using gateway
> > Clients could not ping using FQDN
> > What do you think of my overall strategy? What do I need to change? How
> > can
> > I tell if DNS is working for sure? I am assuming that since I do not get a
> > reply using FQDN that DNS is not working.
> >
> > Would it be correct to say that my DNS server is authoritative for the
> > "office.kelly.net" zone, while my ISP will be authoritative for the
> > "Kelly.net" zone?
> >
> > I guess my goal is that my DNS server resolve all internal addressing, and
> > at the same time forwarding all unresolved addressing to my ISP's DNS
> > through
> > forwarders. Sound right?
> > Thanks!
> >
>
>
>