[SOLVED]DNS timing out but I can dig @ just fine - Linux Mint Forums

[SOLVED]DNS timing out but I can dig @ just fine

Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.

Locked

22 posts

1
2
Next

ryron01

[SOLVED]DNS timing out but I can dig @ just fine

Post by ryron01 » Tue Nov 06, 2018 3:00 pm

DNS lookups do not appear to be working as expected. I was thinking I had a network issue but manual lookups are successful. I don't know exactly how to discribe the problem other than to show it. I don't know how to even begin debugging this issue. Any ideas?

Code: Select all

System:    Host: mediaserver Kernel: 4.4.6-generic.fitlet x86_64 (64 bit gcc: 4.8.4) Console: tty 0
           Distro: Linux Mint 18 Sarah
Machine:   System: CompuLab product: fitlet v: 1.0
           Mobo: CompuLab model: fitlet v: 1.3 Bios: American Megatrends v: SBCFLT_0.08.08 date: 11/30/2015
Network:   Card: Intel I211 Gigabit Network Connection driver: igb v: 5.3.0-k port: e000 bus-ID: 01:00.0
           IF: enp1s0 state: up speed: 1000 Mbps duplex: full mac: <filter>

Code: Select all

mediaserver 10:52:06 / $ dig google.com

; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com
;; global options: +cmd
;; connection timed out; no servers could be reached

Code: Select all

mediaserver 10:56:02 / $ dig google.com @1.1.1.1

; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2965
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1452
;; QUESTION SECTION:
;google.com.			IN	A

;; ANSWER SECTION:
google.com.		119	IN	A	172.217.4.142

;; Query time: 20 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Tue Nov 06 10:56:11 PST 2018
;; MSG SIZE  rcvd: 55

Code: Select all

nmcli dev show | grep DNS
IP4.DNS[1]:                             1.1.1.1
IP4.DNS[2]:                             8.8.8.8
IP4.DNS[3]:                             192.168.1.1

Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.

AZgl1800: Level 20; Posts: 11171; Joined: Thu Dec 31, 2015 3:20 am; Location: Oklahoma where the wind comes Sweeping down the Plains; Contact:
Contact AZgl1800

Website

Re: DNS timing out but I can dig @ just fine

Post by AZgl1800 » Tue Nov 06, 2018 3:03 pm

why are you using 192.168.1.1 ??

that is your ISP's modem to the internet, it does not have a DNS in it normally.

I would remove that and see how things go.

LM21.3 Cinnamon ASUS FX705GM | Donate to Mint https://www.patreon.com/linux_mint

DAMIEN1307

Re: DNS timing out but I can dig @ just fine

Post by DAMIEN1307 » Tue Nov 06, 2018 3:10 pm

hi AZg...my 192.168.1.1 is my netgear nighthawk ROUTER and not my modem.

trytip: Level 14; Posts: 5366; Joined: Tue Jul 05, 2016 1:20 pm

Re: DNS timing out but I can dig @ just fine

Post by trytip » Tue Nov 06, 2018 3:14 pm

how do you set your DNS.

Last edited by trytip on Tue Nov 06, 2018 8:00 pm, edited 1 time in total.

HaveaMint: Level 6; Posts: 1085; Joined: Fri Feb 02, 2018 9:56 pm

Re: DNS timing out but I can dig @ just fine

Post by HaveaMint » Tue Nov 06, 2018 4:02 pm

Holy bejebus I'm going to have nightmares of all those windows out to get me.

"Tune for maximum Smoke and then read the Instructions".

ryron01

Re: DNS timing out but I can dig @ just fine

Post by ryron01 » Tue Nov 06, 2018 4:22 pm

DNS is set via DHCP from my router. 192.168.1.1 is the router and not the modem.

Code: Select all

mediaserver 12:20:01 ~ $ dig google.com @192.168.1.1

; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com @192.168.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46578
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;google.com.			IN	A

;; ANSWER SECTION:
google.com.		9	IN	A	172.217.0.46

;; Query time: 13 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Tue Nov 06 12:20:22 PST 2018
;; MSG SIZE  rcvd: 55

It is also honoring requests when I specify it directly

gm10

Re: DNS timing out but I can dig @ just fine

Post by gm10 » Tue Nov 06, 2018 5:09 pm

