trans atlantic DNS servers

John Studarus studarus at shell.one.net
Thu Aug 19 20:48:48 UTC 1999


	I've been getting some really bizarre DNS
responses from a set of remote servers at an ISP.
I am trying to resolver g2.vod.intervu.net from 
a set of caching DNS servers (resolver0.pipex.net and
resolver1.pipex.net).  These machines are located
in the UK.  The authoritative servers for vod.intervu.net
are located in the United States.
	Several times a day these resolvers will not
answer queries for the name g2.vod.intervu.net.  However
they will resolve other queries just fine!  The ttl for
this name is short (6 minutes) - however we have setup
some other names with short ttls (tty6.intervu.net, tty9.intervu.net)
and not noticed the problem.  (Yes - the names are tty6 - a
little muddled communications - should have been ttl6.intervu.net).
	Any ideas why these two resolvers refuse to
answer this name?  Other machines in the States and the UK
resolve the names just fine!  I've been using dig and
dnsquery via udp and tcp.  With udp I send the query and
never receive a reply.  With tcp I send the query and
then the socket closes.
	We also tested with a four 'octet' hostname -
www.staging.intervu.net and never notice the problem!
	Anyone have ideas?  I need to find out
from Pipex what type of DNS servers they are running.

		-John



-- 
John Studarus <studarus at one.net>


More information about the bind-users mailing list