I think, the _sip._udp.fetest.at does not have corresponding SRV record. I
guessm It shoud be
_sip._udp.fetest.at     SRV 0 1 5060    sipPC.fetest.at.

Please find the configuration file I am using. This might be of use

sip.udp IN      3H      SRV     1       1       5060    test1
test1   IN      3H      A       10.1.1.11

bigu.edu        IN      3H      NAPTR   2       0       "s"     "SIP+D2U"

my zone is testdns. If you do a query for bigu.edu.testdns, the NAPTR and
its corresponding SRV records will be returned.

Thanks,
Babu

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Franz Edler
Sent: Thursday, August 18, 2005 3:31 PM
To: [email protected]
Subject: [Sip-implementors] How to do a correct NAPTR query?

Hello!

Does anyone have a correct example of a NAPTR record and a NAPTR query?

>From my point of view I have put correct NAPTR records in my zone file
(fetest.at), but the query does not get any result.

See below the records in my zone file and the DNS query and response

Any help appreciated.

Franz



This are both records in my zone file: NAPTR and SRV

                IN NAPTR 100 50 "s" "SIP+D2U" ""        _sip._udp.fetest.at.
_sip._udp       SRV 0 1 5060    sipPC.fetest.at.


and this is the query and the response:

Domain Name System (query)
    Transaction ID: 0xba99
    Flags: 0x0100 (Standard query)
        0... .... .... .... = Response: Message is a query
        .000 0... .... .... = Opcode: Standard query (0)
        .... ..0. .... .... = Truncated: Message is not truncated
        .... ...1 .... .... = Recursion desired: Do query recursively
        .... .... .0.. .... = Z: reserved (0)
        .... .... ...0 .... = Non-authenticated data OK: Non-authenticated
data is unacceptable
    Questions: 1
    Answer RRs: 0
    Authority RRs: 0
    Additional RRs: 0
    Queries
        fetest.at: type NAPTR, class IN
            Name: fetest.at
            Type: NAPTR (Naming authority pointer)
            Class: IN (0x0001)


        
Domain Name System (response)
    Transaction ID: 0xba99
    Flags: 0x8580 (Standard query response, No error)
        1... .... .... .... = Response: Message is a response
        .000 0... .... .... = Opcode: Standard query (0)
        .... .1.. .... .... = Authoritative: Server is an authority for
domain
        .... ..0. .... .... = Truncated: Message is not truncated
        .... ...1 .... .... = Recursion desired: Do query recursively
        .... .... 1... .... = Recursion available: Server can do recursive
queries
        .... .... .0.. .... = Z: reserved (0)
        .... .... ..0. .... = Answer authenticated: Answer/authority portion
was not authenticated by the server
        .... .... .... 0000 = Reply code: No error (0)
    Questions: 1
    Answer RRs: 0
    Authority RRs: 1
    Additional RRs: 0
    Queries
        fetest.at: type NAPTR, class IN
            Name: fetest.at
            Type: NAPTR (Naming authority pointer)
            Class: IN (0x0001)
    Authoritative nameservers
        fetest.at: type SOA, class IN, mname sipPC.fetest.at
            Name: fetest.at
            Type: SOA (Start of zone of authority)
            Class: IN (0x0001)
            Time to live: 1 day
            Data length: 35
            Primary name server: sipPC.fetest.at
            Responsible authority's mailbox: root.sipPC.fetest.at
            Serial number: 2005081600
            Refresh interval: 3 hours
            Retry interval: 1 hour
            Expiration limit: 7 days
            Minimum TTL: 1 day

_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

Reply via email to