Dns windows vista problem




















DNS servers do the same. It's only real purpose is to make browsing the Internet easier for people. People like to pull up websites using names. Computers like to pull up websites using IP address numbers. Names, unlike numbers, are easier for people to remember. That does not change the fact that computers networks still insist on IP address numbers.

The solution is DNS servers. DNS servers are servers on the Internet that do the cross-referencing between the two to satisfy both the network and people. DNS servers are like the phone books of the Internet. DNS works out of your view, behind the scenes. Before we do, just for good measure, verify that you can not pull up Google.

If it does not pull up, try pulling up Google by keying in one of its IP addresses in the chart above instead of its name in the address bar. Yes: You simulated what the DNS server was supposed to do and it works for you. It is definitely a DNS server problem. No: DNS is not a factor. You manually did the dirty work that the DNS server would normally do and it made no difference. It is not an issue with the DNS server and the problem lies elsewhere.

You would want to find out the IP addresses of those sites. One way to find out the IP address of a web server that is hosting the web site you are trying to access is by using the PING command from any computer that can view web pages does not need to be in your house.

Using the Ping command with the name of the website gives us the IP address. The "Reply from The first step would be to check your DNS server settings. Media State. Connection-specific DNS Suffix. Physical Address. DHCP Enabled. Autoconfiguration Enabled. Ethernet adapter Local Area Connection:. Link-local IPv6 Address.

IPv4 Address. Subnet Mask. Default Gateway. DNS Servers. Ethernet adapter Wireless Network Connection:. Dhcp Enabled. IP Address. Before moving on, I suggest you manually assign Primary Dns Suffix to the computer.

Click Start, right click Computer and choose Properties. Click Advanced system settings. Click the Computer Name tab. Click Change, and then click More. Please modify the Primary Dns Suffix settings. After applying these changes, restart the computer. Then, please let me know whether is DNS server is a computer and its operating system. As many factors can cause this network problem, I suggest enabling Netmon on both machines to capture the network packets for further research:.

Note: Please start NetMon on both machines. To obtain the phone numbers for specific technology request please take a look at the website listed below:. Robinson Zhang:. I will inform you soon. Thank you for your help. Hello Robinson Zhang. I left the Microsoft Network Monitor issue to the administrator in my company, and its up to him, he will contact microsoft tech persons to fix this problem.

But here's the updates:. Today my friend bring his new laptop to work, and 1st time use it on network, it obtain IP automatically, same problem. I installed windows vista business on new computer, also same problem. I opened 2 cmd windows 1st one i used "ping Office Office Exchange Server. Not an IT pro? Begin the tests in the following procedure by querying a valid root server. The test takes you through a process of querying all the DNS servers from the root down to the server that you're testing for a broken delegation.

Resource record type is the type of resource record that you were querying for in your original query, and FQDN is the FQDN for which you were querying terminated by a period. If the response includes a list of "NS" and "A" resource records for delegated servers, repeat step 1 for each server and use the IP address from the "A" resource records as the server IP address.

If the response does not contain an "NS" resource record, you have a broken delegation. If the response contains "NS" resource records, but no "A" resource records, enter set recursion , and query individually for "A" resource records of servers that are listed in the "NS" records.

If you do not find at least one valid IP address of an "A" resource record for each NS resource record in a zone, you have a broken delegation. If you determine that you have a broken delegation, fix it by adding or updating an "A" resource record in the parent zone by using a valid IP address for a correct DNS server for the delegated zone. If root hints appear to be configured correctly, verify that the DNS server that's used in a failed name resolution can ping the root servers by IP address.

If the root servers do not respond to pinging by IP address, the IP addresses for the root servers might have changed. However, it's uncommon to see a reconfiguration of root servers. If the server restricts zone transfers to a list of servers, such as those listed on the Name Servers tab of the zone properties, make sure that the secondary server is on that list.

Make sure that the server is configured to send zone transfers. Check the primary server for problems by following the steps in the Check DNS server problems section. When you're prompted to perform a task on the client, perform the task on the secondary server instead. If it is, the problem might have one of the following causes:.

The Windows primary server might be configured to send fast zone transfers, but the third-party secondary server might not support fast-zone transfers. If this is the case, disable fast-zone transfers on the primary server from within the DNS console by selecting the Enable Bind secondaries check box on the Advanced tab of the properties for your server. If a forward lookup zone on the Windows server contains a record type for example, an SRV record that the secondary server does not support, the secondary server might have problems pulling the zone.

If so, it's possible that the zone on the primary server includes incompatible resource records that Windows does not recognize. If either the master or secondary server is running another DNS server implementation, check both servers to make sure that they support the same features.

You can check the Windows server in the DNS console on the Advanced tab of the properties page for the server. In addition to the Enable Bind secondaries box, this page includes the Name checking drop-down list. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode.



0コメント

  • 1000 / 1000