Find the answer to your Linux question:
Page 3 of 3 FirstFirst 1 2 3
Results 21 to 23 of 23
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #21
    Linux Guru Lazydog's Avatar
    Join Date
    Jun 2004
    The Keystone State

    I am glad you got this fixed. I am interested in what the linksys router was doing to break DNS.


    The adventure of a life time.

    Linux User #296285
    Get Counted

  2. #22
    I have no idea. I just replaced the router and things started to work.

    I did take a look at various settings on the router but couldn't identify anything that would cause this problem.

    Strangely, when I do a nslookup directly onto a root server, it works:

    nslookup wwwDOTgoogleDOTcom rootServerIP

    But when the same query goes through bind9 (as caught from tcpdump), I never receive a response back from the server.

    The only thing I could think of is that nslookup does a synchronous UDP communication where as bind9 is doing an asynchronous UDP communication.

    I am going to open a support case with Linksys to find out what is going on.


  3. #23
    I read an interesting article/blog/something from someone that found that their DNS queries were "timing out" due to some truncation of the response. They found that the DNS server was responding, but the return was being truncated and discarded (?) at some point...

    Just a guess...

  4. $spacer_open

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts