Does it resolve? It really sounds like the server is multihomed: IPconfig /all at the command prompt would tell you how many interfaces you have. You might switch to google's DNS servers as a forwarder. Thanks for your help Thursday, October 14, 2010 2:30 AM Reply | Quote 0 Sign in to vote Hi kumarunk, Thanks for posting the info. Check This Out
Still the same issue, probably should have mentioned that. 0 LVL 14 Overall: Level 14 SBS 9 DNS 1 Message Author Comment by:plug12011-10-31 Comment Utility Permalink(# a37056611) Sorry, its also PTR record query for the 188.8.131.52.in-addr.arpa. The solution, as per the article, is to reserve specific ports in the registry. Has any hardware changed? https://social.technet.microsoft.com/Forums/windowsserver/en-US/1a3189b9-bf2c-46dd-b414-80ee0a8f3285/dns-issues-sbs-2003?forum=winserverNIS
Start the Active Directory Users and Computers MMC snap-in, and then verify that the RootDNSServers container has been recreated and contains the root servers that were listed in the DNS Manager. In few cases this blocked DNS. It takes multiple attempts to finally have the server accept your login. Can it work?
Remove everything other than 10.31.21.6 fo the DNS entry. The server, for obvious reasons, is setup to start back up after a restored power failure. Assume that the Web Access server is assigned 192.168.1.10 as an IP address, which is NAT-resolved to a “real” IP address so that it’s accessible from the outside of the network. culleymcalpine.local failed test DNS 0 LVL 16 Overall: Level 16 SBS 5 DNS 3 Message Active today Expert Comment by:Michael Ortega (Internetwerx, Inc.)2011-10-30 Comment Utility Permalink(# a37053433) You change anything
Be wary of underscores, and hostnames with only numbers. http://blogs.technet.com/b/sbs/archive/2008/07/17/some-services-may-fail-to-start-or-may-not-work-properly-after-installing-ms08-037-951746-and-951748.aspx Cheers RobWill - Noted PS- It is not a case of an inability to resolve "some top level/specific domains" is it? The server should be using itself only for DNS and the clients should be using the server only for DNS. When a client, or even the DC itself needs to "find" a DC for an AD related function such as to authenticate to a mapped drive, printer, Exchange looking for the
Do you have correct IP address in the resource records for the very server itself. MO 0 LVL 16 Overall: Level 16 SBS 5 DNS 3 Message Active today Expert Comment by:Michael Ortega (Internetwerx, Inc.)2011-11-01 Comment Utility Permalink(# a37062130) Plug1, how about getting on the As such the majority of these customers utilize some version of Small Business Server. Its second best feature is the ability to monitor the health of individual VMware virtual machines.
As far as Dynamic DNS registration is involved, the DC is trying to register the necessary SRV and other records, but if it's sending the records to the ISP's DNS, that You see, if the client doesn't have the web site cached it will seek an answer from the preferred server (in this case google's dns servers)... Recently for some reason the users could not connect to the internet from their client PCs. Even though it’s a well known and well understood service, Windows Server 2003’s DNS implementation can still create headaches for the administrator that needs to maintain it.
The local machines need to address the machine using the private IP address while external clients need to use the real IP address.Windows 2003 can be used to service the needs his comment is here Then, see if you have DNS through the firewall/router from that client. I'm not sure where you're going with the DHCP thing. If so, post the EventID# and Source Name please.
MO 0 LVL 14 Overall: Level 14 SBS 9 DNS 1 Message Author Comment by:plug12011-11-01 Comment Utility Permalink(# a37065880) No packet loss at all, Ive ran malware bytes and mcafee, Or your clients find the proper DNS server for resolution, joy. In SBS environment, SBS serve should handle both internal DNS name resolution and external public DNS name resolution for domain clients. this contact form Make sure it’s running!
Beware that the cause is nothing to do with DNS. Now that I'm looking at the results of the DCDIAG it's obvious you have some DNS issues on that SBS itself. Covered by US Patent.
Look for patterns, spot what is out of the ordinary, such as resource records that is different, or a spelling misNake in a forwarder name.The Event LogMicrosoft has provided a clue There is a known issue, which to the best of my knowledge only applies to SBS 2008/2011 where DNS fails to resolve some domains, but most commonly the problem is with On the General tab’s Dynamic Updates selection, make sure that either Nonsecure And Secure or Secure Only is selected, as shown in Figure B.Figure BSelect Nonsecure And Secure or Secure Only This is the story of an SBS server which was originally setup as a gateway router with two network interfaces (WAN/LAN) only later to be re-configured to connect to the internet
PTR record query for the 184.108.40.206.in-addr.arpa. So now the users can connect to internet without any issues. However I don't see this as being your problem as your DNS sometimes works. navigate here Let's try this: Assuming ICMP is allowed, ping 220.127.116.11 from their workstation and from the server.
It is a domain server used for DNS, DHCP, file server and exchange duties. Can you run both the simple and recursive tests to see if you get a "Pass" for both.