Member_2_6368962
asked on
DNS
Hello everybody,
Recently I made a migration of my DC (AD, DHCP and DNS) from windows 2008 server r2 to windows 2008 server r2 a new server (new equipment)
Apparently everything was working good, but I started to see 2 errors during my navigation.
The first error appeared when I typed an address (first time) like www.apple.com , sometimes it does not find the server and sometimes it finds but it shows the page as simple HTML (as you can see in my attached files). If I press (f5) to reload the page, in both cases it works and the right page appears.
I would like to know if there are some solutions, or what configuration I should check, what test I should make..
Thank you for all help.
Best Regards
Renato Marcandier
erro1.jpg
erro2.jpg
erro3.jpg
erro4.jpg
Recently I made a migration of my DC (AD, DHCP and DNS) from windows 2008 server r2 to windows 2008 server r2 a new server (new equipment)
Apparently everything was working good, but I started to see 2 errors during my navigation.
The first error appeared when I typed an address (first time) like www.apple.com , sometimes it does not find the server and sometimes it finds but it shows the page as simple HTML (as you can see in my attached files). If I press (f5) to reload the page, in both cases it works and the right page appears.
I would like to know if there are some solutions, or what configuration I should check, what test I should make..
Thank you for all help.
Best Regards
Renato Marcandier
erro1.jpg
erro2.jpg
erro3.jpg
erro4.jpg
ASKER
Hi susquperf
Thank you for your answer.
I am attaching the files for you to take a look.
Yes, not just me, all my network is getting problems to browsing. I tried with firefox and chrome.
Let me know if you see something strange pls.
dcdiagV.txt
ipconfigALL.txt
ping.jpg
Thank you for your answer.
I am attaching the files for you to take a look.
Yes, not just me, all my network is getting problems to browsing. I tried with firefox and chrome.
Let me know if you see something strange pls.
dcdiagV.txt
ipconfigALL.txt
ping.jpg
Was the old box a different ip? Does your firewall have rules blocking DNS traffic?
ASKER
Hi aarontomosky,
first box is my DNS server ip (192.168.0.3) and the second box the google.com
I will check my firewall if has some restrictions.
first box is my DNS server ip (192.168.0.3) and the second box the google.com
I will check my firewall if has some restrictions.
Check the switch or may be reset the switch and see if that helps. The packets are dropping it looks like in the Ping.jpg
Check the router settings if you have configured and point to the correct internal IP address.
dcdiag /test:dns >> results.txt ??? Can I get this file? Because I don't see any issues with the Dcdiag.txt results that you had sent to us. Run the port query on these ports from any of the public IPs and see if the important ports are opened on the router and the firewall.
DNS- 53
HTTP - 80
HTTPS - 443
SMTP - 25
Let us know your result.
~SG~
Check the router settings if you have configured and point to the correct internal IP address.
dcdiag /test:dns >> results.txt ??? Can I get this file? Because I don't see any issues with the Dcdiag.txt results that you had sent to us. Run the port query on these ports from any of the public IPs and see if the important ports are opened on the router and the firewall.
DNS- 53
HTTP - 80
HTTPS - 443
SMTP - 25
Let us know your result.
~SG~
ASKER
Hello susquperf
Thank you for your help.
Tomorrow I will reset the switch, I am working remotely at the moment.
I am attaching the file that you are asking me.
I will run the portqry from my machine and see the results.
results.txt
Thank you for your help.
Tomorrow I will reset the switch, I am working remotely at the moment.
I am attaching the file that you are asking me.
I will run the portqry from my machine and see the results.
results.txt
ASKER
susguperf
On windows 7, do you know how to run portqry? I found just for: Windows 2000, Windows Server 2003, Windows XP
On windows 7, do you know how to run portqry? I found just for: Windows 2000, Windows Server 2003, Windows XP
You can download the tool from here
http://www.microsoft.com/download/en/details.aspx?id=24009
The UI version will give options to enter the Source IP address with the port range you can define the ports manually.
http://www.microsoft.com/download/en/details.aspx?id=24009
The UI version will give options to enter the Source IP address with the port range you can define the ports manually.
ASKER
Hello susquperf,
I performed this commands: (192.168.0.3 is my DNS Server)
C:\PortQryV2>portqry -n 192.168.0.3 -e 53
Querying target system called:
192.168.0.3
Attempting to resolve IP address to a name...
IP address resolved to thestove.multuk.internal
querying...
TCP port 53 (domain service): LISTENING
C:\PortQryV2>portqry -n 192.168.0.3 -e 80
Querying target system called:
192.168.0.3
Attempting to resolve IP address to a name...
IP address resolved to thestove.multuk.internal
querying...
Error opening socket: 10051
Network unreachable.
C:\PortQryV2>portqry -n 192.168.0.3 -e 443
Querying target system called:
192.168.0.3
Attempting to resolve IP address to a name...
IP address resolved to thestove.multuk.internal
querying...
Error opening socket: 10051
Network unreachable.
C:\PortQryV2>portqry -n 192.168.0.3 -e 25
Querying target system called:
192.168.0.3
Attempting to resolve IP address to a name...
IP address resolved to thestove.multuk.internal
querying...
Error opening socket: 10051
Network unreachable.
I performed this commands: (192.168.0.3 is my DNS Server)
C:\PortQryV2>portqry -n 192.168.0.3 -e 53
Querying target system called:
192.168.0.3
Attempting to resolve IP address to a name...
IP address resolved to thestove.multuk.internal
querying...
TCP port 53 (domain service): LISTENING
C:\PortQryV2>portqry -n 192.168.0.3 -e 80
Querying target system called:
192.168.0.3
Attempting to resolve IP address to a name...
IP address resolved to thestove.multuk.internal
querying...
Error opening socket: 10051
Network unreachable.
C:\PortQryV2>portqry -n 192.168.0.3 -e 443
Querying target system called:
192.168.0.3
Attempting to resolve IP address to a name...
IP address resolved to thestove.multuk.internal
querying...
Error opening socket: 10051
Network unreachable.
C:\PortQryV2>portqry -n 192.168.0.3 -e 25
Querying target system called:
192.168.0.3
Attempting to resolve IP address to a name...
IP address resolved to thestove.multuk.internal
querying...
Error opening socket: 10051
Network unreachable.
ASKER
ASKER
Hello susquperf,
I think the error is exactly here right? ==>>
"10051 socket error"
I think the error is exactly here right? ==>>
"10051 socket error"
You should have tried the gateway IP address - 192.168.0.1 or with the Public IP. Go to www.whatismyip.com and copy the IP address, paste that in the PortqryUI and perform the same steps.
You are tracing the server ports and we are trying to query the ports on the router or on the firewall. Tracing the ports using the Public IP is much more promising job.
Please return with your results ASAP..
~SG~
You are tracing the server ports and we are trying to query the ports on the router or on the firewall. Tracing the ports using the Public IP is much more promising job.
Please return with your results ASAP..
~SG~
ASKER
hello susguperf
Thank you very much.
I am attaching the print screen for you.
I am getting the same error (10051)
xxx2.jpg
Thank you very much.
I am attaching the print screen for you.
I am getting the same error (10051)
xxx2.jpg
ASKER
Do me a favor, please send dcdiag /test:dns logs in your next comment...
This event only states that to update the DNS.exe on the server. I am not sure what is the SP level you are running on. I would still say to check the DNS and check the forwarders list and beside here are my portqryUI results.
Port 53
Querying target system called:
188.220.33.91
Attempting to resolve IP address to a name...
IP address resolved to 188-220-33-91.zone11.bethe
querying...
TCP port 53 (domain service): FILTERED
UDP port 53 (domain service): LISTENING or FILTERED
Port 80
Querying target system called:
188.220.33.91
Attempting to resolve IP address to a name...
IP address resolved to 188-220-33-91.zone11.bethe
querying...
TCP port 80 (http service): LISTENING
Port 443
Querying target system called:
188.220.33.91
Attempting to resolve IP address to a name...
IP address resolved to 188-220-33-91.zone11.bethe
querying...
TCP port 443 (https service): LISTENING
Port 25
Starting portqry.exe -n 188.220.33.91 -e 25 -p TCP ...
Querying target system called:
188.220.33.91
Attempting to resolve IP address to a name...
IP address resolved to 188-220-33-91.zone11.bethe
querying...
TCP port 25 (smtp service): LISTENING
Can you send us the current status or send us an update as to what is going on at this point?
Good Luck..!!
~SG~
Port 53
Querying target system called:
188.220.33.91
Attempting to resolve IP address to a name...
IP address resolved to 188-220-33-91.zone11.bethe
querying...
TCP port 53 (domain service): FILTERED
UDP port 53 (domain service): LISTENING or FILTERED
Port 80
Querying target system called:
188.220.33.91
Attempting to resolve IP address to a name...
IP address resolved to 188-220-33-91.zone11.bethe
querying...
TCP port 80 (http service): LISTENING
Port 443
Querying target system called:
188.220.33.91
Attempting to resolve IP address to a name...
IP address resolved to 188-220-33-91.zone11.bethe
querying...
TCP port 443 (https service): LISTENING
Port 25
Starting portqry.exe -n 188.220.33.91 -e 25 -p TCP ...
Querying target system called:
188.220.33.91
Attempting to resolve IP address to a name...
IP address resolved to 188-220-33-91.zone11.bethe
querying...
TCP port 25 (smtp service): LISTENING
Can you send us the current status or send us an update as to what is going on at this point?
Good Luck..!!
~SG~
ASKER
Hello susguperf
Thank you for your contact.
Today was very busy day resolving another problems..
Tomorrow I will focus in this one again. I will send for you the results of logs.
See you soon
Thank you for your contact.
Today was very busy day resolving another problems..
Tomorrow I will focus in this one again. I will send for you the results of logs.
See you soon
Sure thing.. we'll wait..
ASKER
Hello susquperf,
When I try to run this portquery like you, I am getting this error:
Error opening socket: 10051
I dont know what I need to do to resolve this problem.
PortQuery.jpg
5501.jpg
When I try to run this portquery like you, I am getting this error:
Error opening socket: 10051
I dont know what I need to do to resolve this problem.
PortQuery.jpg
5501.jpg
ASKER
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = THESTOVE
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\TH
Starting test: Connectivity
......................... THESTOVE passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\TH
Starting test: DNS
DNS Tests are running and not hung. Please wait a few minutes...
......................... THESTOVE passed test DNS
Running partition tests on : ForestDnsZones
Running partition tests on : DomainDnsZones
Running partition tests on : Schema
Running partition tests on : Configuration
Running partition tests on : MULTUK
Running enterprise tests on : MULTUK.INTERNAL
Starting test: DNS
Test results for domain controllers:
DC: THESTOVE.MULTUK.INTERNAL
Domain: MULTUK.INTERNAL
TEST: Delegations (Del)
Error: DNS server: thefridge.multuk.internal.
[Broken delegated domain _msdcs.MULTUK.INTERNAL.]
TEST: Dynamic update (Dyn)
Warning: Failed to delete the test record dcdiag-test-record in zone MULTUK.INTERNAL
Summary of test results for DNS servers used by the above domain
controllers:
DNS server: 192.168.0.4 (thefridge.multuk.internal
1 test failure on this DNS server
DNS server: 2001:500:1::803f:235 (h.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.
DNS server: 2001:500:2d::d (d.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.
DNS server: 2001:500:2f::f (f.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.
DNS server: 2001:500:3::42 (l.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.
DNS server: 2001:503:ba3e::2:30 (a.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.
DNS server: 2001:503:c27::2:30 (j.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.
DNS server: 2001:7fd::1 (k.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.
DNS server: 2001:7fe::53 (i.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.
DNS server: 2001:dc3::35 (m.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
__________________________
Domain: MULTUK.INTERNAL
THESTOVE PASS PASS PASS FAIL WARN PASS n/a
......................... MULTUK.INTERNAL failed test DNS
ASKER
Here is the problem!!
TEST: Delegations (Del)
Error: DNS server: thefridge.multuk.internal.
[Broken delegated domain _msdcs.MULTUK.INTERNAL.]
TEST: Dynamic update (Dyn)
Warning: Failed to delete the test record dcdiag-test-record in zone MULTUK.INTERNAL
Summary of test results for DNS servers used by the above domain
controllers:
DNS server: 192.168.0.4 (thefridge.multuk.internal
1 test failure on this DNS server
This 192.168.0.4 is not my DNS Server anymore... its just a simple File Server
How can I clean it?
TEST: Delegations (Del)
Error: DNS server: thefridge.multuk.internal.
[Broken delegated domain _msdcs.MULTUK.INTERNAL.]
TEST: Dynamic update (Dyn)
Warning: Failed to delete the test record dcdiag-test-record in zone MULTUK.INTERNAL
Summary of test results for DNS servers used by the above domain
controllers:
DNS server: 192.168.0.4 (thefridge.multuk.internal
1 test failure on this DNS server
This 192.168.0.4 is not my DNS Server anymore... its just a simple File Server
How can I clean it?
What is the version of support tools you are using?
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=15326
Can you verify if you are able to ping the DNS server with the FQDN?
DCDIAG /TEST:DNS /V /S:<DCNAME> /F:<filename.log>
The "/s:" switch runs the DNS test against a specified domain controller -->> Run this
Looks like we have bad entry for the NS record for "192.168.0.4" Remove all the entries and restart the DNS, netlogon services after flushing the DNS and re-registering it.
ipconfig /flushdns & net stop dns & net stop netlogon & net start dns & net start netlogon & ipconfig /registerdns
Rest, I am looking into this..
Thank You..!!
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=15326
Can you verify if you are able to ping the DNS server with the FQDN?
DCDIAG /TEST:DNS /V /S:<DCNAME> /F:<filename.log>
The "/s:" switch runs the DNS test against a specified domain controller -->> Run this
Looks like we have bad entry for the NS record for "192.168.0.4" Remove all the entries and restart the DNS, netlogon services after flushing the DNS and re-registering it.
ipconfig /flushdns & net stop dns & net stop netlogon & net start dns & net start netlogon & ipconfig /registerdns
Rest, I am looking into this..
Thank You..!!
ASKER
Hi susqquperf,
Thank you for all your help, but I am getting a lot of problems because of it.
Do you think I should uninstall DNS service from my windows 2008 server r2, and install it again?! Or install a DNS Server in a Linux server.... it shouldn´t give me too many problems...
Thank you for all your help, but I am getting a lot of problems because of it.
Do you think I should uninstall DNS service from my windows 2008 server r2, and install it again?! Or install a DNS Server in a Linux server.... it shouldn´t give me too many problems...
ASKER
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
That's little unfortunate.. Anyways, you made it working. KUDOS..!!
All the best..!!
All the best..!!
ASKER
After a few days making a lot of tests in my DNS Server to try to resolve this problem I found the solution.
During the migration process for the new server I put 2 cables in my Dell R310 Server (LAN1 e LAN2). Because of it my DNS was crazy. I just removed that cable (LAN2), restarted the server.
Now everything is working perfectly. Thank you for all your help.
During the migration process for the new server I put 2 cables in my Dell R310 Server (LAN1 e LAN2). Because of it my DNS was crazy. I just removed that cable (LAN2), restarted the server.
Now everything is working perfectly. Thank you for all your help.
ASKER
I got the solution.
Also, paste the DCDIAG /v results from your server. I also would have tried pinging the DNS if., ping -t 192.168.1.1 along with ping -t google.com
Please check the TTL value and if you get any request time out events or destination unreachable events in between the lines, please paste those.
Are the clients also failing and complaining of the same issues? If yes, then it could be a domain wide issue or it could be machine specific if the console is behaving in a such a way. I would have downloaded another browser like a firefox or chrome to test with.
Good Luck..!!
~SG~