nslookup error? & IP specifying?
Brad Knowles
brad.knowles at skynet.be
Tue Jun 26 22:35:37 UTC 2001
At 8:25 AM -0700 6/26/01, Jason wrote:
> When I use nslookup mydomain.com, I get
> Server ns.mydomain.com
> Address 111.222.333.444
>
> .... error
>
> ( I can't remember the exact message, but something
> about can't find mydomain.com: Non-existent domain
> for hostname.mydomain.com
>
>
> When use dig www.mydomain.com, mail.mydomain.com,
> hostname.mydomain.com
> or nslookup www.mydomain.com, mail.mydomain.com, hostname.mydomain.com
> its seems fine
This is because nslookup is a poor tool to be using for DNS
debugging. Don't use it, and you won't get this error.
However, this does point out that you don't have reverse DNS set
up for your network, which is something you need to fix.
> I've used named-checkzone & named-checkconf, everything is okay.
> I've used the dig & DNS check tools at www.ip-plus.net, everything
> is okay except they say I need 2nd nameserver.
>
> If someone has time, can that someone check over my stuff at
> www.ip-plus.net
> or with some other tool they know of...
>
> my ip is 64.180.126.235
> and domain name is oddjobsbc.com
Hmm. Here's what the latest version of "doc" has to say about this domain:
% doc -d oddjobsbc.com
Doc-2.2.2: doc -d oddjobsbc.com
Doc-2.2.2: Starting test of oddjobsbc.com. parent is com.
Doc-2.2.2: Test date - Tue Jun 26 18:28:13 EDT 2001
DEBUG: digging @a.gtld-servers.net. for soa of com.
soa @a.gtld-servers.net. for com. has serial: 2001062600
DEBUG: digging @b.gtld-servers.net. for soa of com.
soa @b.gtld-servers.net. for com. has serial: 2001062600
DEBUG: digging @c.gtld-servers.net. for soa of com.
soa @c.gtld-servers.net. for com. has serial: 2001062600
DEBUG: digging @d.gtld-servers.net. for soa of com.
soa @d.gtld-servers.net. for com. has serial: 2001062600
DEBUG: digging @e.gtld-servers.net. for soa of com.
soa @e.gtld-servers.net. for com. has serial: 2001062600
DEBUG: digging @f.gtld-servers.net. for soa of com.
soa @f.gtld-servers.net. for com. has serial: 2001062600
DEBUG: digging @g.gtld-servers.net. for soa of com.
soa @g.gtld-servers.net. for com. has serial: 2001062600
DEBUG: digging @h.gtld-servers.net. for soa of com.
soa @h.gtld-servers.net. for com. has serial: 2001062600
DEBUG: digging @i.gtld-servers.net. for soa of com.
soa @i.gtld-servers.net. for com. has serial: 2001062600
DEBUG: digging @j.gtld-servers.net. for soa of com.
soa @j.gtld-servers.net. for com. has serial: 2001062600
DEBUG: digging @k.gtld-servers.net. for soa of com.
soa @k.gtld-servers.net. for com. has serial: 2001062600
DEBUG: digging @l.gtld-servers.net. for soa of com.
soa @l.gtld-servers.net. for com. has serial: 2001062600
DEBUG: digging @m.gtld-servers.net. for soa of com.
soa @m.gtld-servers.net. for com. has serial: 2001062600
SOA serial #'s agree for com. domain
Found 2 NS and 2 glue records for oddjobsbc.com. @a.gtld-servers.net.
(non-AUTH)
Found 2 NS and 2 glue records for oddjobsbc.com. @b.gtld-servers.net.
(non-AUTH)
Found 2 NS and 2 glue records for oddjobsbc.com. @c.gtld-servers.net.
(non-AUTH)
Found 2 NS and 2 glue records for oddjobsbc.com. @d.gtld-servers.net.
(non-AUTH)
Found 2 NS and 2 glue records for oddjobsbc.com. @e.gtld-servers.net.
(non-AUTH)
Found 2 NS and 2 glue records for oddjobsbc.com. @f.gtld-servers.net.
(non-AUTH)
Found 2 NS and 2 glue records for oddjobsbc.com. @g.gtld-servers.net.
(non-AUTH)
Found 2 NS and 2 glue records for oddjobsbc.com. @h.gtld-servers.net.
(non-AUTH)
Found 2 NS and 2 glue records for oddjobsbc.com. @i.gtld-servers.net.
(non-AUTH)
Found 2 NS and 2 glue records for oddjobsbc.com. @j.gtld-servers.net.
(non-AUTH)
Found 2 NS and 2 glue records for oddjobsbc.com. @k.gtld-servers.net.
(non-AUTH)
Found 2 NS and 2 glue records for oddjobsbc.com. @l.gtld-servers.net.
(non-AUTH)
Found 2 NS and 2 glue records for oddjobsbc.com. @m.gtld-servers.net.
(non-AUTH)
DNServers for com.
=== 0 were also authoritatve for oddjobsbc.com.
=== 13 were non-authoritative for oddjobsbc.com.
Servers for com. (not also authoritative for oddjobsbc.com.)
=== agree on NS records for oddjobsbc.com.
DEBUG: domserv = ns3.zoneedit.com. ns4.zoneedit.com.
NS list summary for oddjobsbc.com. from parent (com.) servers
== ns3.zoneedit.com. ns4.zoneedit.com.
digging @ns3.zoneedit.com. for soa of oddjobsbc.com.
soa @ns3.zoneedit.com. for oddjobsbc.com. serial: 991796110
digging @ns4.zoneedit.com. for soa of oddjobsbc.com.
soa @ns4.zoneedit.com. for oddjobsbc.com. serial: 991796110
SOA serial #'s agree for oddjobsbc.com.
Authoritative domain (oddjobsbc.com.) servers agree on NS for oddjobsbc.com.
NS list from oddjobsbc.com. authoritative servers matches list from
=== parent (com.) servers not authoritative for oddjobsbc.com.
Checking 0 potential addresses for hosts at oddjobsbc.com.
==
Summary:
No errors or warnings issued for oddjobsbc.com.
Done testing oddjobsbc.com. Tue Jun 26 18:28:19 EDT 2001
Here's what dnswalk has to say about it:
% dnswalk -alF oddjobsbc.com.
Checking oddjobsbc.com.
Getting zone transfer of oddjobsbc.com. from ns3.zoneedit.com...done.
SOA=ns3.zoneedit.com contact=dnsadmin.zoneedit.com
WARN: oddjobsbc.com A 64.21.143.17: no PTR record
WARN: www.oddjobsbc.com A 64.21.143.17: no PTR record
0 failures, 2 warnings, 0 errors.
Here's the report from "DNS Expert" from Men & Mice:
DNS Expert
Detailed Report for oddjobsbc.com.
6/27/01, 12:33 AM, using the analysis setting "Minimal"
======================================================================
Information
----------------------------------------------------------------------
Serial number: 991796110
Primary name server: ns3.zoneedit.com.
Primary mail server: mail.oddjobsbc.com.
Number of records: 6 (2 NS, 1 MX, 3 A, 0 CNAME, 0 PTR, 0 Other)
Errors
----------------------------------------------------------------------
o There is no PTR record for the host "oddjobsbc.com."
There is no PTR record available for the host "oddjobsbc.com."
which has the IP address 64.21.143.17.
Warnings
----------------------------------------------------------------------
No warnings
----------------------------------------------------------------------
end of report
Looks to me like someone unrelated to isp-plus.com currently has
this domain registered.
Note that this zone is not protected against zone transfers. You
may want to talk to your ISP about this -- they should be able to
provide this kind of security service for any zones that they host
for you.
> I'm assuming there must be something WRONG because why isn't
> my nameserver proprogated yet?... its been more then a week
The delegations are not pointing at the new servers, that's for sure.
> I was told this: ( registrars.com is my registrar )
>
> "registrars.com seem to have no capability to do things like this:
> Name server: ns.oddjobsbc.com 64.180.126.235
> i.e. it has no capability to allow specifying IP along with symbolic
> name of DNS server. "
>
> Is this neccessary, I thought the idea of proprogating you nameserver
> throughout the world was good enough?
Policy on this matter will depend on each registrar. Network
Solutions requires that you register your nameserver(s) as hosts (if
they are not already registered), and that these hosts be registered
with IP addresses. However, other registrars may choose to register
nameservers in a different manner.
I can't imagine how they'd escape the chicken-vs.-egg problem for
discovering the IP address(es) of your nameserver(s), if you don't
tell them both the name(s) and the IP address(es), however.
--
Brad Knowles, <brad.knowles at skynet.be>
/* efdtt.c Author: Charles M. Hannum <root at ihack.net> */
/* Represented as 1045 digit prime number by Phil Carmody */
/* Prime as DNS cname chain by Roy Arends and Walter Belgers */
/* */
/* Usage is: cat title-key scrambled.vob | efdtt >clear.vob */
/* where title-key = "153 2 8 105 225" or other similar 5-byte key */
dig decss.friet.org|perl -ne'if(/^x/){s/[x.]//g;print pack(H124,$_)}'
More information about the bind-users
mailing list