Ubuntu 18.04 not recognizing hostnames from routerUbuntu One hangs router socketsubuntu server not resolving...

"It doesn't matter" or "it won't matter"?

How much theory knowledge is actually used while playing?

Why is the Sun approximated as a black body at ~ 5800 K?

What is Cash Advance APR?

Which Article Helped Get Rid of Technobabble in RPGs?

Make a Bowl of Alphabet Soup

Why do Radio Buttons not fill the entire outer circle?

Does Doodling or Improvising on the Piano Have Any Benefits?

Multiplicative persistence

Merge org tables

Which was the first story featuring espers?

Why Shazam when there is already Superman?

awk assign to multiple variables at once

Circuit Analysis: Obtaining Close Loop OP - AMP Transfer function

What's the name of the logical fallacy where a debater extends a statement far beyond the original statement to make it true?

C++ copy constructor called at return

Does the reader need to like the PoV character?

Taxes on Dividends in a Roth IRA

Why do ¬, ∀ and ∃ have the same precedence?

Review your own paper in Mathematics

The Digit Triangles

What (the heck) is a Super Worm Equinox Moon?

Stack Interview Code methods made from class Node and Smart Pointers

What is the difference between lands and mana?



Ubuntu 18.04 not recognizing hostnames from router


Ubuntu One hangs router socketsubuntu server not resolving LAN hostnamesAccessing router with Ubuntu client from remoteUbuntu 14.04 LTS not recognizing my wifi routerHow to configure home router from terminal?Some websites not loading -16.04dhcpd not handling client hostnames properly on router machinePages loading too long on new router (Ubuntu 18.04)Ubuntu 18.04 as a routerhome router not working after upgrade













0















I previously had Xubuntu 16.04 installed, and it did recognize the hostnames set by my router (Tomato).



For example, I have a computer with the name mate on the network with a static IP of 192.168.2.202, and previously I could do this:



$ host mate                                                               

mate has address 192.168.2.202


But now I get this:



$ host mate

Host mate not found: 2(SERVFAIL)


This time around I did a minimal desktop install, so I wonder if there is a certain package I am missing.



EDIT:



$ cat /var/run/systemd/resolve/resolv.conf:

nameserver 192.168.2.1






$ cat /var/run/NetworkManager/resolv.conf

nameserver 127.0.0.53






$ netstat -antup

Active Internet connections (servers and established)

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    

tcp        0      0 0.0.0.0:5000            0.0.0.0:*               LISTEN      3421/VBoxHeadless   

tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      663/systemd-resolve 

tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      950/sshd            

tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      737/cupsd              

tcp6       0      0 :::5900                 :::*                    LISTEN      3421/VBoxHeadless   

tcp6       0      0 :::22                   :::*                    LISTEN      950/sshd            

tcp6       0      0 ::1:631                 :::*                    LISTEN      737/cupsd           

udp    14784      0 0.0.0.0:52712           0.0.0.0:*                           2092/VirtualBox     

udp     8704      0 0.0.0.0:53789           0.0.0.0:*                           2092/VirtualBox     

udp     9536      0 0.0.0.0:5353            0.0.0.0:*                           730/avahi-daemon: r 

udp    19648      0 0.0.0.0:55126           0.0.0.0:*                           2092/VirtualBox     

udp     8704      0 0.0.0.0:39114           0.0.0.0:*                           2092/VirtualBox     

udp    13248      0 0.0.0.0:41109           0.0.0.0:*                           2092/VirtualBox     

udp        0      0 0.0.0.0:57555           0.0.0.0:*                           730/avahi-daemon: r 

udp     3648      0 0.0.0.0:59213           0.0.0.0:*                           2092/VirtualBox     

udp     8064      0 0.0.0.0:59519           0.0.0.0:*                           2092/VirtualBox     

udp     3648      0 0.0.0.0:48795           0.0.0.0:*                           2092/VirtualBox     

udp     3648      0 0.0.0.0:48900           0.0.0.0:*                           2092/VirtualBox     

udp    36096      0 127.0.0.53:53           0.0.0.0:*                           663/systemd-resolve 

udp    37120      0 0.0.0.0:68              0.0.0.0:*                           1066/dhclient       

udp    15424      0 0.0.0.0:33008           0.0.0.0:*                           2092/VirtualBox     

udp     3648      0 0.0.0.0:49597           0.0.0.0:*                           2092/VirtualBox     

udp    14464      0 0.0.0.0:33395           0.0.0.0:*                           2092/VirtualBox     

udp        0      0 0.0.0.0:631             0.0.0.0:*                           828/cups-browsed    

udp    19840      0 0.0.0.0:49883           0.0.0.0:*                           2092/VirtualBox     

udp    14592      0 0.0.0.0:33614           0.0.0.0:*                           2092/VirtualBox     

udp6       0      0 :::51356                :::*                                730/avahi-daemon: r 

udp6   49344      0 :::5353                 :::*                                730/avahi-daemon: r 






$ systemd-resolve --status

Global

          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 (vboxnet2)

      Current Scopes: none

       LLMNR setting: yes

MulticastDNS setting: no

      DNSSEC setting: no

    DNSSEC supported: no



Link 5 (vboxnet1)

      Current Scopes: none

       LLMNR setting: yes