ryron01 wrote: ⤴Tue Nov 06, 2018 3:00 pm DNS lookups do not appear to be working as expected. I was thinking I had a network issue but manual lookups are successful. I don't know exactly how to discribe the problem other than to show it. I don't know how to even begin debugging this issue. Any ideas?

Seems like your systemd-resolved service has a problem. Is it running? Try:

Code: Select all

systemctl restart systemd-resolved

If that doesn't help, check the logs:

Code: Select all

journalctl -u systemd-resolved

ryron01

Re: DNS timing out but I can dig @ just fine

Post by ryron01 » Tue Nov 06, 2018 5:21 pm

Code: Select all

● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/lib/systemd/system/systemd-resolved.service; disabled; vendor preset: enabled)
  Drop-In: /lib/systemd/system/systemd-resolved.service.d
           └─resolvconf.conf
   Active: active (running) since Tue 2018-11-06 13:19:25 PST; 28s ago
     Docs: man:systemd-resolved.service(8)
 Main PID: 5098 (systemd-resolve)
   Status: "Processing requests..."
   CGroup: /system.slice/systemd-resolved.service
           └─5098 /lib/systemd/systemd-resolved

Nov 06 13:19:25 mediaserver systemd[1]: Starting Network Name Resolution...
Nov 06 13:19:25 mediaserver systemd-resolved[5098]: Positive Trust Anchors:
Nov 06 13:19:25 mediaserver systemd-resolved[5098]: . IN DS    19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Nov 06 13:19:25 mediaserver systemd-resolved[5098]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-a
Nov 06 13:19:25 mediaserver systemd-resolved[5098]: Using system hostname 'mediaserver'.
Nov 06 13:19:25 mediaserver systemd[1]: Started Network Name Resolution.

Code: Select all

mediaserver 13:20:01 ~ $
mediaserver 13:20:01 ~ $ nslookup google.com
;; connection timed out; no servers could be reached

Its the weirdest thing.

gm10

Re: DNS timing out but I can dig @ just fine

Post by gm10 » Tue Nov 06, 2018 5:29 pm

ryron01 wrote: ⤴Tue Nov 06, 2018 5:21 pm Its the weirdest thing.

No, it's not, at least not entirely. Look at what you posted (emphasis added):

● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/lib/systemd/system/systemd-resolved.service; disabled; vendor preset: enabled)

I'm not quite sure why it would be running but disabled, but enable and restart it regardless:

Code: Select all

systemctl enable systemd-resolved
systemctl restart systemd-resolved

ryron01

Re: DNS timing out but I can dig @ just fine

Post by ryron01 » Tue Nov 06, 2018 5:48 pm

gm10 wrote: ⤴Tue Nov 06, 2018 5:29 pm
ryron01 wrote: ⤴Tue Nov 06, 2018 5:21 pm Its the weirdest thing.
No, it's not, at least not entirely. Look at what you posted (emphasis added):

● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/lib/systemd/system/systemd-resolved.service; disabled; vendor preset: enabled)
I'm not quite sure why it would be running but disabled, but enable and restart it regardless:
Code: Select all
systemctl enable systemd-resolved
systemctl restart systemd-resolved

Nice Catch, I suck at details. Unfortunately that was not it.

Code: Select all

● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
  Drop-In: /lib/systemd/system/systemd-resolved.service.d
           └─resolvconf.conf
   Active: active (running) since Tue 2018-11-06 13:37:27 PST; 45s ago
     Docs: man:systemd-resolved.service(8)
 Main PID: 5957 (systemd-resolve)
   Status: "Processing requests..."
   CGroup: /system.slice/systemd-resolved.service
           └─5957 /lib/systemd/systemd-resolved

Nov 06 13:37:26 mediaserver systemd[1]: Starting Network Name Resolution...
Nov 06 13:37:26 mediaserver systemd-resolved[5957]: Positive Trust Anchors:
Nov 06 13:37:26 mediaserver systemd-resolved[5957]: . IN DS    19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Nov 06 13:37:26 mediaserver systemd-resolved[5957]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-a
Nov 06 13:37:26 mediaserver systemd-resolved[5957]: Using system hostname 'mediaserver'.
Nov 06 13:37:27 mediaserver systemd[1]: Started Network Name Resolution.

Code: Select all

