DNS not working

  • Thread starter Thread starter Dan LaJoie
  • Start date Start date
D

Dan LaJoie

When we put the IP address of the DNS server in our client
machines, the client can not access the internet. We we
add the IP providers DNS addresses as a second DNS
address, the client can access the internet but some XP
client intemitiantly can not log into the server and get a
DNS error message.

We looked at the DNS settings and they seem to be ok but
we must be missing something. Is there any suggestion as
to how to diagnose this problem and fix this problem.

Thanks for the help
 
Point all clients to internal dns only (i.e. not also to isp). Your
internal dns should then forward and/or use root-hints to get INET rez. Use
dig or nslookup to direct queries at your dns server to see if it is
forwarding to INET. Could be no forwarders setup, or wrong forwarders, or
network/firewall issue, etc.
 
Hi Dan,
In Your DNS Server, Under for Lookup Zone, do you have a "." zone listed?
Can the DNS server itself get out to the internet? Do you have a signle
Label Domain name? Do you have a Disjoined Domain Name?

Single label Domain Name (SP4 installed on the server or windows 2000
professional or Winxp)
Right click my computer, then properties, then Network Identification.
Example of a single label domain domain:
FCN: xyz.mydomain
Domain: mydomain

How to fix this: Information About Configuring Windows 2000 for Domains With
Single-Label DNS Names 300684

Example of a Disjoined name space:
FCN: xyz.mydomain.
Domain: mydomain.local

Disjoined name space can be taken care of with a script Send me email and I
will send you the script

Here are some things to check on the dns server.

1) Go to a command prompt, type nslookup, then hit enter, the type set
type=all, then hit enter, then type ty.com. You should see this information
or some thing like it.
Non-authoritative answer:
ty.com internet address = 66.150.102.30
ty.com nameserver = ns2.mydyndns.org
ty.com nameserver = ns3.mydyndns.org
ty.com nameserver = ns4.mydyndns.org
ty.com nameserver = ns5.mydyndns.org
ty.com nameserver = ns1.mydyndns.org

ty.com nameserver = ns2.mydyndns.org
ty.com nameserver = ns3.mydyndns.org
ty.com nameserver = ns4.mydyndns.org
ty.com nameserver = ns5.mydyndns.org
ty.com nameserver = ns1.mydyndns.org
ns1.mydyndns.org internet address = 66.151.188.45

If you can resolve from the server the client will never be able too. If the
above doesn't work. Check to see if your setting on the router firewall are
allowing DNS out. Make sure TCP and UDP. You may also have a access list and
the server may not be defind.

2) check to see if there is a "." zone, if so remove it
3) Then run net stop netlogon and net start net logon from a command line.
4) Check to see if forwarders are configured, if not con figure them to you
ISP DNS Servers.
5)Under for Lookup Zone, right click then properties, are Dynamic updates
set to yes?
6) If everything is ok, Then open the DNS MMC and right click the server
name and go to logging. Check everything here.
7) Point the client to the dns sever, and do a query to the internet, review
the logs
8) Take netmon trace while doing this
9) Check to make sure that on the network card of the server, in advanced,
under Wins tab, that enable Netbios over TCP/IP is set. Check the client for
this too.

The client may also have the suffix for the domain wrong so check that.

I hope this help

Tim Roberts (MSFT)
 
Delete the "." zone in forward lookup zones on your DNS server. Point internal clients to internal DNS only. Restart the DNS service and clients should have
Internet access.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
 
Back
Top