On Tue, Oct 27, 2009 at 6:19 PM, Didtel, Larry <[email protected]> wrote: > Yes, from local pc I have to /flushdns /registerdns then it works for a short > time.
It's possible the client PC is caching a negative answer. > The address is //stemilt.gousa1.com. Here's what I see: <stemilt.gousa1.com.> has a single resource record, CNAME type, with a TTL of 1200 (20 minutes). The RHS (right hand side) of the CNAME RR is <5qods.wrfe2.servertrust.com.>. <5qods.wrfe2.servertrust.com.> has a single RR, A type, with a TTL of 900 (15 minutes). The RHS of the A RR is <69.162.233.206>. Compare my results to yours. Test resolution of the above names, and test connectivity to the above IP address. The nameservers at <ns1.apcap.net.> and <ns2.apcap.net.> have been delegated authority for <gousa1.com.>. However, they are claiming authority for the entire <.com> zone (i.e., most of the Internet). While I don't think that is directly relevant to your problem, it is a sign that those nameservers are broken. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
