Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Help, sysquery: findns error

Status
Not open for further replies.

solomonsweb

Technical User
Aug 21, 2003
4
US
This is the error I'm getting in my app log in the event viewer.

sysquery: findns error (NXDOMAIN) on ns1.solomonsweb.com?

I have 2,389 errors in 5 days, what is it? any ideas?

Thanks for your help,
Tom
tom@solomonsweb.com
 
Your name server found NS records which pointed at ns1.solomonsweb.com but when it looked up these names, your server found that they didn't exist. [The lookups got NXDOMAIN errors - "no such host/domain" - returned.] The duplicate log messages can be explained by your name server making more than one lookup for these name.

If you recently made changes to your DNS you may have forgotten to update the zone files so that they didn't have NS records for ns1.solomonsweb.com after you moved their name servers. If ns1.solomonsweb.com were slave (secondary) servers for some zones, you have to get the hostmasters for these zone to fix them. Check your zone files and name server config files.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top