GTLD Servers Report Different IP Address Than Zone Files
phn at icke-reklam.ipsec.nu
phn at icke-reklam.ipsec.nu
Fri Mar 26 18:36:24 UTC 2004
Dennis Julien <dennis.julien at cloakware.com> wrote:
> Greetings:
> Can anyone shed some light on the reasons why GTLD servers would return=
a
> different IP for a given hostname than is indicated within an active zo=
ne
> file?
> For example (using dnsstuff.com):
> Searching for A record for www.cloakware.com at a.root-servers.net: Go=
t
> referral to B.GTLD-SERVERS.NET.
> Searching for A record for www.cloakware.com at B.GTLD-SERVERS.NET.:
> Reports www.cloakware.com.
> www.cloakware.com. A IN 172800 207.61.93.166
> cloakware.com. NS IN 172800 mag2.magmacom.com.
> cloakware.com. NS IN 172800 ns1.cloakware.com.
> mag2.magmacom.com. A IN 172800 206.191.0.140
> ns1.cloakware.com. A IN 172800 207.61.93.165
> But, the zone file contains the following A record (with the correct IP=
):
> www IN A 206.191.60.52
> Both DNS servers for 'cloakware.com' reference the correct IP, but look=
ups
> continue to point back to 207.61.93.166. Any help in tracking this dow=
n
> would be _greatly_ appreciated.
My guess is that www.cloakware.com. is used as glue-record for some
other zone( the TTL indicates it's origin in .com zone ) :
;; ANSWER SECTION:
www.cloakware.com. 2D IN A 207.61.93.166
> __
> Dennis
--=20
Peter H=E5kanson =20
IPSec Sverige ( At Gothenburg Riverside )
Sorry about my e-mail address, but i'm trying to keep spam out=
,
remove "icke-reklam" if you feel for mailing me. Thanx.
More information about the bind-users
mailing list