Tom's Guide | Tom's Hardware | Tom's Games

Computing.Net > Forums > Windows Server 2003 > DNS problem

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

DNS problem

Reply to Message Icon

Name: kiwi_hk
Date: February 11, 2007 at 22:03:25 Pacific
OS: Windows 2003
CPU/Ram: 2G
Comment:

Hi

We have a windows 2003 server with DNS setup and ad intergated zone. When I do a nslookup on some client's machines I get an error can't resolve the name. Non-existent domain.

Is there a problem with our dns server, how to fix this?

Thanks



Sponsored Link
Ads by Google

Response Number 1
Name: wanderer
Date: February 12, 2007 at 06:16:20 Pacific
Reply:

is the client in your zone?
on the internet?
does your dns server forward requests to your isps dns server?

Knowing the correct answer and giving a correct answer, are two different things


0

Response Number 2
Name: kiwi_hk
Date: February 12, 2007 at 07:51:59 Pacific
Reply:

Yes, internal DNS forward to ISP dns, client is on the same domain as the Window2003 server with DNS.


0

Response Number 3
Name: wanderer
Date: February 12, 2007 at 10:38:08 Pacific
Reply:

is the client machine listed in the forward lookup zone?
what does the client list for dns server? ISP or MS server?

Give a person a fish, they eat for a day. Suggest they internet search and they learn a skill for a lifetime.


0

Response Number 4
Name: kiwi_hk
Date: February 12, 2007 at 18:54:55 Pacific
Reply:

Client's machine primary DNS is set to our DNS Windows 2003 DC server and secondary is set to our other DNS windows 2003 DC server.

IT's is not listed in the forward or reverse lookup zone. I have gone to the client's machine and have ipconfig /registerdns.

I have also read somewhere I need to setup the 2 DNS to make each other point to the other as primary DNS but not sure what they mean, it's just setup as Active directory intergated, replicate to all DC on the AD domain.


0

Response Number 5
Name: Glen
Date: February 13, 2007 at 15:57:44 Pacific
Reply:

This message usually comes from a non-existent reverse lookup record. (PTR Record)

In a Windows 2003 domain you can have the DC's point to themselves as their preferred DNS server - assuming the DCs are in fact DNS servers. In previous versions of Windows, DNS could suffer from what is called "islanding".

Make sure there is a PTR record for the clients and that the correct PTR record is there for your servers also.



0

Related Posts

See More



Response Number 6
Name: kiwi_hk
Date: February 13, 2007 at 18:42:45 Pacific
Reply:

Yes, I have the DC pointed to themselves as the DNS server, also there is no PTR records of some clients even after I did a ipconfig /registerdns on the client'
s machine. THe DC/DNS should auto this record. Maybe I should just delete everything and start again.

Any ideas how to delete all the dns records and reinstall dns on the 2 DC. I think this time instead of replications to all DC AD, I should change to all DNS in AD.


0

Response Number 7
Name: Glen
Date: February 15, 2007 at 13:02:03 Pacific
Reply:

I don't think you need to reinstall DNS. Try manually making a pointer record for the DNS and DC servers. That should eliminate your error message.


0

Sponsored Link
Ads by Google
Reply to Message Icon



Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows Server 2003 Forum Home


Sponsored links
Ads by Google


Results for: DNS problem
DNS problem www.computing.net/answers/windows-2003/dns-problem/6616.html

dns problem www.computing.net/answers/windows-2003/dns-problem-/3649.html

DNS Problem www.computing.net/answers/windows-2003/dns-problem/7772.html