Docker network adapter hijacking hostname resolutionLocal hostname resolution with local Ubuntu DNS server failsHow can I connect to remote windows domain knowing gateway hostname and domain name?Setting Internet GatewayDNS/Bind9 Name resolution with no FQDN auf sever itself fails, clients are okServer name resolution messed up when running PiHole in DockerUbuntu - Basic Host Name Resolution 18.04 IssuesUbuntu 18.04 - no DNS query
How likely are you to be injured by falling shot from a game shoot?
How time is defined in astronomical science
Can I say: “The train departs at 16 past every hour“?
Has an engineer called Trevor Jackson invented a revolutionary battery allowing for a car range of 1500 miles?
In what way were Renaissance battles like chess matches?
How should chips with pins on bottom be drawn?
If I am just replacing the car engine, do I need to replace the odometer as well?
How are side-channel attacks executed? What does an attacker need to execute a side channel attack?
How could Thanos survive this attack?
Washing the skin of a dead rat
Graph with cropped letters
Peano's dot notation
Can the Wish spell be used to allow someone to be able to cast all of their spells at will?
Comparison of C-Cl bond length in CH3Cl and CF3Cl
A Caesar cipher in Python3
Does the on'yomi of 輪 (リン) have any relation to the English "ring", or is it a coincidence?
Instant coffee melts like chocolate
Group Policy application on Domain Controllers
How do I disable vim from producing backup files?
Adding coordinate constant to file in QGIS
Induction Inequality Proof
Is it possible to be admitted to CS PhD programs (in US) with scholarship at age 18?
Is there evidence for Col. Vindman literally being a "Never Trump"?
Why was the Vulcan bomber used for the Falklands raid?
Docker network adapter hijacking hostname resolution
Local hostname resolution with local Ubuntu DNS server failsHow can I connect to remote windows domain knowing gateway hostname and domain name?Setting Internet GatewayDNS/Bind9 Name resolution with no FQDN auf sever itself fails, clients are okServer name resolution messed up when running PiHole in DockerUbuntu - Basic Host Name Resolution 18.04 IssuesUbuntu 18.04 - no DNS query
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
I'm struggling to figure out why my hostname resolution is being resolved locally and pointing to my docker networking interface and was hoping someone might be able to point me in the right direction.
I have 3 (relevant) entities in my network.
- A - An Asus RT--AC68U router -> hostname portal
- B - My normal laptop
- C - A server running Ubuntu 18.04 -> hostname server
The basic setup is as follows:
- A has dnsmasq active and is setup to always point 192.168.1.2 to C.
- A has dnsmasq setup to always forward subdomains of server.local to C
- A has a domain name .local setup internally
- C has docker v18.09.6 running
From B
> ping portal
PING portal.local (192.168.1.1): 56 data bytes
> ping portal.local
PING portal.local (192.168.1.1): 56 data bytes
> ping server
PING server.local (192.168.1.2): 56 data bytes
> ping server.local
PING server.local (192.168.1.2): 56 data bytes
> ping test.server.local
PING server.local (192.168.1.2): 56 data bytes
I would expect the same results from C. The first ping should be resolved due to the hostname file and loopback. The second and third should go to the router for resolution.
From C
> ping portal
ping portal.local (192.168.1.1) 56(84) bytes of data.
> ping portal.local
ping: portal.local: Name or service not known
> ping server
PING server (127.0.1.1) 56(84) bytes of data.
> ping server.local
PING server.local (172.17.0.1) 56(84) bytes of data.
> ping test.server.local
ping: test.server.local: Name or service not known
> ifconfig docker0
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
As you can see,
- portal hostname is resolved but including the domain results in unknown service
- server is resolved by loopback interface. Good
- server.local for some reason points to docker network interface
- test.server.local can't be resolved because it never gets to my router
I understand that the docker0 interface is setup as the default network for containers to join when no network is explicitly set. What I don't understand is why this network is handling resolution or at least not forwarding resolution on to my router when it can't resolve it.
networking server 18.04 dns docker
asked Jun 15 at 3:12
Matt RMatt R
1011 bronze badge
add a comment
|
I'm struggling to figure out why my hostname resolution is being resolved locally and pointing to my docker networking interface and was hoping someone might be able to point me in the right direction.
I have 3 (relevant) entities in my network.
- A - An Asus RT--AC68U router -> hostname portal
- B - My normal laptop
- C - A server running Ubuntu 18.04 -> hostname server
The basic setup is as follows:
- A has dnsmasq active and is setup to always point 192.168.1.2 to C.
- A has dnsmasq setup to always forward subdomains of server.local to C
- A has a domain name .local setup internally
- C has docker v18.09.6 running
From B
> ping portal
PING portal.local (192.168.1.1): 56 data bytes
> ping portal.local
PING portal.local (192.168.1.1): 56 data bytes
> ping server
PING server.local (192.168.1.2): 56 data bytes
> ping server.local
PING server.local (192.168.1.2): 56 data bytes
> ping test.server.local
PING server.local (192.168.1.2): 56 data bytes
I would expect the same results from C. The first ping should be resolved due to the hostname file and loopback. The second and third should go to the router for resolution.
From C
> ping portal
ping portal.local (192.168.1.1) 56(84) bytes of data.
> ping portal.local
ping: portal.local: Name or service not known
> ping server
PING server (127.0.1.1) 56(84) bytes of data.
> ping server.local
PING server.local (172.17.0.1) 56(84) bytes of data.
> ping test.server.local
ping: test.server.local: Name or service not known
> ifconfig docker0
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
As you can see,
- portal hostname is resolved but including the domain results in unknown service
- server is resolved by loopback interface. Good
- server.local for some reason points to docker network interface
- test.server.local can't be resolved because it never gets to my router
I understand that the docker0 interface is setup as the default network for containers to join when no network is explicitly set. What I don't understand is why this network is handling resolution or at least not forwarding resolution on to my router when it can't resolve it.
networking server 18.04 dns docker
asked Jun 15 at 3:12
Matt RMatt R
1011 bronze badge
add a comment
|
I'm struggling to figure out why my hostname resolution is being resolved locally and pointing to my docker networking interface and was hoping someone might be able to point me in the right direction.
I have 3 (relevant) entities in my network.
- A - An Asus RT--AC68U router -> hostname portal
- B - My normal laptop
- C - A server running Ubuntu 18.04 -> hostname server
The basic setup is as follows:
- A has dnsmasq active and is setup to always point 192.168.1.2 to C.
- A has dnsmasq setup to always forward subdomains of server.local to C
- A has a domain name .local setup internally
- C has docker v18.09.6 running
From B
> ping portal
PING portal.local (192.168.1.1): 56 data bytes
> ping portal.local
PING portal.local (192.168.1.1): 56 data bytes
> ping server
PING server.local (192.168.1.2): 56 data bytes
> ping server.local
PING server.local (192.168.1.2): 56 data bytes
> ping test.server.local
PING server.local (192.168.1.2): 56 data bytes
I would expect the same results from C. The first ping should be resolved due to the hostname file and loopback. The second and third should go to the router for resolution.
From C
> ping portal
ping portal.local (192.168.1.1) 56(84) bytes of data.
> ping portal.local
ping: portal.local: Name or service not known
> ping server
PING server (127.0.1.1) 56(84) bytes of data.
> ping server.local
PING server.local (172.17.0.1) 56(84) bytes of data.
> ping test.server.local
ping: test.server.local: Name or service not known
> ifconfig docker0
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
As you can see,
- portal hostname is resolved but including the domain results in unknown service
- server is resolved by loopback interface. Good
- server.local for some reason points to docker network interface
- test.server.local can't be resolved because it never gets to my router
I understand that the docker0 interface is setup as the default network for containers to join when no network is explicitly set. What I don't understand is why this network is handling resolution or at least not forwarding resolution on to my router when it can't resolve it.
networking server 18.04 dns docker
asked Jun 15 at 3:12
Matt RMatt R
1011 bronze badge
I'm struggling to figure out why my hostname resolution is being resolved locally and pointing to my docker networking interface and was hoping someone might be able to point me in the right direction.
I have 3 (relevant) entities in my network.
- A - An Asus RT--AC68U router -> hostname portal
- B - My normal laptop
- C - A server running Ubuntu 18.04 -> hostname server
The basic setup is as follows:
- A has dnsmasq active and is setup to always point 192.168.1.2 to C.
- A has dnsmasq setup to always forward subdomains of server.local to C
- A has a domain name .local setup internally
- C has docker v18.09.6 running
From B
> ping portal
PING portal.local (192.168.1.1): 56 data bytes
> ping portal.local
PING portal.local (192.168.1.1): 56 data bytes
> ping server
PING server.local (192.168.1.2): 56 data bytes
> ping server.local
PING server.local (192.168.1.2): 56 data bytes
> ping test.server.local
PING server.local (192.168.1.2): 56 data bytes
I would expect the same results from C. The first ping should be resolved due to the hostname file and loopback. The second and third should go to the router for resolution.
From C
> ping portal
ping portal.local (192.168.1.1) 56(84) bytes of data.
> ping portal.local
ping: portal.local: Name or service not known
> ping server
PING server (127.0.1.1) 56(84) bytes of data.
> ping server.local
PING server.local (172.17.0.1) 56(84) bytes of data.
> ping test.server.local
ping: test.server.local: Name or service not known
> ifconfig docker0
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
As you can see,
- portal hostname is resolved but including the domain results in unknown service
- server is resolved by loopback interface. Good
- server.local for some reason points to docker network interface
- test.server.local can't be resolved because it never gets to my router
I understand that the docker0 interface is setup as the default network for containers to join when no network is explicitly set. What I don't understand is why this network is handling resolution or at least not forwarding resolution on to my router when it can't resolve it.
networking server 18.04 dns docker
networking server 18.04 dns docker
asked Jun 15 at 3:12
Matt RMatt R
1011 bronze badge
asked Jun 15 at 3:12
Matt RMatt R
1011 bronze badge
asked Jun 15 at 3:12
Matt RMatt R
1011 bronze badge
asked Jun 15 at 3:12
Matt RMatt R
1011 bronze badge
asked Jun 15 at 3:12
Matt RMatt R
1011 bronze badge
1011 bronze badge
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/4.0/"u003ecc by-sa 4.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%2f1151192%2fdocker-network-adapter-hijacking-hostname-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%2f1151192%2fdocker-network-adapter-hijacking-hostname-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