MulticastDNS setting: no

      DNSSEC setting: no

    DNSSEC supported: no



Link 4 (vboxnet0)

      Current Scopes: none

       LLMNR setting: yes

MulticastDNS setting: no

      DNSSEC setting: no

    DNSSEC supported: no



Link 3 (wlp4s1)

      Current Scopes: none

       LLMNR setting: yes

MulticastDNS setting: no

      DNSSEC setting: no

    DNSSEC supported: no



Link 2 (eno1)

      Current Scopes: DNS

       LLMNR setting: yes

MulticastDNS setting: no

      DNSSEC setting: no

    DNSSEC supported: no

         DNS Servers: 192.168.2.1


My router is 192.168.2.1



EDIT 2:



Using dig shows that the router does correctly report the hostname.



$ dig @192.168.2.1 mate    

; <<>> DiG 9.11.3-1ubuntu1.1-Ubuntu <<>> @192.168.2.1 mate

; (1 server found)

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47046

;; flags: qr aa rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0



;; QUESTION SECTION:

;mate.              IN  A



;; ANSWER SECTION:

mate.           0   IN  A   192.168.2.202



;; Query time: 0 msec

;; SERVER: 192.168.2.1#53(192.168.2.1)

;; WHEN: Mon Jun 18 18:53:26 PDT 2018

;; MSG SIZE  rcvd: 38


But if I don't specifically mention the router's DNS IP, I don't find it. 



$ dig mate             

; <<>> DiG 9.11.3-1ubuntu1.1-Ubuntu <<>> mate

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 65394

;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1



;; OPT PSEUDOSECTION:

; EDNS: version: 0, flags:; udp: 65494

;; QUESTION SECTION:

;mate.              IN  A



;; Query time: 0 msec

;; SERVER: 127.0.0.53#53(127.0.0.53)

;; WHEN: Mon Jun 18 19:06:13 PDT 2018

;; MSG SIZE  rcvd: 33


So it seems that even though it is listed in /var/run/systemd/resolve/resolv.conf it is not being used. How do I fix this?






networking router hosts







share|improve this question
















bumped to the homepage by Community♦ 9 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • if your local network is as simple, you can add a line to /etc/hosts -- but you should give us more information about your network configuration -- sudo netstat -antup -- cat /var/run/systemd/resolve/resolv.conf -- cat /var/run/NetworkManager/resolv.conf

    – cmak.fr
    Jun 18 '18 at 23:39













  • @cmak.fr I am aware I can add hosts manually to each machine, but that's not really a solution. I have added more info.

    – Sarke
    Jun 19 '18 at 1:03











  • OK, thanks for all the info -- Here is what happen: systemd-resolved do not resolve local domain names if the names are not fully qualified names like mate.local.lan .

    – cmak.fr
    Jun 19 '18 at 7:48
















0















I previously had Xubuntu 16.04 installed, and it did recognize the hostnames set by my router (Tomato).



For example, I have a computer with the name mate on the network with a static IP of 192.168.2.202, and previously I could do this:



$ host mate                                                               

mate has address 192.168.2.202


But now I get this:



$ host mate

Host mate not found: 2(SERVFAIL)


This time around I did a minimal desktop install, so I wonder if there is a certain package I am missing.



EDIT:



$ cat /var/run/systemd/resolve/resolv.conf:

nameserver 192.168.2.1






$ cat /var/run/NetworkManager/resolv.conf

nameserver 127.0.0.53






$ netstat -antup

Active Internet connections (servers and established)

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    

tcp        0      0 0.0.0.0:5000            0.0.0.0:*               LISTEN      3421/VBoxHeadless   

tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      663/systemd-resolve 

tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      950/sshd            

tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      737/cupsd              

tcp6       0      0 :::5900                 :::*                    LISTEN      3421/VBoxHeadless   

tcp6       0      0 :::22                   :::*                    LISTEN      950/sshd            

tcp6       0      0 ::1:631                 :::*                    LISTEN      737/cupsd           

udp    14784      0 0.0.0.0:52712           0.0.0.0:*                           2092/VirtualBox     

udp     8704      0 0.0.0.0:53789           0.0.0.0:*                           2092/VirtualBox     

udp     9536      0 0.0.0.0:5353            0.0.0.0:*                           730/avahi-daemon: r 

udp    19648      0 0.0.0.0:55126           0.0.0.0:*                           2092/VirtualBox     

udp     8704      0 0.0.0.0:39114           0.0.0.0:*                           2092/VirtualBox     

udp    13248      0 0.0.0.0:41109           0.0.0.0:*                           2092/VirtualBox     

udp        0      0 0.0.0.0:57555           0.0.0.0:*                           730/avahi-daemon: r 

udp     3648      0 0.0.0.0:59213           0.0.0.0:*                           2092/VirtualBox     

udp     8064      0 0.0.0.0:59519           0.0.0.0:*                           2092/VirtualBox     

udp     3648      0 0.0.0.0:48795           0.0.0.0:*                           2092/VirtualBox     

udp     3648      0 0.0.0.0:48900           0.0.0.0:*                           2092/VirtualBox     

udp    36096      0 127.0.0.53:53           0.0.0.0:*                           663/systemd-resolve 

udp    37120      0 0.0.0.0:68              0.0.0.0:*                           1066/dhclient       

