Local nameserver issues
I have an Ubuntu 18.04 server that runs a DHCP server for a wired and wireless network and acts as a gateway to the internet (so PCs on the LAN have to connect to the server to access the internet). From PCs on the wired network, I can enter the server's hostname into a browser's address bar and development versions of websites that the server hosts are accessible. If I try the same thing with a PC that's on the wireless network, the server's hostname isn't resolved correctly so the website isn't displayed. PCs on either the wired or wireless network can access sites that are on the internet without any problems. Using "ping " on PCs on the wired network runs without errors but from PCs on the wireless network it fails to resolve the name. Any ideas why the DNS lookup is not working on the WiFi but working OK on the wired interfaces?
EDIT:
I'm using dnsmasq for dns lookups / dhcp control and netplan using NetworkManager for the network configuration (the wireless is set up to act as an access point for any device).
EDIT - in response to PEdroArthur's comment:
dig when run on server:-
; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> thincontroller
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59068
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;thincontroller. IN A
;; ANSWER SECTION:
thincontroller. 0 IN A 127.0.0.1
thincontroller. 0 IN A 127.0.1.1
thincontroller. 0 IN A 192.168.1.254
thincontroller. 0 IN A 10.42.0.254
;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Sat Mar 09 11:44:50 GMT 2019
;; MSG SIZE rcvd: 107
And on a PC connected wirelessly:-
; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> thincontroller
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 33715
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;thincontroller. IN A
;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Sat Mar 09 11:56:07 GMT 2019
;; MSG SIZE rcvd: 43
networking dns
add a comment |
I have an Ubuntu 18.04 server that runs a DHCP server for a wired and wireless network and acts as a gateway to the internet (so PCs on the LAN have to connect to the server to access the internet). From PCs on the wired network, I can enter the server's hostname into a browser's address bar and development versions of websites that the server hosts are accessible. If I try the same thing with a PC that's on the wireless network, the server's hostname isn't resolved correctly so the website isn't displayed. PCs on either the wired or wireless network can access sites that are on the internet without any problems. Using "ping " on PCs on the wired network runs without errors but from PCs on the wireless network it fails to resolve the name. Any ideas why the DNS lookup is not working on the WiFi but working OK on the wired interfaces?
EDIT:
I'm using dnsmasq for dns lookups / dhcp control and netplan using NetworkManager for the network configuration (the wireless is set up to act as an access point for any device).
EDIT - in response to PEdroArthur's comment:
dig when run on server:-
; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> thincontroller
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59068
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;thincontroller. IN A
;; ANSWER SECTION:
thincontroller. 0 IN A 127.0.0.1
thincontroller. 0 IN A 127.0.1.1
thincontroller. 0 IN A 192.168.1.254
thincontroller. 0 IN A 10.42.0.254
;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Sat Mar 09 11:44:50 GMT 2019
;; MSG SIZE rcvd: 107
And on a PC connected wirelessly:-
; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> thincontroller
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 33715
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;thincontroller. IN A
;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Sat Mar 09 11:56:07 GMT 2019
;; MSG SIZE rcvd: 43
networking dns
What DNS server are you running? Is there an option to keep wireless clients from reaching local IP addresses?
– heynnema
Mar 8 at 21:46
@heynnema: I haven't configured anything to stop wireless clients from reaching local IP addresses, entering the server's IP address into the address bar rather than the server name works fine on the wireless network, it's just not converting the name to an IP address which it does do on the wired network without any problems.
– Skizz
Mar 8 at 22:08
can you post the output ofdig hostname
in both machines?
– PEdroArthur
Mar 8 at 22:29
add a comment |
I have an Ubuntu 18.04 server that runs a DHCP server for a wired and wireless network and acts as a gateway to the internet (so PCs on the LAN have to connect to the server to access the internet). From PCs on the wired network, I can enter the server's hostname into a browser's address bar and development versions of websites that the server hosts are accessible. If I try the same thing with a PC that's on the wireless network, the server's hostname isn't resolved correctly so the website isn't displayed. PCs on either the wired or wireless network can access sites that are on the internet without any problems. Using "ping " on PCs on the wired network runs without errors but from PCs on the wireless network it fails to resolve the name. Any ideas why the DNS lookup is not working on the WiFi but working OK on the wired interfaces?
EDIT:
I'm using dnsmasq for dns lookups / dhcp control and netplan using NetworkManager for the network configuration (the wireless is set up to act as an access point for any device).
EDIT - in response to PEdroArthur's comment:
dig when run on server:-
; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> thincontroller
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59068
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;thincontroller. IN A
;; ANSWER SECTION:
thincontroller. 0 IN A 127.0.0.1
thincontroller. 0 IN A 127.0.1.1
thincontroller. 0 IN A 192.168.1.254
thincontroller. 0 IN A 10.42.0.254
;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Sat Mar 09 11:44:50 GMT 2019
;; MSG SIZE rcvd: 107
And on a PC connected wirelessly:-
; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> thincontroller
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 33715
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;thincontroller. IN A
;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Sat Mar 09 11:56:07 GMT 2019
;; MSG SIZE rcvd: 43
networking dns
I have an Ubuntu 18.04 server that runs a DHCP server for a wired and wireless network and acts as a gateway to the internet (so PCs on the LAN have to connect to the server to access the internet). From PCs on the wired network, I can enter the server's hostname into a browser's address bar and development versions of websites that the server hosts are accessible. If I try the same thing with a PC that's on the wireless network, the server's hostname isn't resolved correctly so the website isn't displayed. PCs on either the wired or wireless network can access sites that are on the internet without any problems. Using "ping " on PCs on the wired network runs without errors but from PCs on the wireless network it fails to resolve the name. Any ideas why the DNS lookup is not working on the WiFi but working OK on the wired interfaces?
EDIT:
I'm using dnsmasq for dns lookups / dhcp control and netplan using NetworkManager for the network configuration (the wireless is set up to act as an access point for any device).
EDIT - in response to PEdroArthur's comment:
dig when run on server:-
; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> thincontroller
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59068
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;thincontroller. IN A
;; ANSWER SECTION:
thincontroller. 0 IN A 127.0.0.1
thincontroller. 0 IN A 127.0.1.1
thincontroller. 0 IN A 192.168.1.254
thincontroller. 0 IN A 10.42.0.254
;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Sat Mar 09 11:44:50 GMT 2019
;; MSG SIZE rcvd: 107
And on a PC connected wirelessly:-
; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> thincontroller
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 33715
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;thincontroller. IN A
;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Sat Mar 09 11:56:07 GMT 2019
;; MSG SIZE rcvd: 43
networking dns
networking dns
edited 2 days ago
Skizz
asked Mar 8 at 20:38
SkizzSkizz
3712616
3712616
What DNS server are you running? Is there an option to keep wireless clients from reaching local IP addresses?
– heynnema
Mar 8 at 21:46
@heynnema: I haven't configured anything to stop wireless clients from reaching local IP addresses, entering the server's IP address into the address bar rather than the server name works fine on the wireless network, it's just not converting the name to an IP address which it does do on the wired network without any problems.
– Skizz
Mar 8 at 22:08
can you post the output ofdig hostname
in both machines?
– PEdroArthur
Mar 8 at 22:29
add a comment |
What DNS server are you running? Is there an option to keep wireless clients from reaching local IP addresses?
– heynnema
Mar 8 at 21:46
@heynnema: I haven't configured anything to stop wireless clients from reaching local IP addresses, entering the server's IP address into the address bar rather than the server name works fine on the wireless network, it's just not converting the name to an IP address which it does do on the wired network without any problems.
– Skizz
Mar 8 at 22:08
can you post the output ofdig hostname
in both machines?
– PEdroArthur
Mar 8 at 22:29
What DNS server are you running? Is there an option to keep wireless clients from reaching local IP addresses?
– heynnema
Mar 8 at 21:46
What DNS server are you running? Is there an option to keep wireless clients from reaching local IP addresses?
– heynnema
Mar 8 at 21:46
@heynnema: I haven't configured anything to stop wireless clients from reaching local IP addresses, entering the server's IP address into the address bar rather than the server name works fine on the wireless network, it's just not converting the name to an IP address which it does do on the wired network without any problems.
– Skizz
Mar 8 at 22:08
@heynnema: I haven't configured anything to stop wireless clients from reaching local IP addresses, entering the server's IP address into the address bar rather than the server name works fine on the wireless network, it's just not converting the name to an IP address which it does do on the wired network without any problems.
– Skizz
Mar 8 at 22:08
can you post the output of
dig hostname
in both machines?– PEdroArthur
Mar 8 at 22:29
can you post the output of
dig hostname
in both machines?– PEdroArthur
Mar 8 at 22:29
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%2f1124135%2flocal-nameserver-issues%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%2f1124135%2flocal-nameserver-issues%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
What DNS server are you running? Is there an option to keep wireless clients from reaching local IP addresses?
– heynnema
Mar 8 at 21:46
@heynnema: I haven't configured anything to stop wireless clients from reaching local IP addresses, entering the server's IP address into the address bar rather than the server name works fine on the wireless network, it's just not converting the name to an IP address which it does do on the wired network without any problems.
– Skizz
Mar 8 at 22:08
can you post the output of
dig hostname
in both machines?– PEdroArthur
Mar 8 at 22:29