Re: wget not resolving domain names

From: Derek Martin (code_at_pizzashack.org)
Date: 11/02/05

  • Next message: Derek Martin: "Re: Why Fedora ?" 
    Date: Wed, 2 Nov 2005 11:03:09 -0500
To: For users of Fedora Core releases <fedora-list@redhat.com>

    On Tue, Nov 01, 2005 at 06:08:04PM +0000, Paul Howarth wrote:
    > >; <<>> DiG 9.2.5 <<>> @192.168.0.253 www.uit.no
    > >; (1 server found)
    > >;; global options: printcmd
    > >;; Got answer:
    > >;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39902
    > >;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
    > >
    > >;; QUESTION SECTION:
    > >;www.uit.no. IN A
    > >
    > >;; ANSWER SECTION:
    > >www.uit.no. 10000 IN A 129.242.5.89
    > >
    > >;; Query time: 4 msec
    > >;; SERVER: 192.168.0.253#53(192.168.0.253)
    > >;; WHEN: Tue Nov 1 18:31:51 2005
    > >;; MSG SIZE rcvd: 44
    >
    > Hmm, that's interesting. Your nameserver appears to be returning bad
    > data, though curiously the first answer was the right one in this case.

    No, I don't think so... The address returned is the same as in the
    first query; the answer is correct. I believe the reason the data is
    different is because the first query showed authoritative data that
    the name server looked up, whereas the second query returned
    non-authoritative data that the name server had cached.

    There seems to be nothing wrong with this -- the client got the same
    address in both cases. 

    -- 
Derek D. Martin
http://www.pizzashack.org/
GPG Key ID: 0x81CFE75D



    


    -- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
  • Next message: Derek Martin: "Re: Why Fedora ?"

    Relevant Pages

    • Re: wget not resolving domain names
      ... > first query; the answer is correct. ... > non-authoritative data that the name server had cached. ... The distinction is important because, if say someone was to try sending ... MTA should spot the CNAME record and rewrite the address as ...
      (Fedora)
    • Full text slow startup on SQL 2005 x64, Win2003 x64
      ... The first query ... On another server with the same database we don't see this problem. ... The other server is running SQL 2005 Standard and Windows 2003 Standard. ...
      (microsoft.public.sqlserver.fulltext)
    • Re: efficient way to retrieve master-details data
      ... If you select data from SQL Server with a stored procedure like the ... query can take usage of the result in cache. ... THE SAME WHERES OF FIRST QUERY); ...
      (microsoft.public.dotnet.framework.adonet)
    • Re: Full text slow startup on SQL 2005 x64, Win2003 x64
      ... We tried everything, from reinstalling SQL Server 2005, disabling services, ... The first query ... >> On another server with the same database we don't see this problem. ...
      (microsoft.public.sqlserver.fulltext)