udp    15424      0 0.0.0.0:33008           0.0.0.0:*                           2092/VirtualBox     

udp     3648      0 0.0.0.0:49597           0.0.0.0:*                           2092/VirtualBox     

udp    14464      0 0.0.0.0:33395           0.0.0.0:*                           2092/VirtualBox     

udp        0      0 0.0.0.0:631             0.0.0.0:*                           828/cups-browsed    

udp    19840      0 0.0.0.0:49883           0.0.0.0:*                           2092/VirtualBox     

udp    14592      0 0.0.0.0:33614           0.0.0.0:*                           2092/VirtualBox     

udp6       0      0 :::51356                :::*                                730/avahi-daemon: r 

udp6   49344      0 :::5353                 :::*                                730/avahi-daemon: r 






$ systemd-resolve --status

Global

          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 (vboxnet2)

      Current Scopes: none

       LLMNR setting: yes

MulticastDNS setting: no

      DNSSEC setting: no

    DNSSEC supported: no



Link 5 (vboxnet1)

      Current Scopes: none

       LLMNR setting: yes

MulticastDNS setting: no

      DNSSEC setting: no

    DNSSEC supported: no



Link 4 (vboxnet0)

      Current Scopes: none

       LLMNR setting: yes

MulticastDNS setting: no

      DNSSEC setting: no

    DNSSEC supported: no



Link 3 (wlp4s1)

      Current Scopes: none

       LLMNR setting: yes

MulticastDNS setting: no

      DNSSEC setting: no

    DNSSEC supported: no



Link 2 (eno1)

      Current Scopes: DNS

       LLMNR setting: yes

MulticastDNS setting: no

      DNSSEC setting: no

    DNSSEC supported: no

         DNS Servers: 192.168.2.1


My router is 192.168.2.1



EDIT 2:



Using dig shows that the router does correctly report the hostname.



$ dig @192.168.2.1 mate    

; <<>> DiG 9.11.3-1ubuntu1.1-Ubuntu <<>> @192.168.2.1 mate

; (1 server found)

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47046

;; flags: qr aa rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0



;; QUESTION SECTION:

;mate.              IN  A



;; ANSWER SECTION:

mate.           0   IN  A   192.168.2.202



;; Query time: 0 msec

;; SERVER: 192.168.2.1#53(192.168.2.1)

;; WHEN: Mon Jun 18 18:53:26 PDT 2018

;; MSG SIZE  rcvd: 38


But if I don't specifically mention the router's DNS IP, I don't find it. 



$ dig mate             

; <<>> DiG 9.11.3-1ubuntu1.1-Ubuntu <<>> mate

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 65394

;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1



;; OPT PSEUDOSECTION:

; EDNS: version: 0, flags:; udp: 65494

;; QUESTION SECTION:

;mate.              IN  A



;; Query time: 0 msec

;; SERVER: 127.0.0.53#53(127.0.0.53)

;; WHEN: Mon Jun 18 19:06:13 PDT 2018

;; MSG SIZE  rcvd: 33


So it seems that even though it is listed in /var/run/systemd/resolve/resolv.conf it is not being used. How do I fix this?






networking router hosts







share|improve this question
















bumped to the homepage by Community♦ 9 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • if your local network is as simple, you can add a line to /etc/hosts -- but you should give us more information about your network configuration -- sudo netstat -antup -- cat /var/run/systemd/resolve/resolv.conf -- cat /var/run/NetworkManager/resolv.conf

    – cmak.fr
    Jun 18 '18 at 23:39













  • @cmak.fr I am aware I can add hosts manually to each machine, but that's not really a solution. I have added more info.

    – Sarke
    Jun 19 '18 at 1:03











  • OK, thanks for all the info -- Here is what happen: systemd-resolved do not resolve local domain names if the names are not fully qualified names like mate.local.lan .

    – cmak.fr
    Jun 19 '18 at 7:48














0












0








0








I previously had Xubuntu 16.04 installed, and it did recognize the hostnames set by my router (Tomato).



For example, I have a computer with the name mate on the network with a static IP of 192.168.2.202, and previously I could do this:



$ host mate                                                               

mate has address 192.168.2.202


But now I get this:



$ host mate

Host mate not found: 2(SERVFAIL)


This time around I did a minimal desktop install, so I wonder if there is a certain package I am missing.



EDIT:



$ cat /var/run/systemd/resolve/resolv.conf:

nameserver 192.168.2.1






$ cat /var/run/NetworkManager/resolv.conf

nameserver 127.0.0.53






$ netstat -antup

Active Internet connections (servers and established)

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    

tcp        0      0 0.0.0.0:5000            0.0.0.0:*               LISTEN      3421/VBoxHeadless   

tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      663/systemd-resolve 

tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      950/sshd            

tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      737/cupsd              

tcp6       0      0 :::5900                 :::*                    LISTEN      3421/VBoxHeadless   

tcp6       0      0 :::22                   :::*                    LISTEN      950/sshd            

tcp6       0      0 ::1:631                 :::*                    LISTEN      737/cupsd           

udp    14784      0 0.0.0.0:52712           0.0.0.0:*                           2092/VirtualBox     

udp     8704      0 0.0.0.0:53789           0.0.0.0:*                           2092/VirtualBox     

udp     9536      0 0.0.0.0:5353            0.0.0.0:*                           730/avahi-daemon: r 

udp    19648      0 0.0.0.0:55126           0.0.0.0:*                           2092/VirtualBox     

udp     8704      0 0.0.0.0:39114           0.0.0.0:*                           2092/VirtualBox     

udp    13248      0 0.0.0.0:41109           0.0.0.0:*                           2092/VirtualBox     

udp        0      0 0.0.0.0:57555           0.0.0.0:*                           730/avahi-daemon: r 

udp     3648      0 0.0.0.0:59213           0.0.0.0:*                           2092/VirtualBox     

udp     8064      0 0.0.0.0:59519           0.0.0.0:*                           2092/VirtualBox     

udp     3648      0 0.0.0.0:48795           0.0.0.0:*                           2092/VirtualBox     

udp     3648      0 0.0.0.0:48900           0.0.0.0:*                           2092/VirtualBox     

udp    36096      0 127.0.0.53:53           0.0.0.0:*                           663/systemd-resolve 

udp    37120      0 0.0.0.0:68              0.0.0.0:*                           1066/dhclient       

udp    15424      0 0.0.0.0:33008           0.0.0.0:*                           2092/VirtualBox     

udp     3648      0 0.0.0.0:49597           0.0.0.0:*                           2092/VirtualBox     

udp    14464      0 0.0.0.0:33395           0.0.0.0:*                           2092/VirtualBox     

udp        0      0 0.0.0.0:631             0.0.0.0:*                           828/cups-browsed    

udp    19840      0 0.0.0.0:49883           0.0.0.0:*                           2092/VirtualBox     

udp    14592      0 0.0.0.0:33614           0.0.0.0:*                           2092/VirtualBox     

udp6       0      0 :::51356                :::*                                730/avahi-daemon: r 

udp6   49344      0 :::5353                 :::*                                730/avahi-daemon: r 






$ systemd-resolve --status

Global

          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 (vboxnet2)

      Current Scopes: none

       LLMNR setting: yes

MulticastDNS setting: no

      DNSSEC setting: no

    DNSSEC supported: no



Link 5 (vboxnet1)

      Current Scopes: none

       LLMNR setting: yes

MulticastDNS setting: no

      DNSSEC setting: no

    DNSSEC supported: no



Link 4 (vboxnet0)

      Current Scopes: none

       LLMNR setting: yes

MulticastDNS setting: no

      DNSSEC setting: no

    DNSSEC supported: no



Link 3 (wlp4s1)

      Current Scopes: none

       LLMNR setting: yes

MulticastDNS setting: no

      DNSSEC setting: no

    DNSSEC supported: no



Link 2 (eno1)

      Current Scopes: DNS

       LLMNR setting: yes

MulticastDNS setting: no

      DNSSEC setting: no

    DNSSEC supported: no

         DNS Servers: 192.168.2.1


My router is 192.168.2.1



EDIT 2:



Using dig shows that the router does correctly report the hostname.



$ dig @192.168.2.1 mate    

; <<>> DiG 9.11.3-1ubuntu1.1-Ubuntu <<>> @192.168.2.1 mate

; (1 server found)

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47046

;; flags: qr aa rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0



;; QUESTION SECTION:

;mate.              IN  A



;; ANSWER SECTION:

mate.           0   IN  A   192.168.2.202



;; Query time: 0 msec

;; SERVER: 192.168.2.1#53(192.168.2.1)

;; WHEN: Mon Jun 18 18:53:26 PDT 2018

;; MSG SIZE  rcvd: 38


But if I don't specifically mention the router's DNS IP, I don't find it. 



$ dig mate             

; <<>> DiG 9.11.3-1ubuntu1.1-Ubuntu <<>> mate

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 65394

;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1



;; OPT PSEUDOSECTION:

; EDNS: version: 0, flags:; udp: 65494

;; QUESTION SECTION:

;mate.              IN  A



;; Query time: 0 msec

;; SERVER: 127.0.0.53#53(127.0.0.53)

;; WHEN: Mon Jun 18 19:06:13 PDT 2018

;; MSG SIZE  rcvd: 33


So it seems that even though it is listed in /var/run/systemd/resolve/resolv.conf it is not being used. How do I fix this?






networking router hosts







share|improve this question
















I previously had Xubuntu 16.04 installed, and it did recognize the hostnames set by my router (Tomato).



For example, I have a computer with the name mate on the network with a static IP of 192.168.2.202, and previously I could do this:



$ host mate                                                               

mate has address 192.168.2.202


But now I get this:



$ host mate

Host mate not found: 2(SERVFAIL)


This time around I did a minimal desktop install, so I wonder if there is a certain package I am missing.



EDIT:



$ cat /var/run/systemd/resolve/resolv.conf:

nameserver 192.168.2.1






$ cat /var/run/NetworkManager/resolv.conf

nameserver 127.0.0.53






$ netstat -antup

Active Internet connections (servers and established)

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    

tcp        0      0 0.0.0.0:5000            0.0.0.0:*               LISTEN      3421/VBoxHeadless   

tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      663/systemd-resolve 

tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      950/sshd            

tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      737/cupsd              

tcp6       0      0 :::5900                 :::*                    LISTEN      3421/VBoxHeadless   

tcp6       0      0 :::22                   :::*                    LISTEN      950/sshd            

