[SATLUG] access to FreeNode (or IRC in general) from GVTC's network

Greg Swift gregswift at gmail.com
Tue Dec 13 14:13:32 CST 2011


On Tue, Dec 13, 2011 at 11:55, Bruce Dubbs <bruce.dubbs at gmail.com> wrote:

> mark wrote:
>
>> I'm on GVTC but I do not really do irc. I was able to connect to the
>> freenode via internet based webclient. I was also able to do a
>> traceroute via port 6665 on irc.freenode.net but when I tried to connect
>> via xchat-gnome it just sat there connecting. It gave a couldn't lookup
>> your hostname error. It did eventually connect but it took a while. I
>> know the GVTC DNS servers went down the other day for a few hours. Maybe
>> they are still having DNS issues. I have noticed a network quality
>> degradation (delays in locating websites) ever since they started having
>> DNS issues.
>>
>
> If it is a DNS issue, edit your /etc/resolv.conf and use:
>
> nameserver 8.8.4.4
> nameserver 8.8.8.8
>
> That's google.  I'm on Time-Warner and get the following for
> irc.freenode.net:
>
> $ dig irc.freenode.net
>
> ; <<>> DiG 9.3.3 <<>> irc.freenode.net
> ;; global options:  printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7619
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 17, AUTHORITY: 0, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;irc.freenode.net.              IN      A
>
> ;; ANSWER SECTION:
> irc.freenode.net.       26629   IN      CNAME   chat.freenode.net.
> chat.freenode.net.      22      IN      A       94.125.182.252
> chat.freenode.net.      22      IN      A       208.71.169.36
> chat.freenode.net.      22      IN      A       174.143.119.91
> chat.freenode.net.      22      IN      A       213.92.8.4
> chat.freenode.net.      22      IN      A       38.229.70.20
> chat.freenode.net.      22      IN      A       93.152.160.101
> chat.freenode.net.      22      IN      A       213.232.93.3
> chat.freenode.net.      22      IN      A       128.237.157.136
> chat.freenode.net.      22      IN      A       82.96.64.4
> chat.freenode.net.      22      IN      A       130.239.18.172
> chat.freenode.net.      22      IN      A       140.211.167.98
> chat.freenode.net.      22      IN      A       86.65.39.15
> chat.freenode.net.      22      IN      A       193.219.128.49
> chat.freenode.net.      22      IN      A       216.155.130.130
> chat.freenode.net.      22      IN      A       89.16.176.16
> chat.freenode.net.      22      IN      A       140.211.167.99
>

There isn't an issue resolving freenode's DNS entries.  But using google's
DNS would have bypassed GVTC's DNS crash the other day.  That being said,
their DNS caching works fine when its running.


More information about the SATLUG mailing list