# Algo Node stopped syncing at 2.5.6 and resolved

**URL:** <https://forum.algorand.co/t/algo-node-stopped-syncing-at-2-5-6-and-resolved/3776>\
**Category:** General\
**Created:** [July 15, 2021, 4:22pm UTC](https://forum.algorand.co/t/algo-node-stopped-syncing-at-2-5-6-and-resolved/3776 "2021-07-15T16:22:23Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![debasish](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/debasish/32/419_2.png) [@debasish](https://forum.algorand.co/u/debasish)\
**Post date:** [July 15, 2021, 4:22pm UTC](https://forum.algorand.co/t/algo-node-stopped-syncing-at-2-5-6-and-resolved/3776/1 "2021-07-15T16:22:23Z")

</div>

@fabrice Could you please help me understand below issue .

My node stopped syncing which was running at 2.5.6 .

1. I checked node.logs for find the root cause found DNS Look up issue for which ib have searched over the forum and it was instructed to run the dig command which i did - dig @8.8.8.8 \_algobootstrap.\_tcp.testnet.algorand.network srv and below is the output

; \<\<\>\> DiG 9.11.3-1ubuntu1.11-Ubuntu \<\<\>\> @8.8.8.8 \_algobootstrap.\_tcp.testnet.algorand.network srv  
; (1 server found)  
;; global options: +cmd  
;; connection timed out; no servers could be reached

I guess with the DNS lookup and dig command i thought its something with the 2.5.6 node. _Can you please confirm my understanding._

But i could not find a way but to upgrade the algo node to 2.7.1 and everything starts working.

After that again i took a look at the logs

1. I still have the DNS look up issue and
2. dig command returns the same

Can you please let me know what are the above 2 issues all about and i guess these were not the real reasons for node stopped syncing .So what might the reason for the node sync issue and how can we find the root cause moving ahead

---

_[View the full topic](https://forum.algorand.co/t/algo-node-stopped-syncing-at-2-5-6-and-resolved/3776)._