Hi..I have recently installed Win 7 Enterprise on my laptop on our company network. I have a problem with DNS which is starting to really get to me... I have a win 2003 server that issues DHCP and is the primary DNS server, in the DNS I have setup internal URLs i.e. intranet zone URL (intranet.network.co.uk)This is fine before on the Win XP PCs and server 2003's, but it seems that Win 7 and maybe Server 2008 can't resolve any URL names. If I ping a PC >Ping PC001it resolves to PC001.ourdomain.local (192.168.2.10)If I ping the intranet URL but add the suffix;>ping intranet.network.co.uk.ourdomain.localthen is resolves.However this is a pain in a internet browser and requires new setup to sharepoint and alsorts........ It used to be fine in XP why/what is the problem with Win7?thanks

Please refer the following article. Intranet site is identified as an Internet site when you use an FQDN or an IP addressArthur Xie - MSFT

I don't think that article will help..... the problem is not limited to MS IE or local zones, if you use the dos ping command the problem is clear;When I ping;>ping intranet.network.co.ukPing request could not find host....Yet if I ping;>ping intranet.network.co.uk.domain.localPing is resolved!I think this must be a Windows 7 DNS resolution issue....

I am also having DNS issues. I have two PCs running Windows 7, one PC running XP. The XP machine works fine but the Windows 7 machines frequently give me an error page "Could not find server." When working with IP addresses only everything works fine. In looking at a wireshark trace of the network, the Windows 7 machine DNS requests all have an incorrect checksum value and therefore are not responded to by the DNS server. After about 300 DNS queries it start to intermittently send DNS queries with the correct checksum and then finally will start working. This cycle repeats after about 10 minutes. Here are the wireshark traces directly from one of the windows 7 machine that was acting up. BAD DNS User Datagram Protocol, Src Port: 61328 (61328), Dst Port: domain (53) Source port: 61328 (61328) Destination port: domain (53) Length: 36 Checksum: 0x0f3a [incorrect, should be 0xf992 (maybe caused by "UDP checksum offload"?)] Good Checksum: False Bad Checksum: True GOOD DNS User Datagram Protocol, Src Port: domain (53), Dst Port: 62347 (62347) Source port: domain (53) Destination port: 62347 (62347) Length: 153 Checksum: 0x2abf [correct] Good Checksum: True Bad Checksum: False I've switch NICs in this machine and I have another Windows 7 machine doing the same thing. As I mentioned before, XP works fine with the network setup that has been working for years. I've tried pointing my PC to my ISP DNS servers directly, caching the ISP DNS then relaying it using my router, and using internet based DNS servers. Next step is to mirror a port on my switch so that I can get a better trace of what is actually on the wire but has anyone else run into this or have any ideas how I might fix this? Thanks!

Do you mean you are trying to use an internal namespace domain name that is different than the external name? If so, i suggest you access the following article. Using an Internal SubdomainArthur Xie - MSFT

I am also having DNS issues. I have two PCs running Windows 7, one PC running XP. The XP machine works fine but the Windows 7 machines frequently give me an error page "Could not find server." When working with IP addresses only everything works fine. In looking at a wireshark trace of the network, the Windows 7 machine DNS requests all have an incorrect checksum value and therefore are not responded to by the DNS server. After about 300 DNS queries it start to intermittently send DNS queries with the correct checksum and then finally will start working. This cycle repeats after about 10 minutes.Here are the wireshark traces directly from one of the windows 7 machine that was acting up.BAD DNSUser Datagram Protocol, Src Port: 61328 (61328), Dst Port: domain (53)Source port: 61328 (61328)Destination port: domain (53)Length: 36Checksum: 0x0f3a [incorrect, should be 0xf992 (maybe caused by "UDP checksum offload"?)]Good Checksum: FalseBad Checksum: TrueGOOD DNSUser Datagram Protocol, Src Port: domain (53), Dst Port: 62347 (62347)Source port: domain (53)Destination port: 62347 (62347)Length: 153Checksum: 0x2abf [correct]Good Checksum: TrueBad Checksum: FalseI've switch NICs in this machine and I have another Windows 7 machine doing the same thing. As I mentioned before, XP works fine with the network setup that has been working for years. I've tried pointing my PC to my ISP DNS servers directly, caching the ISP DNS then relaying it using my router, and using internet based DNS servers.Next step is to mirror a port on my switch so that I can get a better trace of what is actually on the wire but has anyone else run into this or have any ideas how I might fix this?Thanks! Are the two Windows 7 computers completely clean? This issue can be caused by the security programs, such as firewall and antivirus on the Windows 7 computers. Some of the security settings may be incorrect, or the programs are not compatible with Windows 7.Arthur Xie - MSFT

Hi Arthur. I think I solved my issue, although not exactly to my satisfaction. To answer your question, yes the machine are clean (new installs) and I have them running all the Microsoft security (security essentials, defender, etc.). First solution was to clear up the bad DNS requests. I did this by going into the NIC configuration and enabling the Checksum offload. On my XP machine, I didn't have this option. But once enabled, the UDP errors cleared. Next, I was still have some issues with DNS resolution (although now all my DNS packets were clean) so I pointed my DNS servers straight to the public DNS on the Internet, instead of proxying them through my router first (I originally have my router pointed to the public DNS, then point my Win7 DNS requests to my router). Now that the DNS bypasses this proxy, it seems to be working. It has a hiccup every now and again but nothing to the level it was before. Thanks for the reply.