DNS Issue
I have two Windows 2003 Server's running Active Directory DNS (one primary and one secondary) For some strange reason when i hit a URL i get page cannot be displayed. This is a very intermittemt problem. If i do NSLOOKUP from Primary DNS it's fine. If i
do the same lookup and specify the secondary DNS then i get something completly different. I get a 69.43 public address and not the internal IP which i get back from the Primary.
Anyone have any ideas, i've checked the logs but don't see anything.
Thanks
Luigi
May 4th, 2012 12:07pm
Does your DNS replicate at all ? Do you see both name in both DNS ? The public IP result just mean that the DNS's server #2 did not found the hostname localy and forwarded the requestMCP | MCTS 70-236: Exchange Server 2007, Configuring
Free Windows Admin Tool Kit Click here and download it now
May 4th, 2012 12:25pm
Thanks for your reply, Yes the Primary replicates to the Secondary and i do see the name in both of the DNS Servers. That all looks OK
May 4th, 2012 12:43pm
Try local at the second's DNS with the nslookup of the FQDN and with the short name you test, just to be sure it's not a prefix problem.MCP | MCTS 70-236: Exchange Server 2007, Configuring
Free Windows Admin Tool Kit Click here and download it now
May 4th, 2012 12:51pm
Hi, tested that and it's fine, same results on both servers
May 4th, 2012 1:12pm
Does your computer got only your DNS's server listed ? If no remove any public DNS's from your NIC configurationMCP | MCTS 70-236: Exchange Server 2007, Configuring
Free Windows Admin Tool Kit Click here and download it now
May 4th, 2012 1:42pm
Hello,
Please check that your DNS zones are AD-integrated and both DCs are DNS servers. Like that, each update on a DC will be replicate to another.
Please also proceed like that:
Make each DC points to the other one as primary DNS serverMake each DC points to its private IP address as secondary DNS server and 127.0.0.1 as third oneMake sure that each DC has one IP address in use and one NIC card enabled (all other NICs should be disabled)
Once done, run ipconfig /registerdns and restart netlogon on each DC you have.
If the problem persists then use Microsoft Skydrive to upload the output of these commands on all DCs you have:
ipconfig /all > c:\ipconfig.txtdcdiag /v /e > c:\dcdiag.txt
Once done, post a link here.
This
posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft
Student Partner 2010 / 2011
Microsoft
Certified Professional
Microsoft
Certified Systems Administrator: Security
Microsoft
Certified Systems Engineer: Security
Microsoft
Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows 7, Configuring
Microsoft
Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
Microsoft
Certified IT Professional: Enterprise Administrator
Microsoft Certified IT Professional: Server Administrator
Microsoft Certified Trainer
May 4th, 2012 4:47pm
Hello,
If I understand correctly, when you type a URL in your browser it resolves intermittently. Is that correct?
If you do an NS lookup from the Primary DC you get your local machine's IP address.
If you do an NS lookup from the secondary DC then the DNS that is answering your queries is a foreign IP. Is my understanding correct?
If so, look at the NIC settings of the secondary machine and make sure that the primary DNS is pointing to 127.0.0.1 and secondary is pointing to the local IP address of the primary DC.Miguel Fra | Falcon IT Services, Miami, FL
www.falconitservices.com |
www.falconits.com |
Blog
Free Windows Admin Tool Kit Click here and download it now
May 4th, 2012 9:02pm
Hello,
Please check that your DNS zones are AD-integrated and both DCs are DNS servers. Like that, each update on a DC will be replicate to another.
Please also proceed like that:
Make each DC points to the other one as primary DNS serverMake each DC points to its private IP address as secondary DNS server and 127.0.0.1 as third oneMake sure that each DC has one IP address in use and one NIC card enabled (all other NICs should be disabled)
Once done, run ipconfig /registerdns and restart netlogon on each DC you have.
If the problem persists then use Microsoft Skydrive to upload the output of these commands on all DCs you have:
ipconfig /all > c:\ipconfig.txtdcdiag /v /e > c:\dcdiag.txt
Once done, post a link here.
This
posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft
Student Partner 2010 / 2011
Microsoft
Certified Professional
Microsoft
Certified Systems Administrator: Security
Microsoft
Certified Systems Engineer: Security
Microsoft
Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows 7, Configuring
Microsoft
Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
Microsoft
Certified IT Professional: Enterprise Administrator
Microsoft Certified IT Professional: Server Administrator
Microsoft Certified Trainer
May 4th, 2012 11:39pm
Do you any A record for that site in DNS ? Is this problem you are getting on a single system ? are using ISA server as firewall for internet ?Sunil Pathare SR. System Admin
Free Windows Admin Tool Kit Click here and download it now
May 5th, 2012 2:09am
Hello,
If I understand correctly, when you type a URL in your browser it resolves intermittently. Is that correct?
If you do an NS lookup from the Primary DC you get your local machine's IP address.
If you do an NS lookup from the secondary DC then the DNS that is answering your queries is a foreign IP. Is my understanding correct?
If so, look at the NIC settings of the secondary machine and make sure that the primary DNS is pointing to 127.0.0.1 and secondary is pointing to the local IP address of the primary DC.Miguel Fra | Falcon IT Services, Miami, FL
www.falconitservices.com |
www.falconits.com |
Blog
May 5th, 2012 3:54am
If you enable debug mode in nslookup ("set d2"), you will notice whats going on and why its resolving it that way.
http://technet.microsoft.com/en-us/library/cc940085.aspx
http://www.arabitpro.com
Free Windows Admin Tool Kit Click here and download it now
May 5th, 2012 5:10am
If you enable debug mode in nslookup ("set d2"), you will notice whats going on and why its resolving it that way.
http://technet.microsoft.com/en-us/library/cc940085.aspx
http://www.arabitpro.com
May 5th, 2012 12:02pm
Hi,
As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as Answered as the previous steps should be helpful for many similar scenarios. If the issue still persists, please feel free to reply this
post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.
BTW, wed love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts.
Best Regards
KevinTechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
May 9th, 2012 1:55am


