> setting the router's search domain(s) will have *no effect at all* on
> lookups from any other system
well - this does depend on your specific dns nameserver program and
configuration; so I shouldn't say this without qualification :) It's
possible to have your router's dns use local lookups, in
> Sorry thought I was using dig at your request...
yes, sorry - dig is useful *but* it does only what you ask it
specifically to do (i.e. lookup the specific hostname you ask it for,
without appending any search domains to it). this is different from
everything else on your system, which uses get
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
> So it seems to me that lookups by systemd-resolved
> are failing to lookup the hostname on the local DNS
> (even if this is by design)
yes, this is by design. systemd-resolved never forwards "single label"
addresses to upstream nameservers.
> If the router has the hostname AND domainname defin
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 @192.168.2.1
...
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 21263
hmm, so, i'm confused now, in the description you said dig works when
querying your router directly? I guess that's not the case?
It certainly seems like this is not a issue with systemd - your prob
** Changed in: systemd (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821491
Title:
DNS lookup fails for local hosts
To manage notifications about this bug
$ 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
> $ dig phspi05 @192.168.2.1
> ;; Warning: Message parser reports malformed message packet.
that's generally not good...
> phspi05. 69314 IN A 192.168.2.35
ok, this is resolving the "single label" name. systemd-resolved never
forwards lookups of single-label names (except for
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
;
can you paste the output of dig:
$ dig phspi05 @192.168.2.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821491
Title:
DNS lookup fails for local hosts
To manage notifications about this bug go
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
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821491
Title:
DNS lookup fails for local hosts
To manage notifications about this bug
> $ nslookup phspi05 192.168.2.1
> Server: 192.168.2.1
> Address: 192.168.2.1#53
>
> Non-authoritative answer:
> Name: phspi05
> Address: 192.168.2.35
> ** server can't find phspi05: NXDOMAIN
your upstream ns is returning an address, but NXDOMAIN as well; I'm
pretty sure resolved sees t
On Thu, Apr 04, 2019 at 07:27:00PM -, Steve Roberts wrote:
> Yes, that sounds correct, your reply made me check, if I do:
> nslookup phspi05.phs
> I also get the same result...
By "same result", you mean the successful result or the failure result?
--
You received this bug notification bec
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821491
Title:
DNS lookup fails for lo
Ok, so you have no other DNS servers configured. So 192.168.2.1 is the
DNS server that's being used, but systemd-resolved doesn't like
something about either the request or the response and is not forwarding
it.
I note that you also say that this only fails for *local* hosts; i.e. if
I pay more a
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
Please show the complete output of systemd-resolve --status on this
system.
> I would expect that the nameserver set in network-manager would be
used
If it's not used, that can only be because you have some other
nameservers defined that are taking precedence; but we would need to see
the com
19 matches
Mail list logo
