Say we have a domain "example.org" and it has an authoritative name server with name "ns1.example.org" with a glued IP as delegated by domain registrars (delegative?) name servers.
Someone types example.org into their browser:
Request is passed onto the ISP's DNS server. When the ISP's caching name server(s)/local cache does not find a match for the domain "example.org" and its respective (Copy of SOA record? or (WebServer IP?, Authoritative Name Sever IP?, Both ?)) the ISP's DNS then attempts to resolve the Authoritative name server IP(s) for the "example.org" domain by quering the WHOIS database with the domain name "example.org"? Or does it pass the request to the root ".org" server which then queries the whois database for the Authoritative Name Sever IP(s) using the domain name "example.org" to find a matching glue record?
The WHOIS database is part of the Internet central directory, I take it the main root servers are what is refered to as the "Internet central directory" ?
The root .org servers will contain the glue records for "example" domain and request for "example.org" will be finally forwarded to the Authoritative Name server. Where the A\AAA records will map the domain name "example.org" to an address for a resource such as WebServer etc.
Also is there such thing as a delegated NS name record that is not glued to an IP address for the authoritative DNS server which hosts and publishes its zone file? Because I read in a book about a circular dependecy/catch-22 problem when NS name is a sub-domain of the domain being resolved and straight away thought aren't all delegated NS names tied to an IP address so why would it occur?