Jetson Nano DNS Problem

Robotics & Edge Computing Jetson & Embedded Systems Jetson Nano
1

I currently have a problem with what I think is a DNS problem on my Jetson Nano

L4T Version: # R32 (release), REVISION: 5.1, GCID: 26202423, BOARD: t210ref, EABI: aarch64

I have the Nano connected via Ethernet to a laptop and the bridged the connection. My aim is to have internet access on the Nano.

I can SSH to the Nano fine, and also I am able to ping address from the Nano.

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=55 time=10.7 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=55 time=9.49 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=55 time=9.34 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=55 time=11.0 ms

However if I try and resolve an address it never works.

**ping google.com**
ping: google.com: Name or service not known

The DNS resolver appears to be set correctly in systemd-resolve --status

Global
         DNS Servers: 8.8.8.8
          DNSSEC NTA: 10.in-addr.arpa
                      16.172.in-addr.arpa
                      168.192.in-addr.arpa
                      17.172.in-addr.arpa
                      18.172.in-addr.arpa
                      19.172.in-addr.arpa
                      20.172.in-addr.arpa
                      21.172.in-addr.arpa
                      22.172.in-addr.arpa
                      23.172.in-addr.arpa
                      24.172.in-addr.arpa
                      25.172.in-addr.arpa
                      26.172.in-addr.arpa
                      27.172.in-addr.arpa
                      28.172.in-addr.arpa
                      29.172.in-addr.arpa
                      30.172.in-addr.arpa
                      31.172.in-addr.arpa
                      corp
                      d.f.ip6.arpa
                      home
                      internal
                      intranet
                      lan
                      local
                      private
                      test

Link 6 (usb0)
      Current Scopes: none
       LLMNR setting: yes
MulticastDNS setting: no
      DNSSEC setting: no
    DNSSEC supported: no

Link 5 (rndis0)
      Current Scopes: none
       LLMNR setting: yes
MulticastDNS setting: no
      DNSSEC setting: no
    DNSSEC supported: no

Link 4 (l4tbr0)
      Current Scopes: none
       LLMNR setting: yes
MulticastDNS setting: no
      DNSSEC setting: no
    DNSSEC supported: no

Link 3 (eth0)
      Current Scopes: none
       LLMNR setting: yes
MulticastDNS setting: no
      DNSSEC setting: no
    DNSSEC supported: no

Link 2 (dummy0)
      Current Scopes: none
       LLMNR setting: yes
MulticastDNS setting: no
      DNSSEC setting: no
    DNSSEC supported: no

I cannot work out what the issue is. I’ve also tried setting up the network via the GUI to no avail. Any ideas?

3

Can we make a experiment here to clarify whether this issue is due to the bridge connection between your host and device?

Try to connect nano directly to the hub/switch and see if it can make the DNS work.

4

Yep, that works. It was previously configured that way, when plugged into the router directly it was fine.

EDIT: Just plugged back directly into router and it worked instantly again. But still not working tethered.

ping google.com
PING google.com (142.250.70.238) 56(84) bytes of data.
64 bytes from mel05s02-in-f14.1e100.net (142.250.70.238): icmp_seq=1 ttl=55 time=8.17 ms
64 bytes from mel05s02-in-f14.1e100.net (142.250.70.238): icmp_seq=2 ttl=55 time=12.7 ms
64 bytes from mel05s02-in-f14.1e100.net (142.250.70.238): icmp_seq=3 ttl=55 time=7.91 ms