Eric said, "It will take up to 48 hours to complete the global
propagation. Hopefully after that, all will work :-)"

Well, the global propagation period is over and when I try to ping
www.kungfugamers.com I can see packets coming to my server box /trying/
to resolve the domain; however, it still doesn't seem to be working.

Specifically, if I issue a dig command it works great (I think), but if
I issue a ping command, it fails.  See results below:

> ping www.kungfugamers.com
ping: unknown host www.kungfugamers.com

> dig @68.15.153.133 a www.kungfugamers.com
 
; <<>> DiG 9.2.2rc1 <<>> @68.15.153.133 a www.kungfugamers.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52385
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1
 
;; QUESTION SECTION:
;www.kungfugamers.com.          IN      A
 
;; ANSWER SECTION:
www.kungfugamers.com.   86400   IN      A       68.15.153.133
 
;; AUTHORITY SECTION:
kungfugamers.com.       259200  IN      NS      a.ns.kungfugamers.com.
 
;; ADDITIONAL SECTION:
a.ns.kungfugamers.com.  259200  IN      A       68.15.153.133
 
;; Query time: 11 msec
;; SERVER: 68.15.153.133#53(68.15.153.133)
;; WHEN: Sat Nov 22 12:35:17 2003
;; MSG SIZE  rcvd: 89

If I do a tcpdump when I issue the ping command, I see this:

> tcpdump -i eth1 | grep kungfugamers
01:26:50.613933 wsip-68-15-153-133.hr.hr.cox.net.32771 >
ns1.hr.cox.net.domain:  64102+ A? www.kungfugamers.com. (38) (DF)
01:26:50.640367 nrfkdnss01.rd.hr.cox.net.55048 >
wsip-68-15-153-133.hr.hr.cox.net.domain:  2889 [1au] A?
www.kungfugamers.com. (49) (DF)
01:26:52.643584 nrfkdnss01.rd.hr.cox.net.55048 >
wsip-68-15-153-133.hr.hr.cox.net.domain:  39214 [1au] A?
www.kungfugamers.com. (49) (DF)
01:26:54.654252 nrfkdnss01.rd.hr.cox.net.55048 >
wsip-68-15-153-133.hr.hr.cox.net.domain:  44595 [1au] A?
www.kungfugamers.com. (49) (DF)
01:26:54.694642 nrfkdnss01.rd.hr.cox.net.55048 >
wsip-68-15-153-133.hr.hr.cox.net.domain:  31431 [1au] A6?
shire.kungfugamers.com. (51) (DF)
01:26:54.701554 nrfkdnss01.rd.hr.cox.net.55048 >
wsip-68-15-153-133.hr.hr.cox.net.domain:  1971 [1au] A6?
mordor.kungfugamers.com. (52) (DF)
01:26:55.622348 wsip-68-15-153-133.hr.hr.cox.net.32772 >
ns1.at.cox.net.domain:  64102+ A? www.kungfugamers.com. (38) (DF)
01:26:55.664038 lkhndnss02.rd.at.cox.net.58754 >
wsip-68-15-153-133.hr.hr.cox.net.domain:  32913 [1au] A?
www.kungfugamers.com. (49) (DF)
01:26:56.663969 nrfkdnss01.rd.hr.cox.net.55048 >
wsip-68-15-153-133.hr.hr.cox.net.domain:  1647 A? www.kungfugamers.com.
(38) (DF)
01:26:56.715620 nrfkdnss01.rd.hr.cox.net.55048 >
wsip-68-15-153-133.hr.hr.cox.net.domain:  62888 [1au] A6?
shire.kungfugamers.com. (51) (DF)
01:26:56.715803 nrfkdnss01.rd.hr.cox.net.55048 >
wsip-68-15-153-133.hr.hr.cox.net.domain:  32079 [1au] A6?
mordor.kungfugamers.com. (52) (DF)
01:26:57.669443 lkhndnss02.rd.at.cox.net.58754 >
wsip-68-15-153-133.hr.hr.cox.net.domain:  57415 [1au] A?
www.kungfugamers.com. (49) (DF)
01:26:58.678490 nrfkdnss01.rd.hr.cox.net.55048 >
wsip-68-15-153-133.hr.hr.cox.net.domain:  59938 A? www.kungfugamers.com.
(38) (DF)
01:26:58.724300 nrfkdnss01.rd.hr.cox.net.55048 >
wsip-68-15-153-133.hr.hr.cox.net.domain:  3774 [1au] A6?
shire.kungfugamers.com. (51) (DF)
01:26:58.725045 nrfkdnss01.rd.hr.cox.net.55048 >
wsip-68-15-153-133.hr.hr.cox.net.domain:  33697 [1au] A6?
mordor.kungfugamers.com. (52) (DF)
01:26:59.679235 lkhndnss02.rd.at.cox.net.58754 >
wsip-68-15-153-133.hr.hr.cox.net.domain:  43063 [1au] A?
www.kungfugamers.com. (49) (DF)
01:26:59.720503 lkhndnss02.rd.at.cox.net.58754 >
wsip-68-15-153-133.hr.hr.cox.net.domain:  12985 [1au] A6?
shire.kungfugamers.com. (51) (DF)
01:26:59.721009 lkhndnss02.rd.at.cox.net.58754 >
wsip-68-15-153-133.hr.hr.cox.net.domain:  59122 [1au] A6?
mordor.kungfugamers.com. (52) (DF)
01:27:00.632170 wsip-68-15-153-133.hr.hr.cox.net.32771 >
ns1.hr.cox.net.domain:  64102+ A? www.kungfugamers.com. (38) (DF)
01:27:00.744656 nrfkdnss01.rd.hr.cox.net.55048 >
wsip-68-15-153-133.hr.hr.cox.net.domain:  48619 A6?
shire.kungfugamers.com. (40) (DF)
01:27:00.744958 nrfkdnss01.rd.hr.cox.net.55048 >
wsip-68-15-153-133.hr.hr.cox.net.domain:  49177 A6?
mordor.kungfugamers.com. (41) (DF)
01:27:01.689391 lkhndnss02.rd.at.cox.net.58754 >
wsip-68-15-153-133.hr.hr.cox.net.domain:  10503 A? www.kungfugamers.com.
(38) (DF)
01:27:01.729197 lkhndnss02.rd.at.cox.net.58754 >
wsip-68-15-153-133.hr.hr.cox.net.domain:  32184 [1au] A6?
shire.kungfugamers.com. (51) (DF)
01:27:01.729578 lkhndnss02.rd.at.cox.net.58754 >
wsip-68-15-153-133.hr.hr.cox.net.domain:  48860 [1au] A6?
mordor.kungfugamers.com. (52) (DF)
01:27:02.754619 nrfkdnss01.rd.hr.cox.net.55048 >
wsip-68-15-153-133.hr.hr.cox.net.domain:  16252 A6?
shire.kungfugamers.com. (40) (DF)
01:27:02.754900 nrfkdnss01.rd.hr.cox.net.55048 >
wsip-68-15-153-133.hr.hr.cox.net.domain:  53242 A6?
mordor.kungfugamers.com. (41) (DF)
01:27:03.699186 lkhndnss02.rd.at.cox.net.58754 >
wsip-68-15-153-133.hr.hr.cox.net.domain:  32859 A? www.kungfugamers.com.
(38) (DF)
01:27:03.729230 lkhndnss02.rd.at.cox.net.58754 >
wsip-68-15-153-133.hr.hr.cox.net.domain:  6148 [1au] A6?
shire.kungfugamers.com. (51) (DF)
01:27:03.729557 lkhndnss02.rd.at.cox.net.58754 >
wsip-68-15-153-133.hr.hr.cox.net.domain:  3074 [1au] A6?
mordor.kungfugamers.com. (52) (DF)
01:27:05.642026 wsip-68-15-153-133.hr.hr.cox.net.32772 >
ns1.at.cox.net.domain:  64102+ A? www.kungfugamers.com. (38) (DF)

...and so on.  It recognizes the names of the two dns authorities for
the domain (ie, mordor.kungfugamers.com and shire.kungfugamers.com) both
oth which point to my one server, which is the same server on which the
web site resides.  I really have no idea what to make of the tcpdump
output, nor do I have the slightest clue why a dig command works but a
ping doesn't since it seems that ping is finding the dns and asking for
the domain info.

Anyone have an idea of what I could try next?  I feel like I've made
some progress (I mean, NOTHING, not even dig worked before!) and I'm so
close I can taste it.  Any further help is much appreciated.  :-)

-Tom Caudron


--
[EMAIL PROTECTED] mailing list

Reply via email to