![]() |
|
Welcome to Vista Banter. You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
|
|||||||
| Networking with Windows Vista Networking issues and questions with Windows Vista. (microsoft.public.windows.vista.networking_sharing) |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
Using Vista Gold, I have IPv4 unchecked. I've statically assigned my Primary
DNS server to be fed0::10. I can ping it fine. When I ping the name associated with fed0::10 (bunt.wateng.org), it resolves perfectly ... 22-Feb-2007 11:35:21.124 queries: client fed0::a069:6611:1e1c:8dc8#49675: query: bunt.wateng.org IN AAAA + Reply from fed0::10%1: time=15ms Reply from fed0::10%1: time=1ms Reply from fed0::10%1: time=1ms Reply from fed0::10%1: time=1ms My DNS server logs also show that the DNS lookup was requested and answered perfectly. The problem is with nslookup. If I attempt to "nslookup bunt.wateng.org" I get the following ... Server: Unknown Address: 127.0.0.1:53 *** UnKnown can't find bunt.wateng.org: No response from server I don't even see an attempt at my DNS server. There is nothing in my hosts file. In fact, even if I make an entry into the hosts file, it _still_ doesn't resolve. If anyone can offer any input on this, i'd be happy to hear it ;-) |
|
|||
|
My input is that Microsoft rushed Vista out the door without having the
networking piece completely finished. For example, DHCP only works on SOME routers / access points. If you use a Gateway on a different subnet, FORGET IT! You have to hard enter all of the IP info for the adapter. Forget the alternate configuration, it just doesn't work at all. This all leads me to believe that MS shoved this out the door without the level of testing and development that is critical for networking. "bozack" wrote: Using Vista Gold, I have IPv4 unchecked. I've statically assigned my Primary DNS server to be fed0::10. I can ping it fine. When I ping the name associated with fed0::10 (bunt.wateng.org), it resolves perfectly ... 22-Feb-2007 11:35:21.124 queries: client fed0::a069:6611:1e1c:8dc8#49675: query: bunt.wateng.org IN AAAA + Reply from fed0::10%1: time=15ms Reply from fed0::10%1: time=1ms Reply from fed0::10%1: time=1ms Reply from fed0::10%1: time=1ms My DNS server logs also show that the DNS lookup was requested and answered perfectly. The problem is with nslookup. If I attempt to "nslookup bunt.wateng.org" I get the following ... Server: Unknown Address: 127.0.0.1:53 *** UnKnown can't find bunt.wateng.org: No response from server I don't even see an attempt at my DNS server. There is nothing in my hosts file. In fact, even if I make an entry into the hosts file, it _still_ doesn't resolve. If anyone can offer any input on this, i'd be happy to hear it ;-) |
|
|||
|
It definately looks like it is broken. Can we get an MS guy in here to
confirm that this is a bug? "Bill Wood" wrote: My input is that Microsoft rushed Vista out the door without having the networking piece completely finished. For example, DHCP only works on SOME routers / access points. If you use a Gateway on a different subnet, FORGET IT! You have to hard enter all of the IP info for the adapter. Forget the alternate configuration, it just doesn't work at all. This all leads me to believe that MS shoved this out the door without the level of testing and development that is critical for networking. "bozack" wrote: Using Vista Gold, I have IPv4 unchecked. I've statically assigned my Primary DNS server to be fed0::10. I can ping it fine. When I ping the name associated with fed0::10 (bunt.wateng.org), it resolves perfectly ... 22-Feb-2007 11:35:21.124 queries: client fed0::a069:6611:1e1c:8dc8#49675: query: bunt.wateng.org IN AAAA + Reply from fed0::10%1: time=15ms Reply from fed0::10%1: time=1ms Reply from fed0::10%1: time=1ms Reply from fed0::10%1: time=1ms My DNS server logs also show that the DNS lookup was requested and answered perfectly. The problem is with nslookup. If I attempt to "nslookup bunt.wateng.org" I get the following ... Server: Unknown Address: 127.0.0.1:53 *** UnKnown can't find bunt.wateng.org: No response from server I don't even see an attempt at my DNS server. There is nothing in my hosts file. In fact, even if I make an entry into the hosts file, it _still_ doesn't resolve. If anyone can offer any input on this, i'd be happy to hear it ;-) |
|
|||
|
At first glance, I'd say you've probably hit a bug in nslookup -- it's not
picking up the DNS server for your IPv6 environment. (It repros on my system when I disable IPv4.) I've e-mailed the PM for nslookup to check into this. Thanks. "bozack" a écrit dans le message de ... Using Vista Gold, I have IPv4 unchecked. I've statically assigned my Primary DNS server to be fed0::10. I can ping it fine. When I ping the name associated with fed0::10 (bunt.wateng.org), it resolves perfectly ... 22-Feb-2007 11:35:21.124 queries: client fed0::a069:6611:1e1c:8dc8#49675: query: bunt.wateng.org IN AAAA + Reply from fed0::10%1: time=15ms Reply from fed0::10%1: time=1ms Reply from fed0::10%1: time=1ms Reply from fed0::10%1: time=1ms My DNS server logs also show that the DNS lookup was requested and answered perfectly. The problem is with nslookup. If I attempt to "nslookup bunt.wateng.org" I get the following ... Server: Unknown Address: 127.0.0.1:53 *** UnKnown can't find bunt.wateng.org: No response from server I don't even see an attempt at my DNS server. There is nothing in my hosts file. In fact, even if I make an entry into the hosts file, it _still_ doesn't resolve. If anyone can offer any input on this, i'd be happy to hear it ;-) |
|
|||
|
Just to let you know, I've followed up with the team that owns nslookup,
confirmed the issue, and opened a bug against them. To boil it down, nslookup ignores site-local IPv6 addresses when selecting a DNS server to query. If you configure your client with the DNS server's global IPv6 address, it should find it. "Michael A. Bishop (MSFT)" a écrit dans le message de ... At first glance, I'd say you've probably hit a bug in nslookup -- it's not picking up the DNS server for your IPv6 environment. (It repros on my system when I disable IPv4.) I've e-mailed the PM for nslookup to check into this. Thanks. "bozack" a écrit dans le message de ... Using Vista Gold, I have IPv4 unchecked. I've statically assigned my Primary DNS server to be fed0::10. I can ping it fine. When I ping the name associated with fed0::10 (bunt.wateng.org), it resolves perfectly ... 22-Feb-2007 11:35:21.124 queries: client fed0::a069:6611:1e1c:8dc8#49675: query: bunt.wateng.org IN AAAA + Reply from fed0::10%1: time=15ms Reply from fed0::10%1: time=1ms Reply from fed0::10%1: time=1ms Reply from fed0::10%1: time=1ms My DNS server logs also show that the DNS lookup was requested and answered perfectly. The problem is with nslookup. If I attempt to "nslookup bunt.wateng.org" I get the following ... Server: Unknown Address: 127.0.0.1:53 *** UnKnown can't find bunt.wateng.org: No response from server I don't even see an attempt at my DNS server. There is nothing in my hosts file. In fact, even if I make an entry into the hosts file, it _still_ doesn't resolve. If anyone can offer any input on this, i'd be happy to hear it ;-) |