I've been happily using Trinity for a couple of weeks, and needed to reinstall it after changing distros -- but the GPG keyserver (command copied from instructions) is coming up as host not found. Here's what I get from a nslookup:
Server: 156.154.71.16 Address: 156.154.71.16#53 ** server can't find keyserver.quickbuild.pearsoncomputing.net: NXDOMAIN
PS. Thank you (to anyone working on the project) for creating, working on, and hosting Trinity. I first installed Linux in Spring 2008 and KDE 3 was what made me fall in love with it!
| I've been happily using Trinity for a couple of weeks, and needed to | reinstall it after changing distros -- but the GPG keyserver (command | copied from instructions) is coming up as host not found. Here's what | I get from a nslookup: | | Server: 156.154.71.16 | Address: 156.154.71.16#53 | ** server can't find keyserver.quickbuild.pearsoncomputing.net: NXDOMAIN
keyserver.quickbuild.pearsoncomputing.net. 1D IN A 74.84.118.181
Open /etc/hosts and put the following lines there:
74.84.118.181 keyserver.quickbuild.pearsoncomputing.net 74.84.118.181 quickbuild.pearsoncomputing.net
| I've been happily using Trinity for a couple of weeks, and needed to | reinstall it after changing distros -- but the GPG keyserver (command | copied from instructions) is coming up as host not found. Here's what | I get from a nslookup: | | Server: 156.154.71.16 | Address: 156.154.71.16#53 | ** server can't find keyserver.quickbuild.pearsoncomputing.net: NXDOMAIN
keyserver.quickbuild.pearsoncomputing.net. 1D IN A 74.84.118.181
Open /etc/hosts and put the following lines there:
74.84.118.181 keyserver.quickbuild.pearsoncomputing.net 74.84.118.181 quickbuild.pearsoncomputing.net
Not a good idea! I can change the IP address I have assigned to this project without warning for a variety of reasons...
What I don't understand is that an invalid DNS cache for *.quickbuild.pearsoncomputing.net has been floating around the Internet. I would suggest giving it a couple days and trying again. If the problem persists then please let me know.
I would also be interested in the output of
nslookup quickbuild.pearsoncomputing.net
Thanks!
Tim
On Wed, 27 Apr 2011 11:43:47 -0500 Timothy Pearson wrote:
nslookup quickbuild.pearsoncomputing.net
From New Zealand
[lists@amd64: Lotr]$ nslookup quickbuild.pearsoncomputing.net Server: 203.97.33.14 Address: 203.97.33.14#53
Non-authoritative answer: Name: quickbuild.pearsoncomputing.net Address: 74.84.118.181
John
On Wed, 27 Apr 2011 11:43:47 -0500 Timothy Pearson wrote:
nslookup quickbuild.pearsoncomputing.net
From New Zealand
[lists@amd64: Lotr]$ nslookup quickbuild.pearsoncomputing.net Server: 203.97.33.14 Address: 203.97.33.14#53
Non-authoritative answer: Name: quickbuild.pearsoncomputing.net Address: 74.84.118.181
John
Do you also have success with
nslookup keyserver.quickbuild.pearsoncomputing.net
and
nslookup ppa.quickbuild.pearsoncomputing.net
?
Thanks!
Tim
On Wed, 27 Apr 2011 11:53:02 -0500 Timothy Pearson wrote:
On Wed, 27 Apr 2011 11:43:47 -0500 Timothy Pearson wrote:
nslookup quickbuild.pearsoncomputing.net
From New Zealand
[lists@amd64: Lotr]$ nslookup quickbuild.pearsoncomputing.net Server: 203.97.33.14 Address: 203.97.33.14#53
Non-authoritative answer: Name: quickbuild.pearsoncomputing.net Address: 74.84.118.181
John
Do you also have success with
nslookup keyserver.quickbuild.pearsoncomputing.net
and
nslookup ppa.quickbuild.pearsoncomputing.net
?
[lists@amd64: Lotr]$ nslookup keyserver.quickbuild.pearsoncomputing.net Server: 203.97.33.14 Address: 203.97.33.14#53
Non-authoritative answer: Name: keyserver.quickbuild.pearsoncomputing.net Address: 74.84.118.181
[lists@amd64: Lotr]$ nslookup ppa.quickbuild.pearsoncomputing.net Server: 203.97.33.14 Address: 203.97.33.14#53
Non-authoritative answer: Name: ppa.quickbuild.pearsoncomputing.net Address: 74.84.118.181
John
[lists@amd64: Lotr]$
On Wed, 27 Apr 2011 11:43:47 -0500 Timothy Pearson wrote:
nslookup quickbuild.pearsoncomputing.net
From New Zealand
[lists@amd64: Lotr]$ nslookup quickbuild.pearsoncomputing.net Server: 203.97.33.14 Address: 203.97.33.14#53
Non-authoritative answer: Name: quickbuild.pearsoncomputing.net Address: 74.84.118.181
John
Do you also have success with
nslookup keyserver.quickbuild.pearsoncomputing.net
and
nslookup ppa.quickbuild.pearsoncomputing.net
?
Thanks!
Tim
| nslookup quickbuild.pearsoncomputing.net
tokra@MD10 ~ $ nslookup quickbuild.pearsoncomputing.net Server: 195.216.160.130 Address: 195.216.160.130#53
** server can't find quickbuild.pearsoncomputing.net: NXDOMAIN
tokra@MD10 ~ $ dig quickbuild.pearsoncomputing.net
;; AUTHORITY SECTION: pearsoncomputing.net. 10792 IN SOA ns1.pearsoncomputing.net. kb9vqf.pearsoncomputing.net. 201103150 14400 28800 2419200 86400
tokra@MD10 ~ $ dig @ns1.pearsoncomputing.net quickbuild.pearsoncomputing.net
;; ANSWER SECTION: quickbuild.pearsoncomputing.net. 86400 IN A 74.84.118.181
;; AUTHORITY SECTION: quickbuild.pearsoncomputing.net. 86400 IN NS ns1.pearsoncomputing.net.
tokra@MD10 ~ $ dig @ns1.twisted4life.com quickbuild.pearsoncomputing.net
;;; ANSWER SECTION: quickbuild.pearsoncomputing.net. 86400 IN A 74.84.118.181 quickbuild.pearsoncomputing.net. 86400 IN A 74.84.118.181
;; AUTHORITY SECTION: quickbuild.pearsoncomputing.net. 86400 IN NS ns1.pearsoncomputing.net.
;; ADDITIONAL SECTION: ns1.pearsoncomputing.net. 86400 IN A 74.84.118.180
Domain servers in listed order: ns1.pearsoncomputing.net ns1.twisted4life.com
So why is pearsoncomputing.net IN NS ns1.pearsoncomputing.net? It's a recursion unless ns1.pearsoncomputing.net is not set up somewhere on the highest level.
A suggestion: change ns1.pearsoncomputing.net NS record to another DNS server or at least another hostname outside pearsoncomputing.net, pointing to 74.84.118.180.
Domain servers in listed order: ns1.pearsoncomputing.net ns1.twisted4life.com
So why is pearsoncomputing.net IN NS ns1.pearsoncomputing.net? It's a recursion unless ns1.pearsoncomputing.net is not set up somewhere on the highest level.
Which it is--check the root DNS records if you want to. :)
Also, pearsoncomputing.net and all other domains here function perfectly. The only problem is with *.quickbuild.pearsoncomputing.net, where * changes somewhat randomly. I have never had an nslookup against ns1.pearsoncomputing.net fail, and the configuration was not changed until just now (to force a cache reload on all DNS servers on the Internet) so I must logically assume the problem was an upstream glitch of some sort. It would not be the first time something unusual has happened upstream to the DNS system of any particular website...
Tim
| nslookup quickbuild.pearsoncomputing.net
tokra@MD10 ~ $ nslookup quickbuild.pearsoncomputing.net Server: 195.216.160.130 Address: 195.216.160.130#53
** server can't find quickbuild.pearsoncomputing.net: NXDOMAIN
tokra@MD10 ~ $ dig quickbuild.pearsoncomputing.net
;; AUTHORITY SECTION: pearsoncomputing.net. 10792 IN SOA ns1.pearsoncomputing.net. kb9vqf.pearsoncomputing.net. 201103150 14400 28800 2419200 86400
tokra@MD10 ~ $ dig @ns1.pearsoncomputing.net quickbuild.pearsoncomputing.net
;; ANSWER SECTION: quickbuild.pearsoncomputing.net. 86400 IN A 74.84.118.181
;; AUTHORITY SECTION: quickbuild.pearsoncomputing.net. 86400 IN NS ns1.pearsoncomputing.net.
tokra@MD10 ~ $ dig @ns1.twisted4life.com quickbuild.pearsoncomputing.net
;;; ANSWER SECTION: quickbuild.pearsoncomputing.net. 86400 IN A 74.84.118.181 quickbuild.pearsoncomputing.net. 86400 IN A 74.84.118.181
;; AUTHORITY SECTION: quickbuild.pearsoncomputing.net. 86400 IN NS ns1.pearsoncomputing.net.
;; ADDITIONAL SECTION: ns1.pearsoncomputing.net. 86400 IN A 74.84.118.180
OK, thanks for the data. I really have no idea what is going on; the fragmentation suggests invalid data floating around the DNS network upstream from me. I have pushed out new DNS records to hopefully override the invalid/corrupted data; give it 24 hours and see if the problem resolves.
Sorry for the inconvenience!
Tim
-
Inga Muste -
John -
Timothy Pearson -
Xyzzy