Date: Tue, 7 Jul 2015 13:06:48 +0000 From: Wei Hu <weh@microsoft.com> To: Pavel Timofeev <timp87@gmail.com>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>, "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: RE: MS DNS doesn't answer to CURRENT under Hyper-V Message-ID: <BY1PR03MB14341E54D68247F7BFAE7504BB920@BY1PR03MB1434.namprd03.prod.outlook.com> In-Reply-To: <CAAoTqftvtQunx%2BWCL4%2BBz-mYSgqCTcGx1aAyemfaz%2B=0ogZuWw@mail.gmail.com> References: <CAAoTqftvtQunx%2BWCL4%2BBz-mYSgqCTcGx1aAyemfaz%2B=0ogZuWw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: owner-freebsd-virtualization@freebsd.org [mailto:owner-freebsd- > virtualization@freebsd.org] On Behalf Of Pavel Timofeev > Sent: Tuesday, July 7, 2015 7:51 PM > To: freebsd-current@freebsd.org; freebsd-virtualization@freebsd.org > Subject: MS DNS doesn't answer to CURRENT under Hyper-V >=20 > Hi! > I have a test virtual machine which runs CURRENT under Hyper-V. It's > amd64 r285198 now. > It can't get any response from MS DNS server. Well, it could two or three > weeks ago, but after upgrade it's not able to do it anymore. > Google DNS answers without problems meanwhile (sic!). >=20 > What I do: > # host google.ru 192.168.25.3 > I see that MS DNS (192.168.25.3) server receives these packets, but ignor= es > them. > And no matter how my system asks MS DNS. Every daemon can't get > response too. >=20 > I know that nothing was changed in MS DNS server. No doubt. > Then I tried different available CURRENT snapshot ISOs. >=20 > FreeBSD-11.0-CURRENT-amd64-20150630-r284969-disc1.iso - MS DNS does > not answer. >=20 > FreeBSD-11.0-CURRENT-amd64-20150625-r284814-disc1.iso - MS DNS does > not answer. >=20 > FreeBSD-11.0-CURRENT-amd64-20150618-r284544-disc1.iso - MS DNS > answers! >=20 > So something was committed to CURRENT between 20150618 and 20150625. > This something ruins communication with MS DNS. >=20 There was a commit for Hyper-V TSO and checksum offloading support (r28474= 6) on=20 June 24th. I think this commit is the cause. Can you verify the MS DNS beha= vior between The builds of June 23rd and 24th? I will take a look of this issue tomorrow= . Thanks, Wei
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BY1PR03MB14341E54D68247F7BFAE7504BB920>