issues with mcd.com DNS

[Mark_Andrews at isc.org]

> Mark_Andrews at isc.org wrote:
> 
> > 
> > 
> > 	ns.mcdkorea.co.kr only has glue.  According to the zone it
> > 	does not exist.   Once the cache learns that ns.mcdkorea.co.kr
> > 	doesn't exist lookups will fail.
> > 
> 
> 
> But the catch already has a good answer cached, and a dig done against 
> the cache (run on the same box as the cache) succeeds, while a dig from 
> the same/24 as the cache, against the same cache, fails.  If what you 
> say is correct, I would (with my admittedly junior knowledge of DNS 
> compared to you) expect both digs to fail.
> 
> It's this apparent inconsistency that has me confused.  Is this correct 
> behavior?

	From the previous mail.  216.64.206.205 != 216.64.213.4
 
; <<>> DiG 9.2.1 <<>> mx mcdkorea.co.kr
;; SERVER: 216.64.206.205#53(216.64.206.205)

; <<>> DiG 8.2 <<>> mx mcdkorea.co.kr @dcns2.ch1.ummail.com
; (1 server found)
;; res_nsend to server dcns2.ch1.ummail.com  216.64.213.4: Connection timed out

	Since you have a timeout I would also be looking at firewall
	settings.  "dig +norec version.bind txt chaos @dcns2.ch1.ummail.com"
	should verify reachability (also with +vc for TCP).

	Mark

> Thanks,
> 
> Dave
> 
> -- 
> --------------------------------------------------------
> Dave Lugo   dlugo at etherboy.com    LC Unit #260   TINLC
> Have you hugged your firewall today?   No spam, thanks.
> --------------------------------------------------------
> Are you the police?  . . . .  No ma'am, we're sysadmins.
> 
> 
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at isc.org