Networking :: DNS does not work

Quote (^thehatsrule^ @ June 06 2007,15:12)

Well ns2.granitecanyon.com doesn't work for me either, but ns1 works. You could also try yahoo's ... it is ns?.yahoo.com (where ? is a number)

I still think that your local network or system may be 'specially' set up in some way though...

For packet sniffing/logging you can try out Ethereal - it's pretty good.

I downloaded Wireshark (the update to Ethereal) and, surprisingly, the UDP port 53 requests are going to some strange DNS server which doesn't work! ("Strange" in the sense that it's not listed as a DNS server on any of my DHCP-initiated interfaces.)

What's even more bizarre, if, from QEMU DSL, I try

Code Sample

nslookup yahoo.com ns1.yahoo.com

the packets still go to this strange address -- not ns1.yahoo.com .

I still don't know what's going on. It's as if QEMU is determined to send all UDP packets to this one IP address no matter what.

Quote

the packets still go to this strange address

Hah, you probably need to resolve ns1.yahoo.com first! (perhaps using a direct ip may be better?)

Quote (^thehatsrule^ @ June 07 2007,16:02)

Hah, you probably need to resolve ns1.yahoo.com first! (perhaps using a direct ip may be better?)

Incredible.

Code Sample

$ nslookup yahoo.com 66.218.71.63
Server: ns1.yahoo.com
Address: 66.218.71.63

Name: yahoo.com
Addresses: 66.94.234.13, 216.109.112.135

So, it's apparently completely QEMU's fault -- it's using this weird IP address.

At least, this means I have a fighting chance. If I could find a local DNS server that actually worked normally, I could change /etc/resolv.conf and I'd be golden.

Thanks for the insight!!

OK, I think I figured it out.

The problem is that most network traffic seems to go through this Microsoft ISA Server Firewall thing via a program called the Microsoft Firewall Client. If I disable this program, DNS no longer works. (I presume it's trying to use those broken servers that get configured into the network interfaces via DHCP.)

I don't know how DNS ever worked. Perhaps somebody turned it off (due to some security restriction), and now it's permanently off.

Maybe I could run a caching DNS server to get around this problem.

Do you (or anybody) have any recommendations?

When I used to use windows as a server+router, I used to have intermittent DNS problems, although I never figured out what the problem was. I did the old fashioned reformat

(temporary solution was to restart the dns windows service I think)

For now, you can just use a public dns server... shouldn't take up much bandwidth at all - but probably using your direct ISP's dns server would be better. But if you do want to run your own separate local DNS server, that's fine as well.

Next Page...
original here.