In article <1167855244.414900.55150@v33g2000cwv.googlegroups. com>,
Keith Gable <ziggythehamster@gmail.com> wrote:
>Hello all,
>
>I have a small question. I've been Googling for a while, and reading in
>a book I bought (DNS and BIND), and I still can't figure this out.
>Typically, when you register a domain, you're asked for the nameserver
>address, and it's typically something like ns1.yourserver.com. My
>question is how exactly you'd do this if nobody knows where
>yourserver.com's nameservers are yet. Obviously, you could enter the IP
>address of the machine as the nameserver, but I've been poking around,
>and it doesn't look like anyone does this.
>
>For example, the nameservers for dreamhost.com are ns1.dreamhost.com
>and ns2.dreamhost.com. How exactly does DNS work in this reguard? I
>mean, I request dreamhost.com, I get sent to ".", then "com.", then
>that says that I should look at "ns1.dreamhost.com." for dreamhost.com,
>right? But it doesn't know what dreamhost.com is yet.
>
>So, really, to state this in another way.. I'm setting up a server for
>a new domain. DNS is installed and it's responding to all of the zones
>that it needs to respond to, but when I connect it to the Internet,
>where would I start getting domains resolving with my nameserver? The
>first place to start would be my registrar for the server's base name
>(i.e. if it's ns1.mysite.com, I'd start with the registrar for
>mysite.com), and I'd set its name servers to my name server. But
>exactly, how? By IP address?
>
>Anyway. This is a problem that is driving me nuts trying to figure out
>.
>
>Thanks in advance!

The parent zone has a copy of the address records for the
nameserver and returns them along with the referral to the
nameservers.

When you are asked to register a zone you are asked for the
nameservers *name*. It the nameserver is within the zone
you are registering (or is below the parent zone) you will
also be asked to register the nameserver. Then you do that
you will supply the nameserver's address(es). These addresses
are supposed to be *copies* of the addresses in the zone
itself.

When you change the address of a nameserver you need to
update both the address records in the zone and the address
registered with the parent server.

Failure to keep these consistant will cause lookup failures.
Failure to have address records in the zone will cause lookup
failures.

Mark

e.g.
The COM servers (A.GTLD-SERVERS.NET in this case)
return a referral (AUTHORITY SECTION) along with the glue
(copy) records (ADDITIONAL SECTION).

; <<>> DiG 9.3.2-P2 <<>> www.google.com +norec @A.GTLD-SERVERS.NET
; (2 servers found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16568
;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 4

;; QUESTION SECTION:
;www.google.com. IN A

;; AUTHORITY SECTION:
google.com. 172800 IN NS ns1.google.com.
google.com. 172800 IN NS ns2.google.com.
google.com. 172800 IN NS ns3.google.com.
google.com. 172800 IN NS ns4.google.com.

;; ADDITIONAL SECTION:
ns1.google.com. 172800 IN A 216.239.32.10
ns2.google.com. 172800 IN A 216.239.34.10
ns3.google.com. 172800 IN A 216.239.36.10
ns4.google.com. 172800 IN A 216.239.38.10

;; Query time: 277 msec
;; SERVER: 2001:503:a83e::2:30#53(2001:503:a83e::2:30)
;; WHEN: Thu Jan 4 09:54:00 2007
;; MSG SIZE rcvd: 168

>---
>Keith Gable
>http://www.ignition-project.com/
>