How does DNS replication work?

Brad Knowles brad.knowles at skynet.be
Thu Aug 9 16:30:11 UTC 2001


At 4:48 AM -0700 8/9/01, Christopher Dillon wrote:

>  I finally submitted the form that would update my glue record.  I did
>  a dig on  ns1.fuzzylemon.net and of course it's still 24.15.185.13.
>  The form that I submitted will change this to 209.190.228.10.

	Okay, good.

>  I have ns1.fuzzylemon.net as the SOA for fuzzylemon.net
>
>  all the world needs to know is that ns1.fuzzylemon.net answers
>  anything under fuzzylemon.net

	 Now that we have this information, we can run tools like "doc" 
and DNS Expert Professional 1.6 (see 
<http://www.menandmice.com/2000/2100_dns_expert.html>) on this domain 
name, and you can get useful information such as this:

% doc -d fuzzylemon.net
Doc-2.2.3: doc -d fuzzylemon.net
Doc-2.2.3: Starting test of fuzzylemon.net.   parent is net.
Doc-2.2.3: Test date - Thu Aug  9 12:25:43 EDT 2001
DEBUG: digging @a.gtld-servers.net. for soa of net.
soa @a.gtld-servers.net. for net. has serial: 2001080801
DEBUG: digging @b.gtld-servers.net. for soa of net.
soa @b.gtld-servers.net. for net. has serial: 2001080801
DEBUG: digging @c.gtld-servers.net. for soa of net.
soa @c.gtld-servers.net. for net. has serial: 2001080801
DEBUG: digging @d.gtld-servers.net. for soa of net.
soa @d.gtld-servers.net. for net. has serial: 2001080801
DEBUG: digging @e.gtld-servers.net. for soa of net.
soa @e.gtld-servers.net. for net. has serial: 2001080801
DEBUG: digging @f.gtld-servers.net. for soa of net.
soa @f.gtld-servers.net. for net. has serial: 2001080801
DEBUG: digging @g.gtld-servers.net. for soa of net.
soa @g.gtld-servers.net. for net. has serial: 2001080801
DEBUG: digging @h.gtld-servers.net. for soa of net.
soa @h.gtld-servers.net. for net. has serial: 2001080801
DEBUG: digging @i.gtld-servers.net. for soa of net.
soa @i.gtld-servers.net. for net. has serial: 2001080801
DEBUG: digging @j.gtld-servers.net. for soa of net.
soa @j.gtld-servers.net. for net. has serial: 2001080801
DEBUG: digging @k.gtld-servers.net. for soa of net.
soa @k.gtld-servers.net. for net. has serial: 2001080801
DEBUG: digging @l.gtld-servers.net. for soa of net.
soa @l.gtld-servers.net. for net. has serial: 2001080801
DEBUG: digging @m.gtld-servers.net. for soa of net.
soa @m.gtld-servers.net. for net. has serial: 2001080801
SOA serial #'s agree for net. domain
Found 2 NS and 2 glue records for fuzzylemon.net. 
@a.gtld-servers.net. (non-AUTH)
Found 2 NS and 2 glue records for fuzzylemon.net. 
@b.gtld-servers.net. (non-AUTH)
Found 2 NS and 2 glue records for fuzzylemon.net. 
@c.gtld-servers.net. (non-AUTH)
Found 2 NS and 2 glue records for fuzzylemon.net. 
@d.gtld-servers.net. (non-AUTH)
Found 2 NS and 2 glue records for fuzzylemon.net. 
@e.gtld-servers.net. (non-AUTH)
Found 2 NS and 2 glue records for fuzzylemon.net. 
@f.gtld-servers.net. (non-AUTH)
Found 2 NS and 2 glue records for fuzzylemon.net. 
@g.gtld-servers.net. (non-AUTH)
Found 2 NS and 2 glue records for fuzzylemon.net. 
@h.gtld-servers.net. (non-AUTH)
Found 2 NS and 2 glue records for fuzzylemon.net. 
@i.gtld-servers.net. (non-AUTH)
Found 2 NS and 2 glue records for fuzzylemon.net. 
@j.gtld-servers.net. (non-AUTH)
Found 2 NS and 2 glue records for fuzzylemon.net. 
@k.gtld-servers.net. (non-AUTH)
Found 2 NS and 2 glue records for fuzzylemon.net. 
@l.gtld-servers.net. (non-AUTH)
Found 2 NS and 2 glue records for fuzzylemon.net. 
@m.gtld-servers.net. (non-AUTH)
DNServers for net.
    === 0 were also authoritatve for fuzzylemon.net.
    === 13 were non-authoritative for fuzzylemon.net.
Servers for net. (not also authoritative for fuzzylemon.net.)
    === agree on NS records for fuzzylemon.net.
DEBUG: domserv = ns1.fuzzylemon.net. ns1.granitecanyon.com.
NS list summary for fuzzylemon.net. from parent (net.) servers
   == ns1.fuzzylemon.net. ns1.granitecanyon.com.
digging @ns1.fuzzylemon.net. for soa of fuzzylemon.net.
soa @ns1.fuzzylemon.net. for fuzzylemon.net. serial:
ERROR: no SOA record for fuzzylemon.net. from ns1.fuzzylemon.net.
digging @ns1.granitecanyon.com. for soa of fuzzylemon.net.
soa @ns1.granitecanyon.com. for fuzzylemon.net. serial:
ERROR: no SOA record for fuzzylemon.net. from ns1.granitecanyon.com.
SYSerr: No servers for fuzzylemon.net. returned SOAs ...
Summary:
    YIKES: doc aborted while testing fuzzylemon.net.  parent net.
    ERRORS found for fuzzylemon.net. (count: 2)
    Incomplete test for fuzzylemon.net. (1)
Done testing fuzzylemon.net.  Thu Aug  9 12:26:08 EDT 2001

		And this:

                               DNS Expert
                  Detailed Report for fuzzylemon.net.
        8/9/01, 6:28 PM, using the analysis setting "Everything"
======================================================================

Information
----------------------------------------------------------------------
Serial number:           N/A
Primary name server:     N/A
Primary mail server:     N/A
Number of records:       N/A


Errors
----------------------------------------------------------------------
o The server "ns1.fuzzylemon.net." did not reply
     The server "ns1.fuzzylemon.net." did not reply when it was
     queried for the name "fuzzylemon.net.".  This indicates that the
     server is not running, or it is currently unreachable.

o Non-authoritative data received from the server
   "ns1.granitecanyon.com."
     The server "ns1.granitecanyon.com." is listed as being
     authoritative for the domain, but it does not contain
     authoritative data for it.

o None of the authoritative name servers were able to provide
   information for the zone
     None of the servers which were listed as being authoritative for
     the zone contained information for the zone.  No further testing
     of this zone will be possible.


Warnings
----------------------------------------------------------------------
No warnings

----------------------------------------------------------------------
end of report



	This basically tells us that the update to the glue record hasn't 
gone out yet, and therefore your domain is not yet visible to the 
'net.

>  and if I'm understanding you guys correctly, this is going to happen
>  when the .net zone under the gTLD server replicated the .net domain??

	When they update the .net gTLD, and when that updated copy gets 
transferred to the other .net gTLD nameservers, then you should 
(hopefully) be good to go.  If not, come back and we can re-run 
"doc", "dnswalk", DNS Expert Professional, etc... and help you figure 
out what's going wrong.

-- 
Brad Knowles, <brad.knowles at skynet.be>

H4sICIFgXzsCA2RtYS1zaWcAPVHLbsMwDDvXX0H0kkvbfxiwVw8FCmzAzqqj1F4dy7CdBfn7
Kc6wmyGRFEnvvxiWQoCvqI7RSWTcfGXQNqCUAnfIU+AT8OZ/GCNjRVlH0bKpguJkxiITZqes
MxwpSucyDJzXxQEUe/ihgXqJXUXwD9ajB6NHonLmNrUSK9nacHQnH097szO74xFXqtlbT3il
wMsBz5cnfCR5cEmci0Rj9u/jqBbPeES1I4PeFBXPUIT1XDSOuutFXylzrQvGyboWstCoQZyP
dxX4dLx0eauFe1x9puhoi0Ao1omEJo+BZ6XLVNaVpWiKekxN0VK2VMpmAy+Bk7ZV4SO+p1L/
uErNRS/qH2iFU+iNOtbcmVt9N16lfF7tLv9FXNj8AiyNcOi1AQAA


More information about the bind-users mailing list