Problems with DNS and IPv6 on Server 2012 and 2016DNS CNAME Record windows 2003 R2 server by IP addressMS DNS lookup issueIPv6 on Server 2008R2 kills DNS resolution? Internet slowdowns?DNS lookup takes 10 plus secondsWindows Server 2012 DNS forwardingBind Server issue: Can not nslookup from client when DNS Master is down, but still can connect to InternetDecisions about DNS on IPv6Server 2016, DNS only responds when requested over private IP AddressCannot add a domain controller to an existing 2012 R2 domainDNS server cannot resolve addresses itself
What are the differences between credential stuffing and password spraying?
Where can I go to avoid planes overhead?
If Earth is tilted, why is Polaris always above the same spot?
Number of seconds in 6 weeks
For a benzene shown in a skeletal structure, what does a substituent to the center of the ring mean?
Airbnb - host wants to reduce rooms, can we get refund?
How did Arya get her dagger back from Sansa?
What do you call the "hold on" music that plays when you wait on the phone?
Why was the battle set up *outside* Winterfell?
What was the state of the German rail system in 1944?
Can the 歳 counter be used for architecture, furniture etc to tell its age?
Point of the the Dothraki's attack in GoT S8E3?
Does a wine bottle stopper require tevillah?
Is it cheaper to drop cargo than to land it?
Enumerate Derangements
Would "lab meat" be able to feed a much larger global population
Can Ghost kill White Walkers or Wights?
Do I really need diodes to receive MIDI?
How to improve/restore vintage Peugeot bike, or is it even worth it?
Virus Detected - Please execute anti-virus code
My ID is expired, can I fly to the Bahamas with my passport?
SFDX Can query Package Installation Status, can we?
How can I close a gap between my fence and my neighbor's that's on his side of the property line?
Help to understand a simple example of clist in expl3
Problems with DNS and IPv6 on Server 2012 and 2016
DNS CNAME Record windows 2003 R2 server by IP addressMS DNS lookup issueIPv6 on Server 2008R2 kills DNS resolution? Internet slowdowns?DNS lookup takes 10 plus secondsWindows Server 2012 DNS forwardingBind Server issue: Can not nslookup from client when DNS Master is down, but still can connect to InternetDecisions about DNS on IPv6Server 2016, DNS only responds when requested over private IP AddressCannot add a domain controller to an existing 2012 R2 domainDNS server cannot resolve addresses itself
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I manage hundreds of servers for many customers. Most are SMB segment, having 1 to 3 servers per customer max.
In past few weeks I get more and more frequent DNS errors on random domain controllers, from 2008R2 to 2016. Simply put, DC does not resolve DNS anymore. This happened on some dozen of servers lately, and I haven't figured out the cause yet.
Weird is, that for example, on same premises, 2 VMs, 2 domain controllers for 2 different companies, each with 15 users. Same ISP, same router, same switch.
1 DC works OK, no problems, while 2nd DC cannot resolve DNS anymore:
On server 1 problem local DNS... but nslookup to 8.8.8.8 works!?:
C:UsersAdministrator>nslookup
Default Server: UnKnown
Address: ::1
> www.google.com
Server: UnKnown
Address: ::1
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
> server 8.8.8.8
Default Server: google-public-dns-a.google.com
Address: 8.8.8.8
> www.google.com
Server: google-public-dns-a.google.com
Address: 8.8.8.8
Non-authoritative answer:
Name: www.google.com
Addresses: 2a00:1450:4001:81c::2004
172.217.16.68
>
On server 2 no problems:
C:UsersAdministrator>nslookup www.google.com
Server: localhost
Address: ::1
Non-authoritative answer:
Name: www.google.com
Addresses: 2a00:1450:4006:802::2004
216.58.206.132
Both are AD DC in single-domain setup, DNS configured with public forwarders, DC DNS points to itself only. IPv4 and IPv6 enabled on servers, but IPv6 is disabled on router. Did not touch any of those servers for past few months.
Did MS change anything?
I do not remember DNS ever before switched to IPv6....why did it switch now? And why it works on one server and not on the other, still they are both the same (actually, same deployment, just configured for 2 different domains).
domain-name-system active-directory ipv6 windows-server-2016 ipv4
asked Jul 25 '18 at 21:48
LabsyLabsy
136
add a comment |
I manage hundreds of servers for many customers. Most are SMB segment, having 1 to 3 servers per customer max.
In past few weeks I get more and more frequent DNS errors on random domain controllers, from 2008R2 to 2016. Simply put, DC does not resolve DNS anymore. This happened on some dozen of servers lately, and I haven't figured out the cause yet.
Weird is, that for example, on same premises, 2 VMs, 2 domain controllers for 2 different companies, each with 15 users. Same ISP, same router, same switch.
1 DC works OK, no problems, while 2nd DC cannot resolve DNS anymore:
On server 1 problem local DNS... but nslookup to 8.8.8.8 works!?:
C:UsersAdministrator>nslookup
Default Server: UnKnown
Address: ::1
> www.google.com
Server: UnKnown
Address: ::1
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
> server 8.8.8.8
Default Server: google-public-dns-a.google.com
Address: 8.8.8.8
> www.google.com
Server: google-public-dns-a.google.com
Address: 8.8.8.8
Non-authoritative answer:
Name: www.google.com
Addresses: 2a00:1450:4001:81c::2004
172.217.16.68
>
On server 2 no problems:
C:UsersAdministrator>nslookup www.google.com
Server: localhost
Address: ::1
Non-authoritative answer:
Name: www.google.com
Addresses: 2a00:1450:4006:802::2004
216.58.206.132
Both are AD DC in single-domain setup, DNS configured with public forwarders, DC DNS points to itself only. IPv4 and IPv6 enabled on servers, but IPv6 is disabled on router. Did not touch any of those servers for past few months.
Did MS change anything?
I do not remember DNS ever before switched to IPv6....why did it switch now? And why it works on one server and not on the other, still they are both the same (actually, same deployment, just configured for 2 different domains).
domain-name-system active-directory ipv6 windows-server-2016 ipv4
asked Jul 25 '18 at 21:48
LabsyLabsy
136
The switch to IPv6 began with Server 2008/Vista. It's not new at all. Since then, localhost has been ::1 and used IPv6 unless the system was explicitly misconfigured by the admin.
– Michael Hampton♦
Jul 25 '18 at 21:50
DC DNS points to itself only- If there are two DC/DNS servers then this configuration is incorrect. Each DC/DNS server should use it's "partner" DC/DNS server for primary DNS, itself for secondary DNS, and 127.0.0.1 for tertiary DNS.
– joeqwerty
Jul 26 '18 at 1:01
@joequerty - both servers are standalone single DC's, each for it's own domain.
– Labsy
Jul 26 '18 at 6:16
add a comment |
I manage hundreds of servers for many customers. Most are SMB segment, having 1 to 3 servers per customer max.
In past few weeks I get more and more frequent DNS errors on random domain controllers, from 2008R2 to 2016. Simply put, DC does not resolve DNS anymore. This happened on some dozen of servers lately, and I haven't figured out the cause yet.
Weird is, that for example, on same premises, 2 VMs, 2 domain controllers for 2 different companies, each with 15 users. Same ISP, same router, same switch.
1 DC works OK, no problems, while 2nd DC cannot resolve DNS anymore:
On server 1 problem local DNS... but nslookup to 8.8.8.8 works!?:
C:UsersAdministrator>nslookup
Default Server: UnKnown
Address: ::1
> www.google.com
Server: UnKnown
Address: ::1
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
> server 8.8.8.8
Default Server: google-public-dns-a.google.com
Address: 8.8.8.8
> www.google.com
Server: google-public-dns-a.google.com
Address: 8.8.8.8
Non-authoritative answer:
Name: www.google.com
Addresses: 2a00:1450:4001:81c::2004
172.217.16.68
>
On server 2 no problems:
C:UsersAdministrator>nslookup www.google.com
Server: localhost
Address: ::1
Non-authoritative answer:
Name: www.google.com
Addresses: 2a00:1450:4006:802::2004
216.58.206.132
Both are AD DC in single-domain setup, DNS configured with public forwarders, DC DNS points to itself only. IPv4 and IPv6 enabled on servers, but IPv6 is disabled on router. Did not touch any of those servers for past few months.
Did MS change anything?
I do not remember DNS ever before switched to IPv6....why did it switch now? And why it works on one server and not on the other, still they are both the same (actually, same deployment, just configured for 2 different domains).
domain-name-system active-directory ipv6 windows-server-2016 ipv4
asked Jul 25 '18 at 21:48
LabsyLabsy
136
I manage hundreds of servers for many customers. Most are SMB segment, having 1 to 3 servers per customer max.
In past few weeks I get more and more frequent DNS errors on random domain controllers, from 2008R2 to 2016. Simply put, DC does not resolve DNS anymore. This happened on some dozen of servers lately, and I haven't figured out the cause yet.
Weird is, that for example, on same premises, 2 VMs, 2 domain controllers for 2 different companies, each with 15 users. Same ISP, same router, same switch.
1 DC works OK, no problems, while 2nd DC cannot resolve DNS anymore:
On server 1 problem local DNS... but nslookup to 8.8.8.8 works!?:
C:UsersAdministrator>nslookup
Default Server: UnKnown
Address: ::1
> www.google.com
Server: UnKnown
Address: ::1
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
> server 8.8.8.8
Default Server: google-public-dns-a.google.com
Address: 8.8.8.8
> www.google.com
Server: google-public-dns-a.google.com
Address: 8.8.8.8
Non-authoritative answer:
Name: www.google.com
Addresses: 2a00:1450:4001:81c::2004
172.217.16.68
>
On server 2 no problems:
C:UsersAdministrator>nslookup www.google.com
Server: localhost
Address: ::1
Non-authoritative answer:
Name: www.google.com
Addresses: 2a00:1450:4006:802::2004
216.58.206.132
Both are AD DC in single-domain setup, DNS configured with public forwarders, DC DNS points to itself only. IPv4 and IPv6 enabled on servers, but IPv6 is disabled on router. Did not touch any of those servers for past few months.
Did MS change anything?
I do not remember DNS ever before switched to IPv6....why did it switch now? And why it works on one server and not on the other, still they are both the same (actually, same deployment, just configured for 2 different domains).
domain-name-system active-directory ipv6 windows-server-2016 ipv4
domain-name-system active-directory ipv6 windows-server-2016 ipv4
asked Jul 25 '18 at 21:48
LabsyLabsy
136
asked Jul 25 '18 at 21:48
LabsyLabsy
136
edited Jul 26 '18 at 6:13
Labsy
asked Jul 25 '18 at 21:48
LabsyLabsy
136
asked Jul 25 '18 at 21:48
LabsyLabsy
136
asked Jul 25 '18 at 21:48
LabsyLabsy
136
136
The switch to IPv6 began with Server 2008/Vista. It's not new at all. Since then, localhost has been ::1 and used IPv6 unless the system was explicitly misconfigured by the admin.
– Michael Hampton♦
Jul 25 '18 at 21:50
DC DNS points to itself only- If there are two DC/DNS servers then this configuration is incorrect. Each DC/DNS server should use it's "partner" DC/DNS server for primary DNS, itself for secondary DNS, and 127.0.0.1 for tertiary DNS.
– joeqwerty
Jul 26 '18 at 1:01
@joequerty - both servers are standalone single DC's, each for it's own domain.
– Labsy
Jul 26 '18 at 6:16
add a comment |
The switch to IPv6 began with Server 2008/Vista. It's not new at all. Since then, localhost has been ::1 and used IPv6 unless the system was explicitly misconfigured by the admin.
– Michael Hampton♦
Jul 25 '18 at 21:50
DC DNS points to itself only- If there are two DC/DNS servers then this configuration is incorrect. Each DC/DNS server should use it's "partner" DC/DNS server for primary DNS, itself for secondary DNS, and 127.0.0.1 for tertiary DNS.
– joeqwerty
Jul 26 '18 at 1:01
@joequerty - both servers are standalone single DC's, each for it's own domain.
– Labsy
Jul 26 '18 at 6:16
The switch to IPv6 began with Server 2008/Vista. It's not new at all. Since then, localhost has been ::1 and used IPv6 unless the system was explicitly misconfigured by the admin.
– Michael Hampton♦
Jul 25 '18 at 21:50
The switch to IPv6 began with Server 2008/Vista. It's not new at all. Since then, localhost has been ::1 and used IPv6 unless the system was explicitly misconfigured by the admin.
– Michael Hampton♦
Jul 25 '18 at 21:50
DC DNS points to itself only - If there are two DC/DNS servers then this configuration is incorrect. Each DC/DNS server should use it's "partner" DC/DNS server for primary DNS, itself for secondary DNS, and 127.0.0.1 for tertiary DNS.– joeqwerty
Jul 26 '18 at 1:01
DC DNS points to itself only - If there are two DC/DNS servers then this configuration is incorrect. Each DC/DNS server should use it's "partner" DC/DNS server for primary DNS, itself for secondary DNS, and 127.0.0.1 for tertiary DNS.– joeqwerty
Jul 26 '18 at 1:01
@joequerty - both servers are standalone single DC's, each for it's own domain.
– Labsy
Jul 26 '18 at 6:16
@joequerty - both servers are standalone single DC's, each for it's own domain.
– Labsy
Jul 26 '18 at 6:16
add a comment |
1 Answer
1
active
oldest
votes
There are two possible reasons for a timeout.
- The request is sent to the wrong address.
- The request doesn't arrive at the DNS server, or the DNS response doesn't get back because of network problem.
Use ipconfig /all to list the DNS servers. If they are different, correct them. If they are the same, use a packet sniffer on the server and on the router to find out what packets are sent.
answered Jul 25 '18 at 22:33
RalfFriedlRalfFriedl
2,4853614
Both servers are on SAME subnet, SAME router, SAME switch. Both use forwarders to 8.8.8.8. If I look at router, the problematic server's DNS requests most of the time do not reach the router from inside out... BUT some (rare) DNS requests from this same server somehow still pass through. For example, trying nslookup www.google.com does not pass, but when I lounch Check for updates, I can see DNS request for MS update service goes through.
– Labsy
Jul 26 '18 at 0:28
EDIT: There are NO lost DNS packets. All DNS requests are passing correctly from local server's IP to 8.8.8.8 and back. They are obviously lost when they arrive back to server.
– Labsy
Jul 26 '18 at 0:42
1
ADDING: manually selecting 8.8.8.8 server with NSLOOKUP works without any problems from problematic server. While using ::1 or localhost or local server's IP as DNS does not.
– Labsy
Jul 26 '18 at 0:49
I understood that the configuration is the SAME, but if it stopped working, there must be some reason. You should add thatnslookup www.google.com 8.8.8.8works to the question, not everybody reads all the comments. It seems there is something wrong with the local resolver. Check the services whether it is running and the event log for possible problems.
– RalfFriedl
Jul 26 '18 at 5:20
Thank you, I edited OP question with nslookup details. I've checked DNS and DNS server logs, and there's no errors or warnings. All needed services are up & running. Monit is configured the same for both servers, and if I compare services one-by-one, on both servers all is the same. I also cleared DNS cache, rebooted multiple times, flushed cache, checked hosts file....hmmm, running out of ideas slowly.
– Labsy
Jul 26 '18 at 6:19
|
show 1 more comment
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
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%2fserverfault.com%2fquestions%2f923550%2fproblems-with-dns-and-ipv6-on-server-2012-and-2016%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
There are two possible reasons for a timeout.
- The request is sent to the wrong address.
- The request doesn't arrive at the DNS server, or the DNS response doesn't get back because of network problem.
Use ipconfig /all to list the DNS servers. If they are different, correct them. If they are the same, use a packet sniffer on the server and on the router to find out what packets are sent.
answered Jul 25 '18 at 22:33
RalfFriedlRalfFriedl
2,4853614
Both servers are on SAME subnet, SAME router, SAME switch. Both use forwarders to 8.8.8.8. If I look at router, the problematic server's DNS requests most of the time do not reach the router from inside out... BUT some (rare) DNS requests from this same server somehow still pass through. For example, trying nslookup www.google.com does not pass, but when I lounch Check for updates, I can see DNS request for MS update service goes through.
– Labsy
Jul 26 '18 at 0:28
EDIT: There are NO lost DNS packets. All DNS requests are passing correctly from local server's IP to 8.8.8.8 and back. They are obviously lost when they arrive back to server.
– Labsy
Jul 26 '18 at 0:42
1
ADDING: manually selecting 8.8.8.8 server with NSLOOKUP works without any problems from problematic server. While using ::1 or localhost or local server's IP as DNS does not.
– Labsy
Jul 26 '18 at 0:49
I understood that the configuration is the SAME, but if it stopped working, there must be some reason. You should add thatnslookup www.google.com 8.8.8.8works to the question, not everybody reads all the comments. It seems there is something wrong with the local resolver. Check the services whether it is running and the event log for possible problems.
– RalfFriedl
Jul 26 '18 at 5:20
Thank you, I edited OP question with nslookup details. I've checked DNS and DNS server logs, and there's no errors or warnings. All needed services are up & running. Monit is configured the same for both servers, and if I compare services one-by-one, on both servers all is the same. I also cleared DNS cache, rebooted multiple times, flushed cache, checked hosts file....hmmm, running out of ideas slowly.
– Labsy
Jul 26 '18 at 6:19
|
show 1 more comment
There are two possible reasons for a timeout.
- The request is sent to the wrong address.
- The request doesn't arrive at the DNS server, or the DNS response doesn't get back because of network problem.
Use ipconfig /all to list the DNS servers. If they are different, correct them. If they are the same, use a packet sniffer on the server and on the router to find out what packets are sent.
answered Jul 25 '18 at 22:33
RalfFriedlRalfFriedl
2,4853614
Both servers are on SAME subnet, SAME router, SAME switch. Both use forwarders to 8.8.8.8. If I look at router, the problematic server's DNS requests most of the time do not reach the router from inside out... BUT some (rare) DNS requests from this same server somehow still pass through. For example, trying nslookup www.google.com does not pass, but when I lounch Check for updates, I can see DNS request for MS update service goes through.
– Labsy
Jul 26 '18 at 0:28
EDIT: There are NO lost DNS packets. All DNS requests are passing correctly from local server's IP to 8.8.8.8 and back. They are obviously lost when they arrive back to server.
– Labsy
Jul 26 '18 at 0:42
1
ADDING: manually selecting 8.8.8.8 server with NSLOOKUP works without any problems from problematic server. While using ::1 or localhost or local server's IP as DNS does not.
– Labsy
Jul 26 '18 at 0:49
I understood that the configuration is the SAME, but if it stopped working, there must be some reason. You should add thatnslookup www.google.com 8.8.8.8works to the question, not everybody reads all the comments. It seems there is something wrong with the local resolver. Check the services whether it is running and the event log for possible problems.
– RalfFriedl
Jul 26 '18 at 5:20
Thank you, I edited OP question with nslookup details. I've checked DNS and DNS server logs, and there's no errors or warnings. All needed services are up & running. Monit is configured the same for both servers, and if I compare services one-by-one, on both servers all is the same. I also cleared DNS cache, rebooted multiple times, flushed cache, checked hosts file....hmmm, running out of ideas slowly.
– Labsy
Jul 26 '18 at 6:19
|
show 1 more comment
There are two possible reasons for a timeout.
- The request is sent to the wrong address.
- The request doesn't arrive at the DNS server, or the DNS response doesn't get back because of network problem.
Use ipconfig /all to list the DNS servers. If they are different, correct them. If they are the same, use a packet sniffer on the server and on the router to find out what packets are sent.
answered Jul 25 '18 at 22:33
RalfFriedlRalfFriedl
2,4853614
There are two possible reasons for a timeout.
- The request is sent to the wrong address.
- The request doesn't arrive at the DNS server, or the DNS response doesn't get back because of network problem.
Use ipconfig /all to list the DNS servers. If they are different, correct them. If they are the same, use a packet sniffer on the server and on the router to find out what packets are sent.
answered Jul 25 '18 at 22:33
RalfFriedlRalfFriedl
2,4853614
answered Jul 25 '18 at 22:33
RalfFriedlRalfFriedl
2,4853614
answered Jul 25 '18 at 22:33
RalfFriedlRalfFriedl
2,4853614
answered Jul 25 '18 at 22:33
RalfFriedlRalfFriedl
2,4853614
2,4853614
Both servers are on SAME subnet, SAME router, SAME switch. Both use forwarders to 8.8.8.8. If I look at router, the problematic server's DNS requests most of the time do not reach the router from inside out... BUT some (rare) DNS requests from this same server somehow still pass through. For example, trying nslookup www.google.com does not pass, but when I lounch Check for updates, I can see DNS request for MS update service goes through.
– Labsy
Jul 26 '18 at 0:28
EDIT: There are NO lost DNS packets. All DNS requests are passing correctly from local server's IP to 8.8.8.8 and back. They are obviously lost when they arrive back to server.
– Labsy
Jul 26 '18 at 0:42
1
ADDING: manually selecting 8.8.8.8 server with NSLOOKUP works without any problems from problematic server. While using ::1 or localhost or local server's IP as DNS does not.
– Labsy
Jul 26 '18 at 0:49
I understood that the configuration is the SAME, but if it stopped working, there must be some reason. You should add thatnslookup www.google.com 8.8.8.8works to the question, not everybody reads all the comments. It seems there is something wrong with the local resolver. Check the services whether it is running and the event log for possible problems.
– RalfFriedl
Jul 26 '18 at 5:20
Thank you, I edited OP question with nslookup details. I've checked DNS and DNS server logs, and there's no errors or warnings. All needed services are up & running. Monit is configured the same for both servers, and if I compare services one-by-one, on both servers all is the same. I also cleared DNS cache, rebooted multiple times, flushed cache, checked hosts file....hmmm, running out of ideas slowly.
– Labsy
Jul 26 '18 at 6:19
|
show 1 more comment
Both servers are on SAME subnet, SAME router, SAME switch. Both use forwarders to 8.8.8.8. If I look at router, the problematic server's DNS requests most of the time do not reach the router from inside out... BUT some (rare) DNS requests from this same server somehow still pass through. For example, trying nslookup www.google.com does not pass, but when I lounch Check for updates, I can see DNS request for MS update service goes through.
– Labsy
Jul 26 '18 at 0:28
EDIT: There are NO lost DNS packets. All DNS requests are passing correctly from local server's IP to 8.8.8.8 and back. They are obviously lost when they arrive back to server.
– Labsy
Jul 26 '18 at 0:42
1
ADDING: manually selecting 8.8.8.8 server with NSLOOKUP works without any problems from problematic server. While using ::1 or localhost or local server's IP as DNS does not.
– Labsy
Jul 26 '18 at 0:49
I understood that the configuration is the SAME, but if it stopped working, there must be some reason. You should add thatnslookup www.google.com 8.8.8.8works to the question, not everybody reads all the comments. It seems there is something wrong with the local resolver. Check the services whether it is running and the event log for possible problems.
– RalfFriedl
Jul 26 '18 at 5:20
Thank you, I edited OP question with nslookup details. I've checked DNS and DNS server logs, and there's no errors or warnings. All needed services are up & running. Monit is configured the same for both servers, and if I compare services one-by-one, on both servers all is the same. I also cleared DNS cache, rebooted multiple times, flushed cache, checked hosts file....hmmm, running out of ideas slowly.
– Labsy
Jul 26 '18 at 6:19
Both servers are on SAME subnet, SAME router, SAME switch. Both use forwarders to 8.8.8.8. If I look at router, the problematic server's DNS requests most of the time do not reach the router from inside out... BUT some (rare) DNS requests from this same server somehow still pass through. For example, trying nslookup www.google.com does not pass, but when I lounch Check for updates, I can see DNS request for MS update service goes through.
– Labsy
Jul 26 '18 at 0:28
Both servers are on SAME subnet, SAME router, SAME switch. Both use forwarders to 8.8.8.8. If I look at router, the problematic server's DNS requests most of the time do not reach the router from inside out... BUT some (rare) DNS requests from this same server somehow still pass through. For example, trying nslookup www.google.com does not pass, but when I lounch Check for updates, I can see DNS request for MS update service goes through.
– Labsy
Jul 26 '18 at 0:28
EDIT: There are NO lost DNS packets. All DNS requests are passing correctly from local server's IP to 8.8.8.8 and back. They are obviously lost when they arrive back to server.
– Labsy
Jul 26 '18 at 0:42
EDIT: There are NO lost DNS packets. All DNS requests are passing correctly from local server's IP to 8.8.8.8 and back. They are obviously lost when they arrive back to server.
– Labsy
Jul 26 '18 at 0:42
1
1
ADDING: manually selecting 8.8.8.8 server with NSLOOKUP works without any problems from problematic server. While using ::1 or localhost or local server's IP as DNS does not.
– Labsy
Jul 26 '18 at 0:49
ADDING: manually selecting 8.8.8.8 server with NSLOOKUP works without any problems from problematic server. While using ::1 or localhost or local server's IP as DNS does not.
– Labsy
Jul 26 '18 at 0:49
I understood that the configuration is the SAME, but if it stopped working, there must be some reason. You should add that
nslookup www.google.com 8.8.8.8 works to the question, not everybody reads all the comments. It seems there is something wrong with the local resolver. Check the services whether it is running and the event log for possible problems.– RalfFriedl
Jul 26 '18 at 5:20
I understood that the configuration is the SAME, but if it stopped working, there must be some reason. You should add that
nslookup www.google.com 8.8.8.8 works to the question, not everybody reads all the comments. It seems there is something wrong with the local resolver. Check the services whether it is running and the event log for possible problems.– RalfFriedl
Jul 26 '18 at 5:20
Thank you, I edited OP question with nslookup details. I've checked DNS and DNS server logs, and there's no errors or warnings. All needed services are up & running. Monit is configured the same for both servers, and if I compare services one-by-one, on both servers all is the same. I also cleared DNS cache, rebooted multiple times, flushed cache, checked hosts file....hmmm, running out of ideas slowly.
– Labsy
Jul 26 '18 at 6:19
Thank you, I edited OP question with nslookup details. I've checked DNS and DNS server logs, and there's no errors or warnings. All needed services are up & running. Monit is configured the same for both servers, and if I compare services one-by-one, on both servers all is the same. I also cleared DNS cache, rebooted multiple times, flushed cache, checked hosts file....hmmm, running out of ideas slowly.
– Labsy
Jul 26 '18 at 6:19
|
show 1 more comment
Thanks for contributing an answer to Server Fault!
- 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%2fserverfault.com%2fquestions%2f923550%2fproblems-with-dns-and-ipv6-on-server-2012-and-2016%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 switch to IPv6 began with Server 2008/Vista. It's not new at all. Since then, localhost has been ::1 and used IPv6 unless the system was explicitly misconfigured by the admin.
– Michael Hampton♦
Jul 25 '18 at 21:50
DC DNS points to itself only- If there are two DC/DNS servers then this configuration is incorrect. Each DC/DNS server should use it's "partner" DC/DNS server for primary DNS, itself for secondary DNS, and 127.0.0.1 for tertiary DNS.– joeqwerty
Jul 26 '18 at 1:01
@joequerty - both servers are standalone single DC's, each for it's own domain.
– Labsy
Jul 26 '18 at 6:16