Re: External resolve / internal don't

From: Deji Akomolafe (deji_at_REMOVEPADDINGakomolafedotcom)
Date: 07/30/04


Date: Thu, 29 Jul 2004 21:35:40 -0700

What does nslookup on the clients show?
If you try pinging internal names with a "." at the end (e.g. clientA.),
does it resolve then? If it does, you may have suffix issues. Try adding
your internal domain names to the "append these DNS suffixes..." option in
TCP/IP. Then net stop and net start dnscache and test again.

Lastly, since you have multiple DNS servers, it would be helpful if you
could describe how they are configured, both in TCP/IP and in DNS
properties.

-- 
Sincerely,
Dèjì Akómöláfé, MCSE MCSA MCP+I
Microsoft MVP - Directory Services
www.readymaids.com - COMPLETE SPAM Protection
www.akomolafe.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday?  -anon
"Geraint" <anonymous@discussions.microsoft.com> wrote in message
news:6c1101c475aa$596ea4d0$a401280a@phx.gbl...
> We have a domain running over a WAN with each subnet
> containing it's own DC and DNS server.  All on Win 2k SP3.
> Just recently one of the subnets is experiencing
> following problem:
> Clients can resolve external names and FQDN for internal
> computers but not the short internal names, (they used to
> resolve OK).
> The DNS server itself can resolve short internal names.
>
> Nothing has changed on this server that I know of and no
> errors are reported in the event logs.  I have re-
> installed DNS on this server but still the same.
> The server is multi-homed with one card to the DSL router
> and one to internal LAN.  Both are set up as per MS
> recommendations for multi-homed.
> Other info:
> DHCP is set up for clients, supplying internal and
> external DNS servers. DHCP working OK (ipconfig/all OK).
> All required records are present in DNS forward/reverse
> lookup zones.
> DNS has forwarding set up for 2 external DNS's.
> DNS listening on both cards (I know not recommended but
> we have this set on all our DNS's as they don't work
> unless we do!).
>
> It looks like DNS is just not reading the records in the
> forward lookup zone  (out of date/not valid???).
>
> Any ideas.
>
> Geraint
>
>


Relevant Pages

  • Re: NS and domain A record affecting AD
    ... Clients are pointing to the local dc for both WINS and DNS, ... If the remote dc's are on a slow link you may not even get your gpo's ... If local clients can not resolve AD domain name to ...
    (microsoft.public.windows.server.active_directory)
  • Re: How to set up Clients with...
    ... The only place foreign DNS servers ... > the Clients need to have the SBS server as their primary DNS server.. ... >>> join any windows domain including an SBS domain. ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN Client Name Resolution
    ... Yes, the vpn/ras clients get a dhcp assigned ip address, ... dns address, etc. ... internal DNS server. ... They try to resolve the name to the external ...
    (microsoft.public.win2000.ras_routing)
  • Re: Drive Mapping Issues in Win2K AD, DNS related?
    ... We have tried connecting via NetBIOS name and ... DNS appears to resolve the host names ... If the clients are W2k or newer, then is DNS resolving and do the SRV ...
    (microsoft.public.win2000.active_directory)
  • Re: Drive Mapping Issues in Win2K AD, DNS related?
    ... We have tried connecting via NetBIOS name and ... DNS appears to resolve the host names ... If the clients are W2k or newer, then is DNS resolving and do the SRV ...
    (microsoft.public.win2000.dns)

Loading