Cant resolve dns names

[glenna]

Hi,

I have some problem here regarding DNS names wont resolve. Some hosts do resolve from the DNS but some dont, and all of the hosts use the same DNS server(s). Dont find any error messages anywhere either so cant really progress atm.

Anyone have any clue on what to do?

Best regards,
Glenn

[dalet0]

Hi Glenn,

I would try increasing the "DNS Timeout" value under Admin->Settings->System Preferences.

What version of scrutinizer are you running?

Danny

[glenna]

Hi Danny,

I'm using Scrutinizer 8.5 now, was told to upgrade cause of some problems solved in that version with DNS.

I increased the timeout to an extensive 60sec now, i know it's probably overkill but i just want to be sure now that it aint that option.

So if the timeout wont fix my problem what could cause it then?

Best regards,

Glenn

[mkrygeri]

Hi Glenna,
Occasionally, we see a problem with DNS due to a problem with the registry. Please try the following and see if this resolves your issue.
1. Create a file in the \scrutinizer\html directory called dns.conf.
2. Open this file with a text editor like Notepad.
3. Create a list of DNS servers in the file in the format below.
nameserver 192.168.1.1
nameserver 166.186.184.2
nameserver 224.39.1.171

Once this file has been created, try again. Let us know if this solved youe issue.

Mike K

[glenna]

Hi Mike,

Tried that also, but no progress yet

It is so wierd cause from the machine itself it do not have any problem resolving the dns names, so probably something within the program. The option to see dns names aint criticall but would be easier when solving network issues to right away have the hostname instead of looking it up manually.

Best regards,
Glenn

[jghidoni]

Hi Glenn,

Can you do a test for us and try placing a copy of your dns.conf file in the following 2 directories, then let us know if the dns resolve works?

[homedir]\scrutinizer\cgi-bin
[homedir]\scrutinizer\bin

Thank you,
Joanne

[glenna]

Hi Joanne,

Even that did not solve the problem it seems :/

Now i started to resolve the dns names manually from the Admin -> Definitions -> Host names option.
Most top host names are usually the same but o course the procedure is kinda time consuming.

But putting the dns.conf file in those 3 directorys did not work, atleast not for me.

Best regards,
Glenn

[tomp]

Hi Glenn,

Do you have time to chat? Please email me at tomp@plixer.com. I'd like to set up a GoToMeeting and take a look around.

- Tom

[glenna]

Hi Tom,

That with putting the dns.conf into the previous mentioned directorys seems to helped, almost fully!
Rest of it i can manually do, cause there are some specific things happening on the net here.

But now i have some more "problems" but that maybe i can take on mail with you, so ill go ahead and send you an emal.

Thanks to you all with helping with the dns problem!

Best regards,
Glenn

[jscheller]

Just downloaded a trial and am also having trouble resolving IPs to DNS. Nslookup works properly from the host and responds quickly. I have increased the DNS timeout to 30 seconds and added the dns.conf file to the directories referenced earlier in the post but no luck. Any ideas?

[pauld]

Hello jscheller,

We've made some improvements to DNS for v8.6.2; can you verify that you're v8.6.2?

Are you doing the nslookup from the Scrutinizer server?

You shouldn't need to use the dns.conf file unless you're trying to query from multiple DNS servers which typically means the DNS server is not properly configured to relay DNS requests to the proper servers.

If you're running v8.6.2 and doing a nslookup from the Scrutinizer server works, I would recommend contacting our pre-sales support at 207-324-8805 so we can investigate this further.

Thanks,
Paul

[jscheller]

I am running 8.6.2. Guess I will call.