[Twisted-Python] twisted.names; authority query

Andy Gayton andy at thecablelounge.com
Sun Feb 15 13:18:27 EST 2004


Hi there,

I've extended twisted.names to support tinydns data files.  

names isn't responding with authoritive answers the way I was expecting it to though.  names responds that it is authoritive for my name server, but not for anything else.  This is the tinydns file I'm using:

-----------------------------------
.cablelounge.com::ns1.cablelounge.com:259200
=cablelounge.com:69.10.144.170:86400
+www.cablelounge.com:69.10.144.170:86400
+miles.cablelounge.com:69.10.144.170:86400
+twisted.cablelounge.com:203.113.212.32:900
+ns1.cablelounge.com:69.10.144.170:86400
@cablelounge.com:69.10.144.170:mail.cablelounge.com:0:86400
------------------------------------

names says that it is authoritive for ns1.cablelounge.com, but nothing else.  tinydns responds as authoritive for all of the above names:

#> dig @cablelounge.com cablelounge.com

I ran a standard pyzone file through names and got the same result .. so I'm not sure where I'm going wrong .. .

Here's what I did with the pyzone file:

zones:
-----------------------
zone = [
    SOA(
        "fred.com",
        mname   = "ns1.fred.com",
        rname   = "hostmaster.fred.com",
        serial  = 2004021501,
        refresh = "1H",
        retry   = "1H",
        expire  = "1H",
        minimum = "1H"
    ),

    A("fred.com", "192.168.10.10"),
    NS("ns1.fred.com", "fred.com"),
    A("ns1.fred.com", "192.168.10.10"),
]
------------------------

#> mktap dns --pyzone=zones --port 5053
#> twistd -f dns
#> dig -p 5053 @cablelounge.com fred.com

; <<>> DiG 9.2.1 <<>> -p 5053 @cablelounge.com fred.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48786
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;fred.com.                      IN      A

;; ANSWER SECTION:
fred.com.               3600    IN      A       192.168.10.10

;; Query time: 2 msec
;; SERVER: 69.10.144.170#5053(cablelounge.com)
;; WHEN: Sun Feb 15 10:01:29 2004
;; MSG SIZE  rcvd: 42

#> dig -p 5053 @cablelounge.com ns1.fred.com

; <<>> DiG 9.2.1 <<>> -p 5053 @cablelounge.com ns1.fred.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63056
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1

;; QUESTION SECTION:
;ns1.fred.com.                  IN      A

;; ANSWER SECTION:
ns1.fred.com.           3600    IN      A       192.168.10.10

;; AUTHORITY SECTION:
ns1.fred.com.           3600    IN      NS      fred.com.

;; ADDITIONAL SECTION:
fred.com.               3600    IN      A       192.168.10.10

;; Query time: 2 msec
;; SERVER: 69.10.144.170#5053(cablelounge.com)
;; WHEN: Sun Feb 15 10:02:24 2004
;; MSG SIZE  rcvd: 76

twisted.names is showing as authoritive for ns1.fred.com, but not fred.com.

Has anyone had a similiar experience with twisted.names?  What am I overlooking?

regards,
Andy.




More information about the Twisted-Python mailing list