mediaserver 13:39:00 ~ $ nslookup google.com
;; connection timed out; no servers could be reached

gm10

Re: DNS timing out but I can dig @ just fine

Post by gm10 » Tue Nov 06, 2018 5:53 pm

Maybe this gives a better error message:

Code: Select all

systemd-resolve google.com

Also check that this exists and points to the default 127.0.0.53:

Code: Select all

cat /etc/resolv.conf

Did you check the journal? I know the status command prints some of it but I was hoping for a bit more:

Code: Select all

journalctl -u systemd-resolved

Otherwise run

Code: Select all

sudo systemctl edit systemd-resolved

Paste this, save and exit, then restart the service, try again and check the log again:

Code: Select all

[Service]
Environment=SYSTEMD_LOG_LEVEL=debug

ryron01

Re: DNS timing out but I can dig @ just fine

Post by ryron01 » Tue Nov 06, 2018 6:12 pm

Code: Select all

mediaserver 14:03:18 ~ $ systemd-resolve google.com
google.com: 172.217.14.110

-- Information acquired via protocol DNS in 25.4ms.
-- Data is authenticated: no

That seems to be working, but nothing else system level for DNS resolution.

Nothin in the debug logs make sense. I see timeouts reached for transactions, but then I seemingly see answer for that transaction. Although I admit that I don't understand what I am looking at.

Code: Select all

