Let's say your /var/log/messages is filling up with a whole lot of this:
Oct 5 05:00:08 server named[3044]: lame server resolving 'api.widget.com.example.com' (in 'example.com'?): 111.222.333.444#53 Oct 5 05:00:08 server named[3044]: lame server resolving 'www.ip-adress.com.example.com' (in 'example.com'?): 111.222.333.444#53 Oct 5 05:00:08 server named[3044]: lame server resolving 'api.widgetbucks.com.example.com' (in 'example.com'?): 111.222.333.444#53 Oct 5 05:00:08 server named[3044]: lame server resolving 'api.widgetbucks.com.example.com' (in 'example.com'?): 111.222.333.444#53 Oct 5 05:00:08 server named[3044]: lame server resolving 'ad.yieldmanager.com.example.com' (in 'example.com'?): 111.222.333.444#53 Oct 5 05:00:08 server named[3044]: lame server resolving 's.us6.us.example.com' (in 'example.com'?): 111.222.333.444#53 Oct 5 05:00:08 server named[3044]: lame server resolving 'i113.imagethrust.com.example.com' (in 'example.com'?): 111.222.333.444#53 Oct 5 05:00:08 server named[3044]: lame server resolving 'api.widgetbucks.com.example.com' (in 'example.com'?): 111.222.333.444#53 Oct 5 05:00:08 server named[3044]: lame server resolving 'api.widgetbucks.com.example.com' (in 'example.com'?): 111.222.333.444#53 Oct 5 05:00:08 server named[3044]: lame server resolving 'partner.gonamic.de.example.com' (in 'example.com'?): 111.222.333.444#53 Oct 5 05:00:08 server named[3044]: lame server resolving 's.us6.us.example.com' (in 'example.com'?): 111.222.333.444#53 Oct 5 05:00:08 server named[3044]: lame server resolving 'api.widgetbucks.com.example.com' (in 'example.com'?): 111.222.333.444#53
Well, what's happening here? Basically your server is having a hard time resolving those domain names, "api.widgetbucks.com.example.com", "s.us6.us.example.com". It's probably having a hard time resolving any domain names.
The first thing you want to check is your /etc/resolv.conf file. If Sago's nameservers aren't in there, add them.
nameserver 66.118.170.2 nameserver 66.118.170.3
If you're 100% sure you don't want to use our nameservers, then you have to make sure your own server is usable as a caching nameserver. If it's a Debian or Ubuntu server, you'll want to install lwresd
apt-get install lwresd
This is the Light Weight Resolver Daemon, it is basically a stripped down copy of Bind just for use as a caching resolver for your server.
If it's a CentOS, Fedora or OpenSUSE server, make sure you have named installed and your firewall allows at least your server to access port 53 UDP.
If all goes well, you should be able to login to your server and run this command and see similar results.
[root@server log]# host google.com localhost Using domain server: Name: localhost Address: 127.0.0.1#53 Aliases: google.com has address 209.85.171.99 google.com has address 64.233.187.99 google.com has address 72.14.207.99