tcp6       0      0 ::1:631                 :::*                    LISTEN      737/cupsd           

udp    14784      0 0.0.0.0:52712           0.0.0.0:*                           2092/VirtualBox     

udp     8704      0 0.0.0.0:53789           0.0.0.0:*                           2092/VirtualBox     

udp     9536      0 0.0.0.0:5353            0.0.0.0:*                           730/avahi-daemon: r 

udp    19648      0 0.0.0.0:55126           0.0.0.0:*                           2092/VirtualBox     

udp     8704      0 0.0.0.0:39114           0.0.0.0:*                           2092/VirtualBox     

udp    13248      0 0.0.0.0:41109           0.0.0.0:*                           2092/VirtualBox     

udp        0      0 0.0.0.0:57555           0.0.0.0:*                           730/avahi-daemon: r 

udp     3648      0 0.0.0.0:59213           0.0.0.0:*                           2092/VirtualBox     

udp     8064      0 0.0.0.0:59519           0.0.0.0:*                           2092/VirtualBox     

udp     3648      0 0.0.0.0:48795           0.0.0.0:*                           2092/VirtualBox     

udp     3648      0 0.0.0.0:48900           0.0.0.0:*                           2092/VirtualBox     

udp    36096      0 127.0.0.53:53           0.0.0.0:*                           663/systemd-resolve 

udp    37120      0 0.0.0.0:68              0.0.0.0:*                           1066/dhclient       

udp    15424      0 0.0.0.0:33008           0.0.0.0:*                           2092/VirtualBox     

udp     3648      0 0.0.0.0:49597           0.0.0.0:*                           2092/VirtualBox     

udp    14464      0 0.0.0.0:33395           0.0.0.0:*                           2092/VirtualBox     

udp        0      0 0.0.0.0:631             0.0.0.0:*                           828/cups-browsed    

udp    19840      0 0.0.0.0:49883           0.0.0.0:*                           2092/VirtualBox     

udp    14592      0 0.0.0.0:33614           0.0.0.0:*                           2092/VirtualBox     

udp6       0      0 :::51356                :::*                                730/avahi-daemon: r 

udp6   49344      0 :::5353                 :::*                                730/avahi-daemon: r 






$ systemd-resolve --status

Global

          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 (vboxnet2)

      Current Scopes: none

       LLMNR setting: yes

MulticastDNS setting: no

      DNSSEC setting: no

    DNSSEC supported: no



Link 5 (vboxnet1)

      Current Scopes: none

       LLMNR setting: yes

MulticastDNS setting: no

      DNSSEC setting: no

    DNSSEC supported: no



Link 4 (vboxnet0)

      Current Scopes: none

       LLMNR setting: yes

MulticastDNS setting: no

      DNSSEC setting: no

    DNSSEC supported: no



Link 3 (wlp4s1)

      Current Scopes: none

       LLMNR setting: yes

MulticastDNS setting: no

      DNSSEC setting: no

    DNSSEC supported: no



Link 2 (eno1)

      Current Scopes: DNS

       LLMNR setting: yes

MulticastDNS setting: no

      DNSSEC setting: no

    DNSSEC supported: no

         DNS Servers: 192.168.2.1


My router is 192.168.2.1



EDIT 2:



Using dig shows that the router does correctly report the hostname.



$ dig @192.168.2.1 mate    

; <<>> DiG 9.11.3-1ubuntu1.1-Ubuntu <<>> @192.168.2.1 mate

; (1 server found)

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47046

;; flags: qr aa rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0



;; QUESTION SECTION:

;mate.              IN  A



;; ANSWER SECTION:

mate.           0   IN  A   192.168.2.202



;; Query time: 0 msec

;; SERVER: 192.168.2.1#53(192.168.2.1)

;; WHEN: Mon Jun 18 18:53:26 PDT 2018

;; MSG SIZE  rcvd: 38


But if I don't specifically mention the router's DNS IP, I don't find it. 



$ dig mate             

; <<>> DiG 9.11.3-1ubuntu1.1-Ubuntu <<>> mate

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 65394

;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1



;; OPT PSEUDOSECTION:

; EDNS: version: 0, flags:; udp: 65494

;; QUESTION SECTION:

;mate.              IN  A



;; Query time: 0 msec

;; SERVER: 127.0.0.53#53(127.0.0.53)

;; WHEN: Mon Jun 18 19:06:13 PDT 2018

;; MSG SIZE  rcvd: 33


So it seems that even though it is listed in /var/run/systemd/resolve/resolv.conf it is not being used. How do I fix this?






networking router hosts




networking router hosts






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jun 19 '18 at 2:08







Sarke

















asked Jun 18 '18 at 22:55









SarkeSarke

14616




14616





