Domaincontroller not forwarding dns requests
0
I've setup a test environment that looks like:
- modem/router connected to physical host
- hyper-v manager running on physical host
- Virtual Switch connected to external network
- Two VMs (DC + client) connected to virtual switch
The DC has the following static config:
- IP: 192.168.1.100
- Subn: 255.255.255.0
- Gateway: 192.168.1.1
- DNS 127.0.0.1
- External DNS 8.8.8.8 added to 'Forwarders' within DNS Management.
Client config:
- IP: 192.168.1.101
- Subn: 255.255.255.0
- Gateway: 192.168.1.100
- DNS: 192.168.1.100
Facts:
- Client can ping router and DC
- DC can ping router, cannot ping client
- DC has internet, client does not
To my limited understanding the DNS query from the client should by forwarded by my DC to either the router (192.168.1.1 or google dns 8.8.8.8). It seems to do neither. Is the fact that i'm using a single NIC for all machines (physical and virtual) related to the problems im having?
networking dns windows-domain
asked Feb 16 at 23:01
RockYoClockRockYoClock
1613
add a comment |
0
I've setup a test environment that looks like:
- modem/router connected to physical host
- hyper-v manager running on physical host
- Virtual Switch connected to external network
- Two VMs (DC + client) connected to virtual switch
The DC has the following static config:
- IP: 192.168.1.100
- Subn: 255.255.255.0
- Gateway: 192.168.1.1
- DNS 127.0.0.1
- External DNS 8.8.8.8 added to 'Forwarders' within DNS Management.
Client config:
- IP: 192.168.1.101
- Subn: 255.255.255.0
- Gateway: 192.168.1.100
- DNS: 192.168.1.100
Facts:
- Client can ping router and DC
- DC can ping router, cannot ping client
- DC has internet, client does not
To my limited understanding the DNS query from the client should by forwarded by my DC to either the router (192.168.1.1 or google dns 8.8.8.8). It seems to do neither. Is the fact that i'm using a single NIC for all machines (physical and virtual) related to the problems im having?
networking dns windows-domain
asked Feb 16 at 23:01
RockYoClockRockYoClock
1613
The gateway on the client should, in normal situations, be the same as on the DC. Both DC and client are in the same subnet. If the modem/router is 192.168.1.1 then use that as gateway from both machines. After that the first thing to test is: is there internet connectivity from the DC. Can you resolve DNS queries from the DC? The installation being virtual and sharing hardware should not be an issue. In this setup the client should use DC for DNS queries. The DC get's the info asked from it's cache or queries upstream (8.8.8.8) to get the info requested
– Gert Jan Kraaijeveld
Feb 17 at 15:52
Setting the client gw to same address as DC didn't work at first which made me doubt. Apparantly the VPN on my physical host messed up NAT. Thanks for sending me in the right direction.
– RockYoClock
Feb 20 at 18:38
add a comment |
0
0
0
I've setup a test environment that looks like:
- modem/router connected to physical host
- hyper-v manager running on physical host
- Virtual Switch connected to external network
- Two VMs (DC + client) connected to virtual switch
The DC has the following static config:
- IP: 192.168.1.100
- Subn: 255.255.255.0
- Gateway: 192.168.1.1
- DNS 127.0.0.1
- External DNS 8.8.8.8 added to 'Forwarders' within DNS Management.
Client config:
- IP: 192.168.1.101
- Subn: 255.255.255.0
- Gateway: 192.168.1.100
- DNS: 192.168.1.100
Facts:
- Client can ping router and DC
- DC can ping router, cannot ping client
- DC has internet, client does not
To my limited understanding the DNS query from the client should by forwarded by my DC to either the router (192.168.1.1 or google dns 8.8.8.8). It seems to do neither. Is the fact that i'm using a single NIC for all machines (physical and virtual) related to the problems im having?
networking dns windows-domain
asked Feb 16 at 23:01
RockYoClockRockYoClock
1613
I've setup a test environment that looks like:
- modem/router connected to physical host
- hyper-v manager running on physical host
- Virtual Switch connected to external network
- Two VMs (DC + client) connected to virtual switch
The DC has the following static config:
- IP: 192.168.1.100
- Subn: 255.255.255.0
- Gateway: 192.168.1.1
- DNS 127.0.0.1
- External DNS 8.8.8.8 added to 'Forwarders' within DNS Management.
Client config:
- IP: 192.168.1.101
- Subn: 255.255.255.0
- Gateway: 192.168.1.100
- DNS: 192.168.1.100
Facts:
- Client can ping router and DC
- DC can ping router, cannot ping client
- DC has internet, client does not
To my limited understanding the DNS query from the client should by forwarded by my DC to either the router (192.168.1.1 or google dns 8.8.8.8). It seems to do neither. Is the fact that i'm using a single NIC for all machines (physical and virtual) related to the problems im having?
networking dns windows-domain
networking dns windows-domain
asked Feb 16 at 23:01
RockYoClockRockYoClock
1613
asked Feb 16 at 23:01
RockYoClockRockYoClock
1613
asked Feb 16 at 23:01
RockYoClockRockYoClock
1613
asked Feb 16 at 23:01
RockYoClockRockYoClock
1613
asked Feb 16 at 23:01
RockYoClockRockYoClock
1613
1613
The gateway on the client should, in normal situations, be the same as on the DC. Both DC and client are in the same subnet. If the modem/router is 192.168.1.1 then use that as gateway from both machines. After that the first thing to test is: is there internet connectivity from the DC. Can you resolve DNS queries from the DC? The installation being virtual and sharing hardware should not be an issue. In this setup the client should use DC for DNS queries. The DC get's the info asked from it's cache or queries upstream (8.8.8.8) to get the info requested
– Gert Jan Kraaijeveld
Feb 17 at 15:52
Setting the client gw to same address as DC didn't work at first which made me doubt. Apparantly the VPN on my physical host messed up NAT. Thanks for sending me in the right direction.
– RockYoClock
Feb 20 at 18:38
add a comment |
The gateway on the client should, in normal situations, be the same as on the DC. Both DC and client are in the same subnet. If the modem/router is 192.168.1.1 then use that as gateway from both machines. After that the first thing to test is: is there internet connectivity from the DC. Can you resolve DNS queries from the DC? The installation being virtual and sharing hardware should not be an issue. In this setup the client should use DC for DNS queries. The DC get's the info asked from it's cache or queries upstream (8.8.8.8) to get the info requested
– Gert Jan Kraaijeveld
Feb 17 at 15:52
Setting the client gw to same address as DC didn't work at first which made me doubt. Apparantly the VPN on my physical host messed up NAT. Thanks for sending me in the right direction.
– RockYoClock
Feb 20 at 18:38
The gateway on the client should, in normal situations, be the same as on the DC. Both DC and client are in the same subnet. If the modem/router is 192.168.1.1 then use that as gateway from both machines. After that the first thing to test is: is there internet connectivity from the DC. Can you resolve DNS queries from the DC? The installation being virtual and sharing hardware should not be an issue. In this setup the client should use DC for DNS queries. The DC get's the info asked from it's cache or queries upstream (8.8.8.8) to get the info requested
– Gert Jan Kraaijeveld
Feb 17 at 15:52
The gateway on the client should, in normal situations, be the same as on the DC. Both DC and client are in the same subnet. If the modem/router is 192.168.1.1 then use that as gateway from both machines. After that the first thing to test is: is there internet connectivity from the DC. Can you resolve DNS queries from the DC? The installation being virtual and sharing hardware should not be an issue. In this setup the client should use DC for DNS queries. The DC get's the info asked from it's cache or queries upstream (8.8.8.8) to get the info requested
– Gert Jan Kraaijeveld
Feb 17 at 15:52
Setting the client gw to same address as DC didn't work at first which made me doubt. Apparantly the VPN on my physical host messed up NAT. Thanks for sending me in the right direction.
– RockYoClock
Feb 20 at 18:38
Setting the client gw to same address as DC didn't work at first which made me doubt. Apparantly the VPN on my physical host messed up NAT. Thanks for sending me in the right direction.
– RockYoClock
Feb 20 at 18:38
add a comment |
0
active
oldest
votes
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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
});
}
});
draft saved
draft discarded
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%2fsuperuser.com%2fquestions%2f1406595%2fdomaincontroller-not-forwarding-dns-requests%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
draft saved
draft discarded
Thanks for contributing an answer to Super User!
- 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.
draft saved
draft discarded
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%2fsuperuser.com%2fquestions%2f1406595%2fdomaincontroller-not-forwarding-dns-requests%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
The gateway on the client should, in normal situations, be the same as on the DC. Both DC and client are in the same subnet. If the modem/router is 192.168.1.1 then use that as gateway from both machines. After that the first thing to test is: is there internet connectivity from the DC. Can you resolve DNS queries from the DC? The installation being virtual and sharing hardware should not be an issue. In this setup the client should use DC for DNS queries. The DC get's the info asked from it's cache or queries upstream (8.8.8.8) to get the info requested
– Gert Jan Kraaijeveld
Feb 17 at 15:52
Setting the client gw to same address as DC didn't work at first which made me doubt. Apparantly the VPN on my physical host messed up NAT. Thanks for sending me in the right direction.
– RockYoClock
Feb 20 at 18:38