š
Original date posted:2014-05-26
š Original message:On Sun, May 25, 2014 at 09:12:10PM +0200, Andreas Schildbach wrote:
> Thanks for looking at the issue.
>
> Unfortunately, it still fails for me:
>
> $ nslookup testnet-seed.bitcoin.petertodd.org
> Server: 127.0.1.1
> Address: 127.0.1.1#53
>
> ** server can't find testnet-seed.bitcoin.petertodd.org: SERVFAIL
>
> Like I said, can you look at the logfiles how the requests arrive?
There are no logfiles for DNS requests.
I just checked on EC2 and my cellphone internet connection here in Tel
Aviv; both work fine. My best guess is that your DNS resolver locally or
at your ISP is unable to deal with the fact that the second DNS seed
serving the domain testnet-seed.bitcoin.petertodd.org happens to be down
right now. Note that some ISP's appear to both run buggy DNS servers,
and redirect traffic meant to go to Google's 8.8.8 and 8.8.4.4 DNS
servers to their own servers.
I'd suggest that someone setup an alternate HTTP(S) based DNS seed for
protocol redundency.
> What particular thing did you fix? It would be good to know for future
> outages.
Dunno exactly. It appeared to be running fine when I logged into the
machine, but for whatever reason DNS requests just weren't getting
resolved. Restarted and it was ok again.
--
'peter'[:-1]@petertodd.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: Digital signature
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140526/c87df7ed/attachment.sig>;
Peter Todd [ARCHIVE] /
npub1m2ā¦a2np2
2023-06-07 15:21:58
in reply to nevent1qā¦hc4k
Author Public Key
npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2Published at
2023-06-07 15:21:58Event JSON
{
"id": "05afe7983ef86625b8216037fcda2d13429d0d491da2db83da52303bf342b63b",
"pubkey": "daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa",
"created_at": 1686151318,
"kind": 1,
"tags": [
[
"e",
"1df32530851d221cbbd33f32f81f5456a402725593653d36a2348e31d3f14708",
"",
"root"
],
[
"e",
"2dd33427d20cb951186516c5d9c229f3c036cf9c0f921d4d2e19ae73b6f7abc9",
"",
"reply"
],
[
"p",
"993649062e0bbe4df9623f7c93df2746ccfe1ce9dcb5251a6283e09a5019a3c2"
]
],
"content": "š
Original date posted:2014-05-26\nš Original message:On Sun, May 25, 2014 at 09:12:10PM +0200, Andreas Schildbach wrote:\n\u003e Thanks for looking at the issue.\n\u003e \n\u003e Unfortunately, it still fails for me:\n\u003e \n\u003e $ nslookup testnet-seed.bitcoin.petertodd.org\n\u003e Server:\t\t127.0.1.1\n\u003e Address:\t127.0.1.1#53\n\u003e \n\u003e ** server can't find testnet-seed.bitcoin.petertodd.org: SERVFAIL\n\u003e \n\u003e Like I said, can you look at the logfiles how the requests arrive?\n\nThere are no logfiles for DNS requests.\n\nI just checked on EC2 and my cellphone internet connection here in Tel\nAviv; both work fine. My best guess is that your DNS resolver locally or\nat your ISP is unable to deal with the fact that the second DNS seed\nserving the domain testnet-seed.bitcoin.petertodd.org happens to be down\nright now. Note that some ISP's appear to both run buggy DNS servers,\nand redirect traffic meant to go to Google's 8.8.8 and 8.8.4.4 DNS\nservers to their own servers.\n\nI'd suggest that someone setup an alternate HTTP(S) based DNS seed for\nprotocol redundency.\n\n\u003e What particular thing did you fix? It would be good to know for future\n\u003e outages.\n\nDunno exactly. It appeared to be running fine when I logged into the\nmachine, but for whatever reason DNS requests just weren't getting\nresolved. Restarted and it was ok again.\n\n-- \n'peter'[:-1]@petertodd.org\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 490 bytes\nDesc: Digital signature\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140526/c87df7ed/attachment.sig\u003e",
"sig": "f239d708f344d102c066e15e9e85fbf6507bafca1de1da747b8f692dee0a2b166d94a02f3f98cfff8ee1221ad2ef2ebc4c5da0e1971bb7427e70bda8513c1524"
}