bumped to the homepage by Community♦ 9 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community♦ 9 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • if your local network is as simple, you can add a line to /etc/hosts -- but you should give us more information about your network configuration -- sudo netstat -antup -- cat /var/run/systemd/resolve/resolv.conf -- cat /var/run/NetworkManager/resolv.conf

    – cmak.fr
    Jun 18 '18 at 23:39













  • @cmak.fr I am aware I can add hosts manually to each machine, but that's not really a solution. I have added more info.

    – Sarke
    Jun 19 '18 at 1:03











  • OK, thanks for all the info -- Here is what happen: systemd-resolved do not resolve local domain names if the names are not fully qualified names like mate.local.lan .

    – cmak.fr
    Jun 19 '18 at 7:48



















  • if your local network is as simple, you can add a line to /etc/hosts -- but you should give us more information about your network configuration -- sudo netstat -antup -- cat /var/run/systemd/resolve/resolv.conf -- cat /var/run/NetworkManager/resolv.conf

    – cmak.fr
    Jun 18 '18 at 23:39













  • @cmak.fr I am aware I can add hosts manually to each machine, but that's not really a solution. I have added more info.

    – Sarke
    Jun 19 '18 at 1:03











  • OK, thanks for all the info -- Here is what happen: systemd-resolved do not resolve local domain names if the names are not fully qualified names like mate.local.lan .

    – cmak.fr
    Jun 19 '18 at 7:48

















if your local network is as simple, you can add a line to /etc/hosts -- but you should give us more information about your network configuration -- sudo netstat -antup -- cat /var/run/systemd/resolve/resolv.conf -- cat /var/run/NetworkManager/resolv.conf

– cmak.fr
Jun 18 '18 at 23:39







if your local network is as simple, you can add a line to /etc/hosts -- but you should give us more information about your network configuration -- sudo netstat -antup -- cat /var/run/systemd/resolve/resolv.conf -- cat /var/run/NetworkManager/resolv.conf

– cmak.fr
Jun 18 '18 at 23:39















@cmak.fr I am aware I can add hosts manually to each machine, but that's not really a solution. I have added more info.

– Sarke
Jun 19 '18 at 1:03





@cmak.fr I am aware I can add hosts manually to each machine, but that's not really a solution. I have added more info.

– Sarke
Jun 19 '18 at 1:03













OK, thanks for all the info -- Here is what happen: systemd-resolved do not resolve local domain names if the names are not fully qualified names like mate.local.lan .

– cmak.fr
Jun 19 '18 at 7:48





OK, thanks for all the info -- Here is what happen: systemd-resolved do not resolve local domain names if the names are not fully qualified names like mate.local.lan .

– cmak.fr
Jun 19 '18 at 7:48










2 Answers
2






active

oldest

votes


















0














Here is what happen: systemd-resolved do not resolve local domain names if the names are not fully qualified names like mate.local


As told in a doc about Systemd-networkd, a good fix is to trim the /etc/nsswitch.conf file



sudo nano /etc/nsswitch.conf


Modify the hosts line



# /etc/nsswitch.conf

#

# Example configuration of GNU Name Service Switch functionality.

# If you have the `glibc-doc-reference' and `info' packages installed, try:

# `info libc "Name Service Switch"' for information about this file.



passwd:         compat systemd

group:          compat systemd

shadow:         compat

gshadow:        files

# ---- MODIFY THIS LINE ------------------------------------------------

# hosts:          files mdns4_minimal [NOTFOUND=return] dns myhostname

# ---- TO --------------------------------------------------------------

hosts:          files mdns4_minimal dns myhostname

# ---- THATS ALL -------------------------------------------------------

networks:       files



protocols:      db files

services:       db files

ethers:         db files

rpc:            db files



netgroup:       nis


Explanation:

Hostname resolving search first in files (/etc/hosts), then with avahi (zeroconf), then ask to dns server. And do not more stop if avahi does not find a local name as [NOTFOUND=return] forced. Hope its clear.



restart service



sudo systemctl restart systemd-resolved





share|improve this answer





















  • 3





    This sounds good, but it didn't fix it for me, even after executing "systemd-resolve --flush-caches". (Mine broke after upgrade from 16.04 to 18.04)

    – Charles Boling
    Oct 25 '18 at 4:19





















-1














This seems to related to this issue:



https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320



On a fresh install, /etc/resolv.conf is linked to /run/systemd/resolve/stub-resolv.conf instead of /run/systemd/resolve/resolv.conf.



Updating it per https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/comments/8 fixed it.






share|improve this answer
























  • Sorry, the story with /etc/resolv.conf and /run/systemd/resolve/stub-resolv.conf is not the issue of the bug report #1624320 -- The workaround found by some user is not a fix

    – cmak.fr
    Jun 19 '18 at 7:46













Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1047735%2fubuntu-18-04-not-recognizing-hostnames-from-router%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














Here is what happen: systemd-resolved do not resolve local domain names if the names are not fully qualified names like mate.local


As told in a doc about Systemd-networkd, a good fix is to trim the /etc/nsswitch.conf file



sudo nano /etc/nsswitch.conf


Modify the hosts line



# /etc/nsswitch.conf

#

# Example configuration of GNU Name Service Switch functionality.

# If you have the `glibc-doc-reference' and `info' packages installed, try:

# `info libc "Name Service Switch"' for information about this file.



passwd:         compat systemd

group:          compat systemd

shadow:         compat

gshadow:        files

# ---- MODIFY THIS LINE ------------------------------------------------

# hosts:          files mdns4_minimal [NOTFOUND=return] dns myhostname

# ---- TO --------------------------------------------------------------

hosts:          files mdns4_minimal dns myhostname

# ---- THATS ALL -------------------------------------------------------

networks:       files



protocols:      db files

services:       db files

ethers:         db files

rpc:            db files



netgroup:       nis


Explanation:

