[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] latest GPLPV drivers 0.10.0.86 and microsoft.com
On Fri, Sep 4, 2009 at 7:21 PM, Ian Tobin<itobin@xxxxxxxxxxxxx> wrote: > Hi, > > I realise you can't ping Microsoft.com, but the problem is it just doesn't > even resolve the IP address. Its any Microsoft.com websites. AF, OK, so we're getting close. Previously you said DNS is fine :D Can you run this on the PV domU AND a physical machine on the same network, and paste the results : - nslookup www.microsoft.com - ping www.microsoft.com - the error message when you try to access www.microsoft.com Also if possible, try setting up Bind (https://www.isc.org/software/bind), and run "dig +trace microsoft.com". It should print the DNS query path. Here's the result from my PC: $ dig +trace microsoft.com ; <<>> DiG 9.5.1-P2 <<>> +trace microsoft.com ;; global options: printcmd . 4190 IN NS I.ROOT-SERVERS.NET. . 4190 IN NS J.ROOT-SERVERS.NET. . 4190 IN NS K.ROOT-SERVERS.NET. . 4190 IN NS L.ROOT-SERVERS.NET. . 4190 IN NS M.ROOT-SERVERS.NET. . 4190 IN NS A.ROOT-SERVERS.NET. . 4190 IN NS B.ROOT-SERVERS.NET. . 4190 IN NS C.ROOT-SERVERS.NET. . 4190 IN NS D.ROOT-SERVERS.NET. . 4190 IN NS E.ROOT-SERVERS.NET. . 4190 IN NS F.ROOT-SERVERS.NET. . 4190 IN NS G.ROOT-SERVERS.NET. . 4190 IN NS H.ROOT-SERVERS.NET. ;; Received 448 bytes from 192.168.17.15#53(192.168.17.15) in 21 ms com. 172800 IN NS F.GTLD-SERVERS.NET. com. 172800 IN NS G.GTLD-SERVERS.NET. com. 172800 IN NS H.GTLD-SERVERS.NET. com. 172800 IN NS J.GTLD-SERVERS.NET. com. 172800 IN NS C.GTLD-SERVERS.NET. com. 172800 IN NS D.GTLD-SERVERS.NET. com. 172800 IN NS M.GTLD-SERVERS.NET. com. 172800 IN NS A.GTLD-SERVERS.NET. com. 172800 IN NS K.GTLD-SERVERS.NET. com. 172800 IN NS E.GTLD-SERVERS.NET. com. 172800 IN NS L.GTLD-SERVERS.NET. com. 172800 IN NS I.GTLD-SERVERS.NET. com. 172800 IN NS B.GTLD-SERVERS.NET. ;; Received 491 bytes from 202.12.27.33#53(M.ROOT-SERVERS.NET) in 101 ms microsoft.com. 172800 IN NS ns1.msft.net. microsoft.com. 172800 IN NS ns2.msft.net. microsoft.com. 172800 IN NS ns3.msft.net. microsoft.com. 172800 IN NS ns4.msft.net. microsoft.com. 172800 IN NS ns5.msft.net. ;; Received 209 bytes from 192.48.79.30#53(J.GTLD-SERVERS.NET) in 227 ms microsoft.com. 3600 IN A 207.46.232.182 microsoft.com. 3600 IN A 207.46.197.32 ;; Received 63 bytes from 64.4.59.173#53(ns2.msft.net) in 208 ms Probably you're having network problems connecting to ns*.msft.net? > > Theres no malware as its a fresh build. I have just finished creating the > new image and now it can ping but i have not installed anything yet so ill do > it once step at a time. > > Just for your info its 2 seperate DomUs having this problem maintained by > different people so unlikely a config problem. > > Ill let you know. > > Oh and tried disabling the PV drivers but had no effect That pretty much ruled out PV driver problem. If ALL DNS lookup fails, I'd say it's probably network issue. But since it's only microsoft.com, I'm suspecting problem with your existing DNS server or connection to MS' name server. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |