WHM Autopilot Resolve Server

[djshaw]

I have searched the forum but can't find any info on this. Can anyone tell me the IP address of a remote DNS server I can use in the Autopilot setup? Perhaps the hostgator DNS server?

I'm just not sure what to enter in this field.

Thanks

[gtgeorge]

I use my isp's dns server...the same one I use all day long

[chaloupe]

For the resolve server?


Best regards,

[gtgeorge]

Originally Posted by chaloupe

For the resolve server?


Best regards,

Yes, it's what i use.

[chaloupe]

Nice, didn't know that.

I've ask Hostgator about a month ago and they sent me this one for Main Resolver Configuration in WHM.Autopilot:

Resolver Functionality: Use "gethostbyname" for resolve check
Resolve Server: 216.234.234.30

Best regards,

[WHMAutoPilot]

As a side note on the resolver, it helps to understand what the utility does so that you can better understand the settings.

[1] Auto-Resolve
=> this option does NO checking of the domain to see if the domain is resolving. It will automatically mark the domain as resolved and send out EMID 2 upon first run of the cron_resolver.php

[2] Using gethostbyname() as the option
=> This option uses the servers utility gethostbyname $domain to pull back the results of what some are familiar with when they perform a DIG command. The script parses the results provided and matches the IP giving in the gethostbyname to the IP in the hosting order. If there is a match, the domain "looks" to be resolved by the script. This function does NOT use the IP address you input.

This can provide false results if the domain is installed on the same server as AutoPilot since gethostbyname results are localhost lookups first, it will pull the local DNS record off the server for the results, giving false results.

[3] nslookup is the most reliable, if that function is actively working on the server. What this option does is it bounces the nslookup command off the IP address provided ( which should NOT be an IP on the same server ) to get outside results looking in for the lookup on the domain. This option has been 99% accurate since the results are pulled outside of your network and provides the exact results of that domain.

In todays world of 8 hour or less resolve time after updating nameservers, some have seen this utility to be "not needed" but, there are always those clients who wait 4 days to update nameservers and need that little reminder that their domain 'has not resolve' and requires attention.

Thanks.

[chaloupe]

Thank you WHMAutoPilot

That is the perfect answer I was looking for the Resolve Server Function!

So I would change my option from gethostbyname to nslookup for better resolve results?!

[methodprobiz]

Originally Posted by WHMAutoPilot

[3] nslookup is the most reliable, if that function is actively working on the server. What this option does is it bounces the nslookup command off the IP address provided ( which should NOT be an IP on the same server ) to get outside results looking in for the lookup on the domain. This option has been 99% accurate since the results are pulled outside of your network and provides the exact results of that domain.

What is the rule in knowing what IP to use for 'nslookup' in the Resolver Server configuration for HostGator? The WHMAutoPilot Forums give several options, all lead to a CPANEL message of a site that doesnt exist. Maybe that's all that is needed in the process, but I would like to know for sure.

Thanks in advance to the responder that is willing to coach