That may have been the case when we were having data centre problems, but all should be proper now.
Do you use static DNS assignment or dynamic (from ISP)? If you're using dynamic, you should be able to resolve on all sites. If not, please post some traceroutes here so I can take a look (and please mark which ones are tested using which DNS). If that's a bit too much to paste on a forum (not always image friendly) please drop me a mail on [email protected].
I've been using dynamic, which assigns 196.7.7.7 and 196.7.8.9 for DNS. I've manually set Google's public DNS as a temporary workaround.
www.gerbergear.com is one of the sites that doesn't resolve at the moment
When using 196.7.7.7:
nslookup
> www.gerbergear.com
Server: UnKnown
Address: 196.7.7.7
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
> www.google.com
Server: UnKnown
Address: 196.7.7.7
Non-authoritative answer:
Name: www.google.com
Addresses: 2c0f:fb50:4002:803::2004
216.58.223.36
traceroute fails - "Unable to resolve target system name www.gerbergear.com"
when using Google's DNS:
nslookup
> www.gerbergear.com
Server: google-public-dns-a.google.com
Address: 8.8.8.8
Non-authoritative answer:
Name: www.gerbergear.com
Address: 24.177.133.159
> www.google.com
Server: google-public-dns-a.google.com
Address: 8.8.8.8
Non-authoritative answer:
Name: www.google.com
Addresses: 2c0f:fb50:4002:803::2004
66.8.14.27
66.8.14.16
66.8.14.20
66.8.14.59
66.8.14.46
66.8.14.38
66.8.14.49
66.8.14.42
66.8.14.31
66.8.14.26
66.8.14.48
66.8.14.37
66.8.14.53
66.8.14.24
66.8.14.35
66.8.14.57
traceroute works "Tracing route to www.gerbergear.com [24.177.133.159]"
This is definitely related to DNS on 196.7.7.7 and 196.7.8.9