Internet Unknown (28)

[Mark Andrews]

> We have been unable to resolve =E2=80=9Cpolaris.co.in=E2=80=9D and we can't=
>  seem to figure it out.  If we run an nslookup from our DNS server we don=
> =E2=80=99t get a response from the polaris.co.in DNS server.=20=20
> 
> If we run:
> 	nslookup=09
> 	> set d2
> 	> set type=3DMX
> 	> polaris.co.in
> 
> Server:  xxxxx.yyy.com
> Address:  xxx.xxx.xxx.xxx
> 
> ;; res_nmkquery(QUERY, polaris.co.in, IN, MX)
> ------------
> SendRequest(), len 31
>     HEADER:
>         opcode =3D QUERY, id =3D 17646, rcode =3D NOERROR
>         header flags:  query, want recursion
>         questions =3D 1,  answers =3D 0,  authority records =3D 0,  additio=
> nal =3D 0
> 
>     QUESTIONS:
>         polaris.co.in, type =3D MX, class =3D IN
> 
> ------------
> timeout
> timeout
> timeout
> timeout
> SendRequest failed
> 
> =09
> Here are the results from a snoop run on our DNS server.
> 
> xxx.xxx.xxx.xxx -> 202.54.218.7 DNS C polaris.co.in. Internet MX ?
> xxx.xxx.xxx.xxx -> 202.54.70.3  DNS C polaris.co.in. Internet MX ?
> xxx.xxx.xxx.xxx -> 202.54.70.3  DNS C dns3.polaris.co.in. Internet Unknown =
> (28) ?
> xxx.xxx.xxx.xxx -> 202.54.70.3  DNS C dns1.polaris.co.in. Internet Unknown =
> (28) ?
> xxx.xxx.xxx.xxx -> 202.54.70.3  DNS C dns2.polaris.co.in. Internet Unknown =
> (28) ?
> xxx.xxx.xxx.xxx -> 202.54.70.3  DNS C polaris.co.in. Internet MX ?
> xxx.xxx.xxx.xxx -> 202.54.189.3 DNS C dns2.polaris.co.in. Internet Unknown =
> (28) ?
> xxx.xxx.xxx.xxx -> 202.54.189.3 DNS C dns1.polaris.co.in. Internet Unknown =
> (28) ?
> xxx.xxx.xxx.xxx -> 202.54.189.3 DNS C dns3.polaris.co.in. Internet Unknown =
> (28) ?
> xxx.xxx.xxx.xxx -> 202.54.189.3 DNS C polaris.co.in. Internet MX ?
> xxx.xxx.xxx.xxx -> 202.54.189.3 DNS C polaris.co.in. Internet MX ?
> 
> I would tend to think something is wrong with the polaris.co.in NS servers,=
>  but others have told me then can resolv this domain just fine.=20=20

	The polaris.co.in nameservers are not RFC 1034 compliant
	(they don't reply to EDNS (RFC 2671) queries).  Named then
	has to timeout on the EDNS queries before retrying without
	EDNS.  This can take longer than the application (nslookup)
	timeout.

	You would think that all nameservers would handle EDNS queries
	by now.  After all EDNS has been on the standards track for 5
	years now.  It only takes 1/2 a day to add support for them to
	a existing server.

Network Working Group                                            P. Vixie
Request for Comments: 2671                                            ISC
Category: Standards Track                                     August 1999


                  Extension Mechanisms for DNS (EDNS0)

	Mark
 
> Any help would be appreciated.
> 
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at isc.org