Help required to test some Negative Responses from Bind Server.

Alan Clegg alan at clegg.com
Tue Jun 28 13:15:28 UTC 2016


SERVFAIL:   create a delegation NS record in your zone to a server that
isn't authoritative for the zone being delegated.
REFUSED:  create an ACL that matches (and denies) the query being done
NOERROR w/ no RR:   query for  example.com AAAA

As for NOTIMP, I'm not aware of an easy path, but I'm sure that someone here
knows.

AlanC

On 6/28/16, 2:07 AM, "bind-users on behalf of Harshith Mulky"
<bind-users-bounces at lists.isc.org on behalf of harshith.mulky at outlook.com>
wrote:

> Hello Experts,
> 
> 
> 
> As a tester who is testing a client(lwres) developed on same bind stack.
> 
> I would want to generate scenarios and test how the client responds when the
> bind server responds with negative Responses
> 
> 
> 
> I was able to test Negative response like NXDOMAIN as it was straight forward
> where a record is not present in particular Domain file
> 
> 
> 
> I would want to test a scenario where bind Server responds with the following
> Response Codes
> 
> 
> 
> 1. SERVFAIL
> 
> 2. REFUSED
> 
> 3. Receiving NOERROR, but no RR in response
> 
> 4. NOTIMP
> 
> 
> 
> If I have a basic Zone file like this, Can I be able to test the above 4
> scenarios
> 
> 
> 
> 
> $ORIGIN example.com.
> $TTL 600
> @  IN      SOA     atlanta.example.com. admin.example.com.  (
>                                       2003022720 ; Serial
>                                       56800      ; Refresh
>                                       14400      ; Retry
>                                       3600000    ; Expire
>                                       2h )    ; Minimum
> 
>               IN      NS      atlanta.example.com.
> 
> 
> atlanta.example.com.  IN A    10.54.48.68
> 
> ; zone ims.blueslice.com direct  - for some phones
> ;srvtesting.com.   IN A    10.128.254.115
> ;example.com.   IN A    10.54.25.75
> 
> ;;                 order preference flags service regexp replacement.
> ;        IN NAPTR   22   34   "u"        "SIP+D2U"       ""
> _sip._udp.test1.com.
>         IN NAPTR   22   32   "u"        "SIP+D2U"       ""
> _sip._udp.example.com.
>         IN NAPTR   22   32   "u"        "SIP+D2T"       ""
> _sip._tcp.example.com.
> ;        IN NAPTR   45   56   "u"        "SIP+D2T"       ""
> _sip._tcp.srvtesting.com.
> ;        IN NAPTR   45   56   "u"        "SIP+D2S"       ""
> _sip._sctp.srvtesting.com.
> 
> ; SRV records for each sip service
> ; service.prot.name   ttl class rr     pri weight port target
> ;_sip._udp               IN  SRV      3        2      7700 denver.example.com.
> _sip._udp               IN  SRV       0        40      7701
> denver1.example.com.
> _sip._tcp               IN  SRV       0        40      7701
> denver1.example.com.
> _sip._udp               IN  SRV       0        10      7702
> denver2.example.com.
> _sip._udp               IN  SRV       1        10      7703
> denver3.example.com.
> _sip._udp               IN  SRV       2        10      7704
> denver4.example.com.
> _sip._tcp               IN  SRV      1        1      0
> icscf52.srvtesting.com.
> _sip._sctp              IN  SRV      1        1      12215
> icscf71.srvtesting.com.
> 
> 
> denver1.example.com.  IN A    10.54.80.150
> denver1.example.com.  IN A    10.54.80.17
> denver2.example.com.  IN A    10.54.80.150
>   IN A    10.54.80.35
> ;denver3.example.com.  IN AAAA   fd00:10:6b50:4500::88
> ;denver2.example.com.  IN AAAA   fd00:10:6b50:4500::21
> ;denver2.example.com.  IN AAAA   fd00:10:6b50:4500::22
> example.com.  IN A   10.54.80.150
> example.com.  IN AAAA   fd00:10:6b50:4500::88
> denver1.example.com.  IN AAAA   fd00:10:6b50:4500::88
> 
> 
> 
> Thanks
> 
> Harshith
> _______________________________________________ Please visit
> https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this
> list bind-users mailing list bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20160628/fe40f0bf/attachment.html>


More information about the bind-users mailing list