Thanks again Dan for taking the time to explain.
> stop using dig to debug your system.
Sorry thought I was using dig at your request...
I was originally using nslookup and ping to find out why I couldn't browse to
the server on phspi05 (phspi05 is actually controlling the heating and cooling
i
Thankyou for all the attention to this and the explanations Dan, but now
I am also confused...
I tend to think that if my desktop is able to successfully lookup the
host on the router (as per
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1817903) then
I should expect that my laptop on
$ dig phspi05.phs
; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> phspi05.phs
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 61787
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 6549
Sorry for slow response Dan, here is the output:
$ dig phspi05 @192.168.2.1
;; Warning: Message parser reports malformed message packet.
; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> phspi05 @192.168.2.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2588
;
Sorry thought I had responded already:
In answer to #5
same result = failure result
In answer to #6
For info Router is a Billion BiPAC 7800VDOX
Router is set to use public DNS:
208.67.222.222
212.159.6.10
Router is set with domain name of phs
Router has a table of static DNS defined:
Host IP
Yes, that sounds correct, your reply made me check, if I do:
nslookup phspi05.phs
I also get the same result...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1821491
Titl
Okay thanks for the attention, full output below:
$ systemd-resolve --status
Global
DNS Domain: phs
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
1
Public bug reported:
Mint 19 (Ubuntu Bionic)
Laptop so Using NetworkManager, and connecting wirelessly to LAN
Upgraded from Mint 18.3 so using resolvconf...
Versions:
network-manager: 1.10.6-2ubuntu1.1
resolvconf: 1.79ubuntu10.18.04.3 or 1.79ubuntu10.18.04.2
systemd: 237-3ubuntu10.15
dns is spe
I have installed 1.79ubunbtu10.18.04.3 from the bionic-proposed and
rebooted...
The result is different from before
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.
Installed resolvconf from bionic-proposed, all seems to working as it
should.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1817903
Title:
systemd-resolve appends "option
Sorry, my bad, it seems I miss read the first part of the wiki! Now
installed, will report back.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1817903
Title:
systemd-reso
On checking it seems that is the case. Tried a dozen different mirrors all give:
Failed to fetch
http://ports.ubuntu.com/ubuntu-ports/dists/bionic-proposed/main/binary-amd64/Packages
404 Not Found [IP: 91.189.88.150 80]
Which mirror do you recommend?
--
You received this bug notification be
I followed the instructions at
https://wiki.ubuntu.com/Testing/EnableProposed
but after repeated updates, it keeps telling me the it is not found:
$ sudo apt-get install resolvconf/bionic-proposed
Reading package lists... Done
Building dependency tree
Reading state information... Done
E:
Testing fix:
I added the ppa (same system) and updated resolvconf
then did:
$ sudo systemctl enable resolvconf-pull-resolved.path
OK
and
$ sudo systemctl enable resolvconf-pull-resolved.service
this gives: The unit files have no installation config
(not sure if this is expected ?), but it does
Yes that works, and many thanks for the explanation.
/etc/resolv.conf is now linked to /run/resolvconf/resolv.conf
and contains only the local proxy dns:
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YO
Thanks again for the help
Removed resolvconf:
sudo apt remove resolvconf
reboot
as expected now /etc/resolv.conf is linked to run/systemd/sub-resolv.conf
and contains only:
nameserver 127.0.0.53
options edns0
BUT now I cannot connect to anything, nslookup, ping fails, etc.
$ ping google.co
Thanks for the attention to this:
DNS servers: 208.67.220.220 (opend dns) and 212.159.6.10 (recommended by
isp)
typical sites: planthealth.co.uk, plus random others...
nslookup and dig ok
ping domain_name gives "Name or service not known"
ping ip ok
FF: Hmmm problem etc...
So this is my resolv.c
My update was from 237-3ubuntu10.11, which didn't have the problem (12
was never installed)
It seems I cannot easily downgrade via apt or synaptic, as the previous
versions do not seem to be in the repos, can you advise how to do so?
On a different machine on the same network I still have 237-3ub
It seems this breaks dns lookups on some system, see #1817903
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1811471
Title:
local resolver stub fails to handle multiple TC
Public bug reported:
Mint 19 (Ubuntu 18.04)
Following latest mint update done on 24/02/2019, DNS is broken
nslookup and dig of certain domain names work as expected, ping does not
(ip works but not domain name)
After a day of trial and error, testing I found that the problem lies
with the p
20 matches
Mail list logo
