# PYNQ-2.7 on ZCU104 has network connection problem **URL:** \ **Category:** Support\ **Created:** [December 1, 2021, 8:45am UTC](https://discuss.pynq.io/t/pynq-2-7-on-zcu104-has-network-connection-problem/3362 "2021-12-01T08:45:52Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Hideki](https://avatars.discourse-cdn.com/v4/letter/h/898d66/32.png) [@Hideki](https://discuss.pynq.io/u/Hideki)\ **Post date:** [December 1, 2021, 8:45am UTC](https://discuss.pynq.io/t/pynq-2-7-on-zcu104-has-network-connection-problem/3362/1 "2021-12-01T08:45:52Z")
This is my first post. I download the PYNQ-v2.7 image file for ZCU104, and could successfully boot the system with the ZCU104 board. I found out that network connection to outer world failed with the names, such as, [google.com](http://google.com). I checked with PYNQ v2.6, and it works with this version. It seems to me that name resolving seems not working in v2.7. ---
**Author:** ![cathalmccabe](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/cathalmccabe/32/3348_2.png) [@cathalmccabe](https://discuss.pynq.io/u/cathalmccabe)\ **Post date:** [December 1, 2021, 9:04am UTC](https://discuss.pynq.io/t/pynq-2-7-on-zcu104-has-network-connection-problem/3362/2 "2021-12-01T09:04:19Z")
Can you provide more info? How is your board connected to your network? Did you run `ip addr` on the board? Did you check your network? Cathal ---
**Author:** ![Hideki](https://avatars.discourse-cdn.com/v4/letter/h/898d66/32.png) [@Hideki](https://discuss.pynq.io/u/Hideki)\ **Post date:** [December 2, 2021, 2:59am UTC](https://discuss.pynq.io/t/pynq-2-7-on-zcu104-has-network-connection-problem/3362/3 "2021-12-02T02:59:36Z")
Dear Cathal, My ZCU104 board is connected to a local network using a cabe through a hub The local network in an office shared by several devices is connected to outer world through a conventional gateway, which I think is a sort of typical network environment. The board has two IP addr, the given one 192.168.2.99, and another provate address dynamically allocated by DHCP. With the v2.6, I could access [github.com](http://github.com) to set up DPU-PYNQ without any problem, but no success with v2.7 because of network access failure. I used the brand-new images for both versions, with the same ZCU104 board, while keeping the network environment. Let me know if you need more information. I would hope to hear some good news soon. Thanks in advance. Hideki ---
**Author:** ![Hideki](https://avatars.discourse-cdn.com/v4/letter/h/898d66/32.png) [@Hideki](https://discuss.pynq.io/u/Hideki)\ **Post date:** [December 2, 2021, 4:21am UTC](https://discuss.pynq.io/t/pynq-2-7-on-zcu104-has-network-connection-problem/3362/4 "2021-12-02T04:21:56Z")
Another information. Behavior for ping is different between PYNQ v2.6 and v2.7. In PYNQ v2.7, I can ping from ZCU104 some local machines, such as my MacBook and Ubuntu desktop machine; > ping AAAA.local > ping BBBB.local > and also ping ZCU104 from these machines, > % ping pynq.local > In the PYNQ v2.6, these were not possible. Hideki ---
**Author:** ![cathalmccabe](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/cathalmccabe/32/3348_2.png) [@cathalmccabe](https://discuss.pynq.io/u/cathalmccabe)\ **Post date:** [December 2, 2021, 4:39pm UTC](https://discuss.pynq.io/t/pynq-2-7-on-zcu104-has-network-connection-problem/3362/5 "2021-12-02T16:39:35Z")
Did you run `ip addr` on the board? Can you copy the output here? Cathal ---
**Author:** ![Hideki](https://avatars.discourse-cdn.com/v4/letter/h/898d66/32.png) [@Hideki](https://discuss.pynq.io/u/Hideki)\ **Post date:** [December 3, 2021, 12:22am UTC](https://discuss.pynq.io/t/pynq-2-7-on-zcu104-has-network-connection-problem/3362/6 "2021-12-03T00:22:53Z")
Dear Cathal, xilinx@pynq:~$ ip addr 1: lo: \ mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid\_lft forever preferred\_lft forever inet6 ::1/128 scope host valid\_lft forever preferred\_lft forever 2: dummy0: \ mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether a6:31:1c:44:aa:2b brd ff:ff:ff:ff:ff:ff 3: sit0@NONE: mtu 1480 qdisc noop state DOWN group default qlen 1000 link/sit 0.0.0.0 brd 0.0.0.0 4: can0: \ mtu 16 qdisc noop state DOWN group default qlen 10 link/can 5: eth0: \ mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:0a:35:07:1e:0c brd ff:ff:ff:ff:ff:ff inet 192.168.2.127/24 brd 192.168.2.255 scope global dynamic eth0 valid\_lft 13328sec preferred\_lft 13328sec inet 192.168.2.99/24 brd 192.168.2.255 scope global secondary eth0:1 valid\_lft forever preferred\_lft forever inet6 2408:211:4e23:4c00:20a:35ff:fe07:1e0c/64 scope global dynamic mngtmpaddr valid\_lft 14326sec preferred\_lft 12526sec inet6 fe80::20a:35ff:fe07:1e0c/64 scope link valid\_lft forever preferred\_lft forever xilinx@pynq:~$ ping [github.com](http://github.com) ping: [github.com](http://github.com): Temporary failure in name resolution xilinx@pynq:~$ ping 13.114.40.48 PING 13.114.40.48 (13.114.40.48) 56(84) bytes of data. 64 bytes from 13.114.40.48: icmp\_seq=1 ttl=42 time=11.1 ms 64 bytes from 13.114.40.48: icmp\_seq=2 ttl=42 time=8.36 ms 64 bytes from 13.114.40.48: icmp\_seq=3 ttl=42 time=6.74 ms 64 bytes from 13.114.40.48: icmp\_seq=4 ttl=42 time=7.40 ms ^C — 13.114.40.48 ping statistics — 4 packets transmitted, 4 received, 0% packet loss, time 3004ms rtt min/avg/max/mdev = 6.737/8.385/11.053/1.644 ms Hideki ---
**Author:** ![mizan](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/mizan/32/2119_2.png) [@mizan](https://discuss.pynq.io/u/mizan)\ **Post date:** [December 3, 2021, 6:11am UTC](https://discuss.pynq.io/t/pynq-2-7-on-zcu104-has-network-connection-problem/3362/7 "2021-12-03T06:11:41Z")
try adding the line nameserver 8.8.8.8 to the the /etc/resolv.conf file: nano /ete/resolv.conf → nameserver 8.8.8.8 This [one](https://linuxhint.com/update-resolv-conf-on-ubuntu/) has worked for me once. ---
**Author:** ![Hideki](https://avatars.discourse-cdn.com/v4/letter/h/898d66/32.png) [@Hideki](https://discuss.pynq.io/u/Hideki)\ **Post date:** [December 3, 2021, 8:27am UTC](https://discuss.pynq.io/t/pynq-2-7-on-zcu104-has-network-connection-problem/3362/8 "2021-12-03T08:27:41Z")
/etc/resolve.conf is dynamically created, and changing it directly is not recommended. Thus, I tried; > sudo systemd-resolve —interface=eth0 —set-dns=8.8.8.8 > systemd-resolve —status > I could see DNS Server for eth0, and I now can ping to outer world. > ping github.cim > Thank you very much for your cooporation. > Best Hideki ---
**Author:** ![nfmzl](https://avatars.discourse-cdn.com/v4/letter/n/dbc845/32.png) [@nfmzl](https://discuss.pynq.io/u/nfmzl)\ **Post date:** [January 30, 2022, 10:11am UTC](https://discuss.pynq.io/t/pynq-2-7-on-zcu104-has-network-connection-problem/3362/9 "2022-01-30T10:11:07Z")
Hi guys, I have solved the problem by following steps posted on stackoverflow originally: 1. Disable “systemd-resolved” service: `sudo systemctl disable systemd-resolved.service` 2. Stop the service: `sudo systemctl stop systemd-resolved.service` 3. Remove the link to “/run/systemd/resolve/stub-resolv.conf” in “/etc/resolv.conf” `sudo rm /etc/resolv.conf` 4. Add a manually created “resolv.conf” in “/etc/” `sudo vim /etc/resolv.conf` 5. Add your prefered DNS server there `nameserver 8.8.8.8` This solutions work well for my own ZCU104 board, I can connect to the Internet after doing this. It still works well after every reboot. This solution is from the following post on Stackoverflow: [ubuntu - ping: google.com: Temporary failure in name resolution - Stack Overflow](https://stackoverflow.com/questions/53687051/ping-google-com-temporary-failure-in-name-resolution)