Hostname resolving search first in files (/etc/hosts), then with avahi (zeroconf), then ask to dns server. And do not more stop if avahi does not find a local name as [NOTFOUND=return] forced. Hope its clear.



restart service



sudo systemctl restart systemd-resolved





share|improve this answer





















  • 3





    This sounds good, but it didn't fix it for me, even after executing "systemd-resolve --flush-caches". (Mine broke after upgrade from 16.04 to 18.04)

    – Charles Boling
    Oct 25 '18 at 4:19


















0














Here is what happen: systemd-resolved do not resolve local domain names if the names are not fully qualified names like mate.local


As told in a doc about Systemd-networkd, a good fix is to trim the /etc/nsswitch.conf file



sudo nano /etc/nsswitch.conf


Modify the hosts line



# /etc/nsswitch.conf

#

# Example configuration of GNU Name Service Switch functionality.

# If you have the `glibc-doc-reference' and `info' packages installed, try:

# `info libc "Name Service Switch"' for information about this file.



passwd:         compat systemd

group:          compat systemd

shadow:         compat

gshadow:        files

# ---- MODIFY THIS LINE ------------------------------------------------

# hosts:          files mdns4_minimal [NOTFOUND=return] dns myhostname

# ---- TO --------------------------------------------------------------

hosts:          files mdns4_minimal dns myhostname

# ---- THATS ALL -------------------------------------------------------

networks:       files



protocols:      db files

services:       db files

ethers:         db files

rpc:            db files



netgroup:       nis


Explanation:

Hostname resolving search first in files (/etc/hosts), then with avahi (zeroconf), then ask to dns server. And do not more stop if avahi does not find a local name as [NOTFOUND=return] forced. Hope its clear.



restart service



sudo systemctl restart systemd-resolved





share|improve this answer





















  • 3





    This sounds good, but it didn't fix it for me, even after executing "systemd-resolve --flush-caches". (Mine broke after upgrade from 16.04 to 18.04)

    – Charles Boling
    Oct 25 '18 at 4:19
















0












0








0







Here is what happen: systemd-resolved do not resolve local domain names if the names are not fully qualified names like mate.local


As told in a doc about Systemd-networkd, a good fix is to trim the /etc/nsswitch.conf file



sudo nano /etc/nsswitch.conf


Modify the hosts line



# /etc/nsswitch.conf

#

# Example configuration of GNU Name Service Switch functionality.

# If you have the `glibc-doc-reference' and `info' packages installed, try:

# `info libc "Name Service Switch"' for information about this file.



passwd:         compat systemd

group:          compat systemd

shadow:         compat

gshadow:        files

# ---- MODIFY THIS LINE ------------------------------------------------

# hosts:          files mdns4_minimal [NOTFOUND=return] dns myhostname

# ---- TO --------------------------------------------------------------

hosts:          files mdns4_minimal dns myhostname

# ---- THATS ALL -------------------------------------------------------

networks:       files



protocols:      db files

services:       db files

ethers:         db files

rpc:            db files



netgroup:       nis


Explanation:

Hostname resolving search first in files (/etc/hosts), then with avahi (zeroconf), then ask to dns server. And do not more stop if avahi does not find a local name as [NOTFOUND=return] forced. Hope its clear.



restart service



sudo systemctl restart systemd-resolved





share|improve this answer















Here is what happen: systemd-resolved do not resolve local domain names if the names are not fully qualified names like mate.local


As told in a doc about Systemd-networkd, a good fix is to trim the /etc/nsswitch.conf file



sudo nano /etc/nsswitch.conf


Modify the hosts line



# /etc/nsswitch.conf

#

# Example configuration of GNU Name Service Switch functionality.

# If you have the `glibc-doc-reference' and `info' packages installed, try:

# `info libc "Name Service Switch"' for information about this file.



passwd:         compat systemd

group:          compat systemd

shadow:         compat

gshadow:        files

# ---- MODIFY THIS LINE ------------------------------------------------

# hosts:          files mdns4_minimal [NOTFOUND=return] dns myhostname

# ---- TO --------------------------------------------------------------

hosts:          files mdns4_minimal dns myhostname

# ---- THATS ALL -------------------------------------------------------

networks:       files



protocols:      db files

services:       db files

ethers:         db files

rpc:            db files



netgroup:       nis


Explanation:

Hostname resolving search first in files (/etc/hosts), then with avahi (zeroconf), then ask to dns server. And do not more stop if avahi does not find a local name as [NOTFOUND=return] forced. Hope its clear.



restart service



sudo systemctl restart systemd-resolved






share|improve this answer














share|improve this answer



share|improve this answer








edited Jun 19 '18 at 8:28

























answered Jun 19 '18 at 8:14









cmak.frcmak.fr

2,2391121




2,2391121








  • 3





    This sounds good, but it didn't fix it for me, even after executing "systemd-resolve --flush-caches". (Mine broke after upgrade from 16.04 to 18.04)

    – Charles Boling
    Oct 25 '18 at 4:19
















  • 3





    This sounds good, but it didn't fix it for me, even after executing "systemd-resolve --flush-caches". (Mine broke after upgrade from 16.04 to 18.04)

    – Charles Boling
    Oct 25 '18 at 4:19










3




3





This sounds good, but it didn't fix it for me, even after executing "systemd-resolve --flush-caches". (Mine broke after upgrade from 16.04 to 18.04)

