Since Bitcoin is decentralized, peers can come and go without notice. The DNS queries are purposefully designed to return a different set of peers for each query. So yes this also applies to Mainnet.
The Bitcoin P2P network cannot work unless you allow full access to port 8333 (port 18333 for testnet). To work around that limitation, we suggest you to run your own full node and connect to it exclusively (using the Peer API). However, that full node would need to sit outside your fireware or otherwise it could not connect to the P2P network either. On 04/21/2017 05:19 AM, Ramez Az wrote: > Hi, > > I am developing small client application for posting the txns and > receiving the txns. I have firewall in my network and i am able to allow > only some Peers to connect in the network. The list of peers(IP > addresses) are getting changed every DNS lookup at > testnet-seed.bitcoin.petertodd.org domain. Can you please provide some > list of Peers through which we should be able to do connect at any time. > Is there any other domain where we can get some consistent Peers or any > alternatives?. If you provide some of consistent peers, i can open my > firewall for those nodes. > > I am facing this issue in Testnet, Is this the same case for mainnet as > well or can we get consistent Peers in MainNet. > > As this is bit urgent, Can any one clarify as soon as possible. > > Thanks in Advance. > > Thanks, > Ramesh A > > -- > You received this message because you are subscribed to the Google > Groups "bitcoinj" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "bitcoinj" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
