Tricky DNS issue....

Fri Nov 3 04:07:16 UTC 2000

Hmm. I ran dnswalk over your zone and got these:
	# ./dnswalk -Ffal esubcontractor.com.
	Checking esubcontractor.com.
	Getting zone transfer of esubcontractor.com. from =
209.163.136.253...done.
	SOA=3Dns1.websourcemedia.com      =
contact=3Dhostmaster.websourcemedia.com
	BAD: esubcontractor.com NS 209.247.122.205: Nameserver must be a =
hostname
	BAD: esubcontractor.com NS 209.163.136.253: Nameserver must be a =
hostname

	WARN: portal.esubcontractor.com A 209.247.122.200: no PTR record
	WARN: dev.v1.portal.esubcontractor.com A 10.20.0.6: no PTR record
	WARN: ss.dev.v1.portal.esubcontractor.com A 10.20.0.6: no PTR record
	WARN: staging.v1.portal.esubcontractor.com A 209.247.122.209: no PTR =
record
	WARN: admin.esubcontractor.com A 209.247.122.200: no PTR record
	WARN: dev.temp.admin.esubcontractor.com A 10.20.0.6: no PTR record
	WARN: dev.v1.admin.esubcontractor.com A 10.20.0.6: no PTR record
	WARN: staging.v1.admin.esubcontractor.com A 209.247.122.209: no PTR =
record
	WARN: secure.esubcontractor.com A 209.247.122.200: no PTR record
	WARN: dev.v1.reports.esubcontractor.com A 10.20.0.6: no PTR record
	WARN: staging.v1.reports.esubcontractor.com A 209.247.122.209: no PTR =
record
	WARN: dev.v1.esubcontractor.com A 10.20.0.6: no PTR record
	WARN: ss.dev.v1.esubcontractor.com A 10.20.0.6: no PTR record
	WARN: secure.dev.v1.esubcontractor.com A 10.20.0.6: no PTR record
	WARN: staging.v1.esubcontractor.com A 209.247.122.209: no PTR record
	WARN: secure.staging.v1.esubcontractor.com A 209.247.122.209: no PTR =
record
	WARN: dev.v2.esubcontractor.com A 10.20.0.6: no PTR record
	WARN: ss.dev.v2.esubcontractor.com A 10.20.0.6: no PTR record
	WARN: prototype.v2.esubcontractor.com A 209.247.122.209: no PTR record
	WARN: staging.v2.esubcontractor.com A 209.247.122.209: no PTR record
	WARN: www.esubcontractor.com A 209.247.122.200: no PTR record
	WARN: intranet.esubcontractor.com A 209.247.122.200: no PTR record
	WARN: dev.v1.intranet.esubcontractor.com A 10.20.0.6: no PTR record
	WARN: ss.dev.v1.intranet.esubcontractor.com A 10.20.0.6: no PTR record
	WARN: staging.v1.intranet.esubcontractor.com A 209.247.122.209: no PTR =
record
	WARN: dev.v1.siteassistant.esubcontractor.com A 10.20.0.6: no PTR =
record
	WARN: secure.dev.v1.siteassistant.esubcontractor.com A 10.20.0.6: no =
PTR record
	WARN: dev.temp.esubcontractor.com A 10.20.0.6: no PTR record
	WARN: ss.dev.temp.esubcontractor.com A 10.20.0.6: no PTR record
	0 failures, 29 warnings, 2 errors.

True enough:
	# dig esubcontractor.com. ns @209.163.136.253

	; <<>> DiG 8.2 <<>> esubcontractor.com. ns @209.163.136.253=20
	; (1 server found)
	;; res options: init recurs defnam dnsrch
	;; got answer:
	;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
	;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
	;; QUERY SECTION:
	;;      esubcontractor.com, type =3D NS, class =3D IN

	;; ANSWER SECTION:
	esubcontractor.com.     5M IN NS        209.163.136.253.
	esubcontractor.com.     5M IN NS        209.247.122.205.

	;; Total query time: 595 msec
	;; FROM: matjes to SERVER: 209.163.136.253
	;; WHEN: Fri Nov  3 12:05:56 2000
	;; MSG SIZE  sent: 36  rcvd: 94