Nov 06 14:01:22 mediaserver systemd[1]: Stopping Network Name Resolution...
Nov 06 14:01:22 mediaserver systemd[1]: Stopped Network Name Resolution.
Nov 06 14:01:22 mediaserver systemd[1]: Starting Network Name Resolution...
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Positive Trust Anchors:
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: . IN DS    19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-a
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Using system hostname 'mediaserver'.
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: New scope on link *, protocol dns, family *
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Found new link 2/enp1s0
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Found new link 1/lo
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: New scope on link enp1s0, protocol llmnr, family AF_INET6
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Excercising transaction 63150 for <mediaserver. IN ANY> on scope llmnr on enp1s0/AF_INET6.
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Delaying llmnr transaction for 5862us.
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: New scope on link enp1s0, protocol llmnr, family AF_INET
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Excercising transaction 50747 for <mediaserver. IN ANY> on scope llmnr on enp1s0/AF_INET.
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Delaying llmnr transaction for 75102us.
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus interface=org.freedesktop.DB
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.124 object=n/a interface=n/a member=n/a cookie=1 reply_co
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus interface=org.freedesktop.DB
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.124 object=n/a interface=n/a member=n/a cookie=4 reply_co
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus interface=org.freedesktop.DB
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.124 object=n/a interface=n/a member=n/a cookie=5 reply_co
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus interface=org.freedesktop.DB
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.124 object=n/a interface=n/a member=n/a cookie=1 reply_co
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus interface=org.freedesktop.DB
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.124 object=n/a interface=n/a member=n/a cookie=4 reply_co
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus interface=org.freedesktop.DB
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.124 object=n/a interface=n/a member=n/a cookie=5 reply_co
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Timeout reached on transaction 63150.
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Retrying transaction 63150.
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Excercising transaction 63150 for <mediaserver. IN ANY> on scope llmnr on enp1s0/AF_INET6.
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Sending query packet with id 63150 on interface 2/AF_INET6.
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Got LLMNR query packet for id 63150
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Sending response packet with id 63150 on interface 2/AF_INET6.
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Got LLMNR reply packet for id 63150
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Processing incoming packet on transaction 63150.
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Got message type=signal sender=org.freedesktop.DBus destination=:1.124 object=/org/freedesktop/DBus interface=org.freedesktop.DBus
Nov 06 14:01:22 mediaserver systemd-resolved[7022]: Got message type=signal sender=org.freedesktop.DBus destination=:1.124 object=/org/freedesktop/DBus interface=org.freedesktop.DBus
Nov 06 14:01:22 mediaserver systemd[1]: Started Network Name Resolution.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Timeout reached on transaction 50747.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Retrying transaction 50747.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Excercising transaction 50747 for <mediaserver. IN ANY> on scope llmnr on enp1s0/AF_INET.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Sending query packet with id 50747 on interface 2/AF_INET.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Timeout reached on transaction 63150.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Retrying transaction 63150.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Excercising transaction 63150 for <mediaserver. IN ANY> on scope llmnr on enp1s0/AF_INET6.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Sending query packet with id 63150 on interface 2/AF_INET6.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Got LLMNR query packet for id 50747
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Sending response packet with id 50747 on interface 2/AF_INET.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Got LLMNR query packet for id 63150
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Sending response packet with id 63150 on interface 2/AF_INET6.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Got LLMNR reply packet for id 50747
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Processing incoming packet on transaction 50747.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Got LLMNR reply packet for id 63150
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Processing incoming packet on transaction 63150.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Timeout reached on transaction 50747.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Retrying transaction 50747.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Excercising transaction 50747 for <mediaserver. IN ANY> on scope llmnr on enp1s0/AF_INET.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Sending query packet with id 50747 on interface 2/AF_INET.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Timeout reached on transaction 63150.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Retrying transaction 63150.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Excercising transaction 63150 for <mediaserver. IN ANY> on scope llmnr on enp1s0/AF_INET6.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Sending query packet with id 63150 on interface 2/AF_INET6.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Got LLMNR query packet for id 50747
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Sending response packet with id 50747 on interface 2/AF_INET.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Got LLMNR query packet for id 63150
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Sending response packet with id 63150 on interface 2/AF_INET6.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Got LLMNR reply packet for id 50747
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Processing incoming packet on transaction 50747.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Got LLMNR reply packet for id 63150
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Processing incoming packet on transaction 63150.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Timeout reached on transaction 50747.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Retrying transaction 50747.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Excercising transaction 50747 for <mediaserver. IN ANY> on scope llmnr on enp1s0/AF_INET.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Sending query packet with id 50747 on interface 2/AF_INET.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Timeout reached on transaction 63150.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Retrying transaction 63150.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Transaction 63150 for <mediaserver. IN ANY> on scope llmnr on enp1s0/AF_INET6 now complete with <attempts-max-reached> from none (u
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Record mediaserver. IN AAAA  fe80::201:c0ff:fe1c:86e1 successfully probed.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Freeing transaction 63150.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Got LLMNR query packet for id 50747
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Sending response packet with id 50747 on interface 2/AF_INET.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Got LLMNR reply packet for id 50747
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Processing incoming packet on transaction 50747.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Timeout reached on transaction 50747.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Retrying transaction 50747.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Transaction 50747 for <mediaserver. IN ANY> on scope llmnr on enp1s0/AF_INET now complete with <attempts-max-reached> from none (un
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Record mediaserver. IN A     192.168.1.116 successfully probed.
Nov 06 14:01:23 mediaserver systemd-resolved[7022]: Freeing transaction 50747.

gm10

Re: DNS timing out but I can dig @ just fine

Post by gm10 » Tue Nov 06, 2018 6:16 pm

No, that's helpful, apparently it's trying to use IPv6 addressing, try to disable that for that connection (connection properties > IPv6 > set to ignore and then re-connect the connection).

By the way, if that fixes it, don't forget to remove the debug output setting again or your logs will keep getting spammed.

trytip: Level 14; Posts: 5366; Joined: Tue Jul 05, 2016 1:20 pm

Re: DNS timing out but I can dig @ just fine

Post by trytip » Tue Nov 06, 2018 8:05 pm

a while back when i tested DNS in my router i left the computer alone. a simple test is, after you set DNS in router/modem boot a live mint and connect to the internet and see how it resolves there.

ryron01

Re: DNS timing out but I can dig @ just fine

Post by ryron01 » Mon Nov 12, 2018 6:56 pm

gm10 wrote: ⤴Tue Nov 06, 2018 6:16 pm No, that's helpful, apparently it's trying to use IPv6 addressing, try to disable that for that connection (connection properties > IPv6 > set to ignore and then re-connect the connection).

By the way, if that fixes it, don't forget to remove the debug output setting again or your logs will keep getting spammed.

I forgot to post back. I tried this and it had the same behavior. So then I went down the route of making IPV6 work on my local network. That was successful but DNS was still not working.

So I'm still stuck. At this point I'm not certain that DNS lookups are using systemd-resolved. It seems to be working just fine, but nothing else is.

trytip: Level 14; Posts: 5366; Joined: Tue Jul 05, 2016 1:20 pm

Re: DNS timing out but I can dig @ just fine

Post by trytip » Mon Nov 12, 2018 7:13 pm

do you get the same reaction when you connect with a live mint?

ryron01

Re: DNS timing out but I can dig @ just fine

Post by ryron01 » Mon Nov 12, 2018 7:15 pm

I'm guessing I should have a resolv.conf

Code: Select all

mediaserver 15:15:04 ~ $ sudo stat /run/resolvconf/resolv.conf
stat: cannot stat '/run/resolvconf/resolv.conf': No such file or directory
mediaserver 15:16:04 ~ $ stat /etc/resolv.conf
  File: '/etc/resolv.conf' -> '../run/resolvconf/resolv.conf'
  Size: 29        	Blocks: 0          IO Block: 4096   symbolic link
Device: 811h/2065d	Inode: 131053      Links: 1
Access: (0777/lrwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2018-11-12 00:08:21.178389467 -0800
Modify: 2016-07-18 02:26:44.723384165 -0700
Change: 2016-07-18 02:26:44.723384165 -0700
 Birth: -

Code: Select all

mediaserver 15:16:08 ~ $ sudo stat /run/resolvconf/resolv.conf
stat: cannot stat '/run/resolvconf/resolv.conf': No such file or directory
mediaserver 15:16:35 ~ $

ryron01

Re: DNS timing out but I can dig @ just fine

Post by ryron01 » Mon Nov 12, 2018 7:16 pm

trytip wrote: ⤴Mon Nov 12, 2018 7:13 pm do you get the same reaction when you connect with a live mint?

I'm embarrassed but I don't quite understand what you mean by this?

ryron01

Re: DNS timing out but I can dig @ just fine

Post by ryron01 » Mon Nov 12, 2018 7:22 pm

ryron01 wrote: ⤴Mon Nov 12, 2018 7:15 pm I'm guessing I should have a resolv.conf

Code: Select all

mediaserver 15:15:04 ~ $ sudo stat /run/resolvconf/resolv.conf
stat: cannot stat '/run/resolvconf/resolv.conf': No such file or directory
mediaserver 15:16:04 ~ $ stat /etc/resolv.conf
  File: '/etc/resolv.conf' -> '../run/resolvconf/resolv.conf'
  Size: 29        	Blocks: 0          IO Block: 4096   symbolic link
Device: 811h/2065d	Inode: 131053      Links: 1
Access: (0777/lrwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2018-11-12 00:08:21.178389467 -0800
Modify: 2016-07-18 02:26:44.723384165 -0700
Change: 2016-07-18 02:26:44.723384165 -0700
 Birth: -

Code: Select all

mediaserver 15:16:08 ~ $ sudo stat /run/resolvconf/resolv.conf
stat: cannot stat '/run/resolvconf/resolv.conf': No such file or directory
mediaserver 15:16:35 ~ $

Code: Select all

mediaserver 15:20:30 ~ $ sudo mkdir -p /run/resolvconf/
mediaserver 15:20:48 ~ $ sudo vi /run/resolvconf/resolv.conf
mediaserver 15:21:00 ~ $ host google.com
google.com has address 216.58.194.206
google.com has IPv6 address 2607:f8b0:4005:804::200e
google.com mail is handled by 30 alt2.aspmx.l.google.com.
google.com mail is handled by 20 alt1.aspmx.l.google.com.
google.com mail is handled by 50 alt4.aspmx.l.google.com.
google.com mail is handled by 10 aspmx.l.google.com.
google.com mail is handled by 40 alt3.aspmx.l.google.com.
mediaserver 15:21:05 ~ $

uuugggggg I should have tried this awhile ago. So now I just need to figure why that file went missing and what I have to do to get NetworkManager to .... manage it.

trytip: Level 14; Posts: 5366; Joined: Tue Jul 05, 2016 1:20 pm

Re: DNS timing out but I can dig @ just fine

Post by trytip » Mon Nov 12, 2018 8:38 pm

ryron01 wrote: ⤴Mon Nov 12, 2018 7:16 pm
trytip wrote: ⤴Mon Nov 12, 2018 7:13 pm do you get the same reaction when you connect with a live mint?
I'm embarrassed but I don't quite understand what you mean by this?

just means boot the mint usb or cd that you used for installing mint. connect to the internet and see how the browser works

Locked

22 posts

1
2
Next

Return to “Networking”