Issues

• Check for expected field lengths on receiving request

  twtiger/nameserver#21 · Filter by author chelseakomlo opened on Aug 9, 2016

• Nameserver receives a redirect to the next nameserver to query to another nameserver

  twtiger/nameserver#13 · Filter by author chelseakomlo opened on Aug 1, 2016

• Nameserver receives complete response for query to another nameserver

  twtiger/nameserver#12 · Filter by author chelseakomlo opened on Aug 1, 2016

• Nameserver receives query that it has no information for from resolver

  twtiger/nameserver#11 · Filter by author chelseakomlo opened on Aug 1, 2016

• Nameserver receives query that it has partial information for from resolver

  twtiger/nameserver#10 · Filter by author chelseakomlo opened on Aug 1, 2016

• Nameserver receives query that it can resolve immediately from resolver

  twtiger/nameserver#9 · Filter by author chelseakomlo opened on Aug 1, 2016
  7

• Spike: How to handle nameserver attacks/cache poisening/other security issues

  twtiger/nameserver#8 · Filter by author chelseakomlo opened on Aug 1, 2016

• Spike: how are primary vs secondary nameservers managed?

  twtiger/nameserver#6 · Filter by author chelseakomlo opened on Aug 1, 2016

• Spike: different server actions based on the record that is requested

  twtiger/nameserver#5 · Filter by author chelseakomlo opened on Aug 1, 2016

• Spike: how to handle caching/TTL

  twtiger/nameserver#4 · Filter by author chelseakomlo opened on Aug 1, 2016

• Spike: how does email work with DNS?

  twtiger/nameserver#3 · Filter by author chelseakomlo opened on Aug 1, 2016

• Decide scope of implementation

  twtiger/nameserver#1 · Filter by author chelseakomlo opened on Jul 26, 2016
  1