I'm pretty sure it's not a caching issue I'm seeing.  DNS is working. I've
verified this by purging my DNS cache (IPCONFIG /FLUSHDNS), followed by
NSLOOKUP (which uses the configured ISP DNS). For example:

    >ipconfig /flushdns

    Windows IP Configuration

    Successfully flushed the DNS Resolver Cache.

    >nslookup navas.us
    *** Can't find server name for address 192.168.1.1: Non-existent domain
    *** Default servers are not available
    Server:  UnKnown
    Address:  192.168.1.1

    Non-authoritative answer:
    Name:    navas.us
    Address:  216.40.47.17

The apparent real problem is erratic lack of response by your HTTP Forwarder,
not DNS. For example, http://sail.navas.us/ sometimes works, but usually
doesn't (fails here about 80% of the time). (When it does work, you have to
clear the browser cache or restart the browser to see subsequent failures.)

The error I'm seeing in Firefox (1.5.0.3), after "Looking up sail.navas.us..."
(which succeeds) and "Connecting to sail.navas.us...", is:

    The connection has timed out
    The server at sail.navas.us is taking too long to respond.

Had it been a DNS failure, the error would have been:

    Server not found
    Firefox can't find the server at xsail.navas.us.

-John Navas

In <[EMAIL PROTECTED]> on Thu, 4 May
2006 15:51:58 -0400, "Greg Frank" <[EMAIL PROTECTED]> wrote:

>This is probably a caching issue.  We updated all glue records and expected
>it to take some time to propagate.  Only the IPs were affected, the
>redirection service was not modified.
>
>We are doing our best to contact service providers to expedite these
>changes.
>
>We checked the domains provided as well as the IP in the previous messages
>and they seem to be working now.  This is a hard problem to troubleshoot via
>email because by the time we receive the problem, there is a good chance
>that it has been resolved.
>
>Please let me know if you come across more of these and we will do some more
>troubleshooting.
>
>Greg Frank
>Product Manager, TLDs
>Tucows
>
>-----Original Message-----
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] Behalf Of dotregister
>Sent: Thursday, May 04, 2006 3:23 PM
>To: [email protected]
>Subject: Re: [domains-gen] Fallout continues: HTTP Forwarding often (but
>notalways) failing
>
>
>All those URL's are no go for me. Just thought I'd FYI. I am on SHAW COMM.
>here in Vancouver. DNS I use is 64.59.144.18 & .19
>
>GB
>_______________________________________________
>domains-gen mailing list
>[email protected]
>http://discuss.tucows.com/mailman/listinfo/domains-gen
>

_______________________________________________
domains-gen mailing list
[email protected]
http://discuss.tucows.com/mailman/listinfo/domains-gen

Reply via email to