You simply cannot have IP addresses as the RHS of NS records. There
must be the hostnames of the nameservers there !

> -----Original Message-----
> From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]On
> Behalf Of Brett Busch
> Sent: Friday, November 03, 2000 08:14
> To: 'bind-users at isc.org'
> Subject: Tricky DNS issue....
>=20
>=20
>=20
> I am having a really *wierd* problem with a domain I have and any=20
> help would
> be greatly appreciated.
>=20
> I am hosting a domain that can be seen by some nameservers and not =
seen by
> others. I have contacted Network Solutions, but they can only tell me =
that
> it is not their problem.
>=20
> The domain is esubcontractor.com
> The nameservers for esubcontractor.com are ns1.websourcemedia.com and
> calypso.thisbox.com
>=20
> I am sure that my DNS servers are set up correctly. Here is some =
nslookup
> output from them:
>=20
> The host that I am looking up is portal.esubcontractor.com
>=20
> C:\>nslookup
> Default Server:  calypso.thisbox.com
> Address:  209.163.136.253
>=20
> > portal.esubcontractor.com
> Server:  calypso.thisbox.com
> Address:  209.163.136.253
>=20
> Name:    portal.esubcontractor.com
> Address:  209.247.122.200
>=20
> > server 209.247.122.205
> Default Server:  ns1.websourcemedia.com
> Address:  209.247.122.205
>=20
> > portal.esubcontractor.com
> Server:  ns1.websourcemedia.com
> Address:  209.247.122.205
>=20
> Name:    portal.esubcontractor.com
> Address:  209.247.122.200
>=20
> >
>=20
> Everything looks fine from this end, but I have customers that=20
> cannot see my
> site, and their nameservers cannot see this host. Some examples:
>=20
> > server ns.kivex.com
> Default Server:  ns.kivex.com
> Address:  204.177.32.2
>=20
> > portal.esubcontractor.com
> Server:  ns.kivex.com
> Address:  204.177.32.2
>=20
> *** ns.kivex.com can't find portal.esubcontractor.com: Server failed
> >
>=20
> > server 204.62.131.44
> Default Server:  ts1.hotwired.com
> Address:  204.62.131.44
>=20
> > portal.esubcontractor.com
> Server:  ts1.hotwired.com
> Address:  204.62.131.44
>=20
> *** ts1.hotwired.com can't find portal.esubcontractor.com: Server =
failed
> >
>=20
>=20
> And some success stories...
>=20
> > server 209.113.65.2
> Default Server:  sod.insync.net
> Address:  209.113.65.2
>=20
> > portal.esubcontractor.com
> Server:  sod.insync.net
> Address:  209.113.65.2
>=20
> Name:    portal.esubcontractor.com
> Address:  209.247.122.200
>=20
> > server 206.109.1.1
> Default Server:  ns.neo.net
> Address:  206.109.1.1
>=20
> > portal.esubcontractor.com
> Server:  ns.neo.net
> Address:  206.109.1.1
>=20
> Name:    portal.esubcontractor.com
> Address:  209.247.122.200
>=20
> > server 207.235.34.2
> Default Server:  gator.lconn.com
> Address:  207.235.34.2
>=20
> > portal.esubcontractor.com
> Server:  gator.lconn.com
> Address:  207.235.34.2
>=20
> Name:    portal.esubcontractor.com
> Address:  209.247.122.200
>=20
> I thought this may have something to do with the root name servers but =
I
> cannot find anyone who is willing to help. The beauty of dns is that
> everyone minds their own boat but the downside is that NSI has=20
> used that to
> clear themselves of responsibility.
>=20
> This is becoming a real problem, any help would be appreciated. I =
would be
> really happy to find out that this is my fault, so I could fix it=20
> and put it
> behind me.
>=20
> Thanks,
>=20
> Brett Busch
> bbusch at websourcemedia.com
>=20
>=20
>=20
>=20