| |
| |
| |
|
Comments:
<0> BT's 21st Century Network (21CN) is a network transformation project which will see the UK's telephone network move from the present AXE/System X Public Switched Telephone Network (PSTN) to an Internet Protocol (IP) system. -- news to me :o
<1> they've promised 100Mb/s cafes.
<0> nice
<0> And it will still take 10 minutes to get just a cappuccino.
<0> :)
<2> things are getting better
<3> does anyone know what causes a gtld-servers.net name server to cache a glue record for a nameserver responsible for a subdomain delegation?
<3> ie, say i have ns.us.blah.com, and ns.blah.com has an A record for this host, and an NS record delegating the us.blah.com domain to it... why would a gtld-servers.net cache the A record for ns.us.blah.com ?
<3> the problem is such a request is answered by the gtld-servers.net name servers with an A record, and never even hits our servers
<4> that's the meaning of the glue record as far as i understand it
<5> I'm with the Bonsai on this one
<3> er? the meaning of a glue record isn't 'cache this mysteriously forever'...
<3> how would a gtld server even know about my subdomain delegation? i can understand it having a glue record for our domain, but why the subdomain?
<6> what is the domain in question?
<3> this would be prov.ingenta.com
<3> is the subdomain
<3> mail.prov.ingenta.com is also the DNS server. but, *.gtld-servers.net are answering with an A record for this host, which is casuing nothing but problems
<3> any other hosts in the subdomain recurse properly
<6> what's another?
<3> edam.prov.ingenta.com
<3> works fine
<6> interesting.
<3> yeah... i'd expect gtld servers to have a glue record for the ingenta.com authoritative servers only
<3> not prov.ingenta.com
<6> was mail.prov.ingenta.com ever authoritative for any second level domains?
<3> granted if i had originally set this up, i would've made a seperate ns.prov, but that's neither here nor there, and has no bearing on the problem this is causing me
<3> yes, and it still is
<6> then that's why there's glue
<3> i moved it to a different data center, and consequently a different IP
<3> but how? as i understand it, a client would first hit the root servers, then get referred to gtld, for the .com domain, then get referred to one of the ingenta.com servers, then to mail.prov.ingenta.com. at what point did gtld find out about this address?
<3> i understand the point of glue records, but why, and how one here?
<3> and as i understand it, the glue records at the gtld level would be updated by our registrar for the ingenta.com domain, which is well and good, but how would that happen for a subdomain?
<3> i've a feeling asking verisign for enlightenment here would be quixotic at best
<3> and it's gone a full week past the ttl and such
<6> if you have a nameserver registered as such with your registrar, then there is glue for it. what domain is mail.prov.ingenta.com authoritative for?
<3> for prov.ingenta.com
<3> mail.prov is not registered with anyone.... it's just delegated by the nameservers authoritative for ingenta.com
<3> hence why i wonder... why the glue on gtld servers?
<3> there must have been a domain registered at one point, that that server was authoritative for.. that's all i can think of
<3> i'm guessing it must be a domain that was registered before my time here, has not expired, and is no longer in use
<3> so begins my hunt =/
<6> i should have been more specific. what 2nd level domain is mail.prov.ingenta.com authoritative for?
<3> luna, i figured it out a bit ago, cheers
<3> i had to think beyond ingenta.com, and found two domains that i hadn't been told about, that it was authoritative for
<3> those two weren't subdomains, hence why the registrar had the host record, and hence why the glue record was there
Return to
#dns
or
Go to some related
logs:
breezy libasound
blue screen while installing xp
#linux
#lisp
netdaemon gentoo
Apachez birthday
error wile loading shared libraries +linux
mvangel8
This program cannot start until you start the dbus session service.
#perl
|
|