– Charles Boling
Oct 25 '18 at 4:19







This sounds good, but it didn't fix it for me, even after executing "systemd-resolve --flush-caches". (Mine broke after upgrade from 16.04 to 18.04)

– Charles Boling
Oct 25 '18 at 4:19















-1














This seems to related to this issue:



https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320



On a fresh install, /etc/resolv.conf is linked to /run/systemd/resolve/stub-resolv.conf instead of /run/systemd/resolve/resolv.conf.



Updating it per https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/comments/8 fixed it.






share|improve this answer
























  • Sorry, the story with /etc/resolv.conf and /run/systemd/resolve/stub-resolv.conf is not the issue of the bug report #1624320 -- The workaround found by some user is not a fix

    – cmak.fr
    Jun 19 '18 at 7:46


















-1














This seems to related to this issue:



https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320



On a fresh install, /etc/resolv.conf is linked to /run/systemd/resolve/stub-resolv.conf instead of /run/systemd/resolve/resolv.conf.



Updating it per https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/comments/8 fixed it.






share|improve this answer
























  • Sorry, the story with /etc/resolv.conf and /run/systemd/resolve/stub-resolv.conf is not the issue of the bug report #1624320 -- The workaround found by some user is not a fix

    – cmak.fr
    Jun 19 '18 at 7:46
















-1












-1








-1







This seems to related to this issue:



https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320



On a fresh install, /etc/resolv.conf is linked to /run/systemd/resolve/stub-resolv.conf instead of /run/systemd/resolve/resolv.conf.



Updating it per https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/comments/8 fixed it.






share|improve this answer













This seems to related to this issue:



https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320



On a fresh install, /etc/resolv.conf is linked to /run/systemd/resolve/stub-resolv.conf instead of /run/systemd/resolve/resolv.conf.



Updating it per https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/comments/8 fixed it.







share|improve this answer












share|improve this answer



share|improve this answer










answered Jun 19 '18 at 2:33









SarkeSarke

14616




14616













  • Sorry, the story with /etc/resolv.conf and /run/systemd/resolve/stub-resolv.conf is not the issue of the bug report #1624320 -- The workaround found by some user is not a fix

    – cmak.fr
    Jun 19 '18 at 7:46





















  • Sorry, the story with /etc/resolv.conf and /run/systemd/resolve/stub-resolv.conf is not the issue of the bug report #1624320 -- The workaround found by some user is not a fix

    – cmak.fr
    Jun 19 '18 at 7:46



















Sorry, the story with /etc/resolv.conf and /run/systemd/resolve/stub-resolv.conf is not the issue of the bug report #1624320 -- The workaround found by some user is not a fix

– cmak.fr
Jun 19 '18 at 7:46







Sorry, the story with /etc/resolv.conf and /run/systemd/resolve/stub-resolv.conf is not the issue of the bug report #1624320 -- The workaround found by some user is not a fix

– cmak.fr
Jun 19 '18 at 7:46




















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1047735%2fubuntu-18-04-not-recognizing-hostnames-from-router%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

Popular posts from this blog

Is there a lightweight tool to crop images quickly?Cropping Images using Command Line Tools OnlyHow to crop...

Image
Does every functor from Set to Set preserve products? Why avoid shared user accounts? What to look for when criticizing poetry? Is a new Boolean field better than a null reference when a value can be meaningfully absent? Why zero tolerance on nudity in space? In Linux what happens if 1000 files in a directory are moved to another location while another 300 files were added to the source directory? Why exactly do action photographers need high fps burst cameras? Can we harness gravitational potential energy? What sets the resolution of an analog resistive sensor? How to make ice magic work from a scientific point of view? ...
Read more

List of shipwrecks in 1808...

Image
Lists of shipwrecks by yearMaritime incidents in 1808 Anglo-Russian Warship of the lineBaltiskiHMS  Centaur HMS  Implacable Royal Navy The list of shipwrecks in 1808 includes some ships sunk, wrecked or otherwise lost during 1808. table of contents 1808 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Unknown date References January 1 January List of shipwrecks: 1 January 1808 Ship Country Description Barrett   United Kingdom The ship was holed by an anchor and sank at Falmouth, Jamaica. [1] Brisk   United Kingdom The ship sprang a leak and was abandoned by her crew. She was on a voyage from London to Africa. [2] Jenny   United Kingdom The sloop collided with a brig off Great Yarmouth, Norfolk and was abandoned by her crew. She was then driven ashore. Jenny was on a voyage from Boston, Lincolnshire to London. [3] Leighton   United Kingdom The ship was wrecked on the I...
Read more

Unit packagekit.service is masked Announcing the arrival of Valued Associate #679: Cesar...

Image
Why do C and C++ allow the expression (int) + 4*5? Can I take recommendation from someone I met at a conference? How to obtain original coefficients after performing gradient descent on normalized data? Does Prince Arnaud cause someone holding the Princess to lose? Indexes with the same object_id but different names Compiling and throwing simple dynamic exceptions at runtime for JVM My admission is revoked after accepting the admission offer Lights are flickering on and off after accidentally bumping into light switch Why did Israel vote against lifting the American embargo on Cuba? Why are two-digit numbers in Jonathan Swift's ...
Read more