DNS problem using Draytek router for local name resolution
I'm running Ubuntu 18.04 with a Draytek 2860n router connecting to the
internet. The router provides resolution of some LAN addresses for me:-
For example my printer:-
chris@esprimo$ dig @192.168.1.1 oki
; <<>> DiG 9.11.3-1ubuntu1.3-Ubuntu <<>> @192.168.1.1 oki
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64099
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: Message has 3 extra bytes at end
;; QUESTION SECTION:
;oki. IN A
;; ANSWER SECTION:
oki. 86400 IN A 192.168.1.50
;; Query time: 0 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Mon Feb 04 22:49:43 GMT 2019
;; MSG SIZE rcvd: 40
chris@esprimo$
The system is set up with a static IP and has 192.168.1.1 set as the
DNS server:-
chris@esprimo$ nmcli
eth0: connected to Wired connection 1
"Intel 82579LM Gigabit (Lewisville)"
ethernet (e1000e), 90:1B:0E:06:BC:91, hw, mtu 1500
ip4 default
inet4 192.168.1.3/24
route4 192.168.1.0/24
route4 169.254.0.0/16
route4 192.168.20.1/32
route4 0.0.0.0/0
inet6 fe80::921b:eff:fe06:bc91/64
route6 ff00::/8
route6 fe80::/64
route6 fe80::/64
lo: unmanaged
"lo"
loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
DNS configuration:
servers: 192.168.1.1
interface: eth0
But I can't actually connect to my printer by name:-
chris@esprimo$ ping oki
ping: oki: Temporary failure in name resolution
ping: oki.zbmc.eu: Temporary failure in name resolution
chris@esprimo$
Other commands report the same "Temporary failure in name resolution".
This is driving me crazy! How can I diagnose and resolve the problem?
networking dns
add a comment |
I'm running Ubuntu 18.04 with a Draytek 2860n router connecting to the
internet. The router provides resolution of some LAN addresses for me:-
For example my printer:-
chris@esprimo$ dig @192.168.1.1 oki
; <<>> DiG 9.11.3-1ubuntu1.3-Ubuntu <<>> @192.168.1.1 oki
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64099
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: Message has 3 extra bytes at end
;; QUESTION SECTION:
;oki. IN A
;; ANSWER SECTION:
oki. 86400 IN A 192.168.1.50
;; Query time: 0 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Mon Feb 04 22:49:43 GMT 2019
;; MSG SIZE rcvd: 40
chris@esprimo$
The system is set up with a static IP and has 192.168.1.1 set as the
DNS server:-
chris@esprimo$ nmcli
eth0: connected to Wired connection 1
"Intel 82579LM Gigabit (Lewisville)"
ethernet (e1000e), 90:1B:0E:06:BC:91, hw, mtu 1500
ip4 default
inet4 192.168.1.3/24
route4 192.168.1.0/24
route4 169.254.0.0/16
route4 192.168.20.1/32
route4 0.0.0.0/0
inet6 fe80::921b:eff:fe06:bc91/64
route6 ff00::/8
route6 fe80::/64
route6 fe80::/64
lo: unmanaged
"lo"
loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
DNS configuration:
servers: 192.168.1.1
interface: eth0
But I can't actually connect to my printer by name:-
chris@esprimo$ ping oki
ping: oki: Temporary failure in name resolution
ping: oki.zbmc.eu: Temporary failure in name resolution
chris@esprimo$
Other commands report the same "Temporary failure in name resolution".
This is driving me crazy! How can I diagnose and resolve the problem?
networking dns
add a comment |
I'm running Ubuntu 18.04 with a Draytek 2860n router connecting to the
internet. The router provides resolution of some LAN addresses for me:-
For example my printer:-
chris@esprimo$ dig @192.168.1.1 oki
; <<>> DiG 9.11.3-1ubuntu1.3-Ubuntu <<>> @192.168.1.1 oki
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64099
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: Message has 3 extra bytes at end
;; QUESTION SECTION:
;oki. IN A
;; ANSWER SECTION:
oki. 86400 IN A 192.168.1.50
;; Query time: 0 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Mon Feb 04 22:49:43 GMT 2019
;; MSG SIZE rcvd: 40
chris@esprimo$
The system is set up with a static IP and has 192.168.1.1 set as the
DNS server:-
chris@esprimo$ nmcli
eth0: connected to Wired connection 1
"Intel 82579LM Gigabit (Lewisville)"
ethernet (e1000e), 90:1B:0E:06:BC:91, hw, mtu 1500
ip4 default
inet4 192.168.1.3/24
route4 192.168.1.0/24
route4 169.254.0.0/16
route4 192.168.20.1/32
route4 0.0.0.0/0
inet6 fe80::921b:eff:fe06:bc91/64
route6 ff00::/8
route6 fe80::/64
route6 fe80::/64
lo: unmanaged
"lo"
loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
DNS configuration:
servers: 192.168.1.1
interface: eth0
But I can't actually connect to my printer by name:-
chris@esprimo$ ping oki
ping: oki: Temporary failure in name resolution
ping: oki.zbmc.eu: Temporary failure in name resolution
chris@esprimo$
Other commands report the same "Temporary failure in name resolution".
This is driving me crazy! How can I diagnose and resolve the problem?
networking dns
I'm running Ubuntu 18.04 with a Draytek 2860n router connecting to the
internet. The router provides resolution of some LAN addresses for me:-
For example my printer:-
chris@esprimo$ dig @192.168.1.1 oki
; <<>> DiG 9.11.3-1ubuntu1.3-Ubuntu <<>> @192.168.1.1 oki
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64099
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: Message has 3 extra bytes at end
;; QUESTION SECTION:
;oki. IN A
;; ANSWER SECTION:
oki. 86400 IN A 192.168.1.50
;; Query time: 0 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Mon Feb 04 22:49:43 GMT 2019
;; MSG SIZE rcvd: 40
chris@esprimo$
The system is set up with a static IP and has 192.168.1.1 set as the
DNS server:-
chris@esprimo$ nmcli
eth0: connected to Wired connection 1
"Intel 82579LM Gigabit (Lewisville)"
ethernet (e1000e), 90:1B:0E:06:BC:91, hw, mtu 1500
ip4 default
inet4 192.168.1.3/24
route4 192.168.1.0/24
route4 169.254.0.0/16
route4 192.168.20.1/32
route4 0.0.0.0/0
inet6 fe80::921b:eff:fe06:bc91/64
route6 ff00::/8
route6 fe80::/64
route6 fe80::/64
lo: unmanaged
"lo"
loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
DNS configuration:
servers: 192.168.1.1
interface: eth0
But I can't actually connect to my printer by name:-
chris@esprimo$ ping oki
ping: oki: Temporary failure in name resolution
ping: oki.zbmc.eu: Temporary failure in name resolution
chris@esprimo$
Other commands report the same "Temporary failure in name resolution".
This is driving me crazy! How can I diagnose and resolve the problem?
networking dns
networking dns
asked Feb 4 at 23:07
Chris GreenChris Green
11
11
add a comment |
add a comment |
0
active
oldest
votes
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1115668%2fdns-problem-using-draytek-router-for-local-name-resolution%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1115668%2fdns-problem-using-draytek-router-for-local-name-resolution%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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