Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 Apr 2002 11:57:36 -0400
From:      "Peter Brezny" <pbrezny@purplecat.net>
To:        "Forrest W. Christian" <forrestc@imach.com>, "Peter Brezny" <pbrezny@purplecat.net>
Cc:        <freebsd-isp@FreeBSD.ORG>
Subject:   RE: Help host resolution mixup.
Message-ID:  <NEBBIGLHNDFEJMMIEGOOMEBIFBAA.pbrezny@purplecat.net>
In-Reply-To: <20020430091200.X32964-100000@workhorse.imach.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Thanks a lot for the help Forrest.

For freebsd isp related problems, I've always had helpful support from this
list, I'm glad to see that the positive supportive environment still exists
here.

Here's an example of the problem I am seeing:

Two domains both using ns1 and ns2.purplecat.net as their name servers.
domains registered at a registrar _other than_ networksolutions don't list
ip addresses related to ns1 and ns2.purplecat.net for example:

whois agrnews.org
   Domain Name: AGRNEWS.ORG
   Registrar: CORE INTERNET COUNCIL OF REGISTRARS
   Whois Server: whois.corenic.net
   Referral URL: http://www.corenic.net
   Name Server: NS1.PURPLECAT.NET
   Name Server: NS2.PURPLECAT.NET
   Updated Date: 24-apr-2002

domains registered at networksolutions.com provide incorrect ip addresses
for ns1 and ns2.purplecat.net even thought he forward lookup for these hosts
works fine, _and_ modifying the information for barbarafield.org with the
correct ip addresses at networksolutions does not fix the problem, even
though it claims that the update went through successfully:

whois barbarafield.org
   Domain Name: BARBARAFIELD.ORG
   Registrar: NETWORK SOLUTIONS, INC.
   Whois Server: whois.networksolutions.com
   Referral URL: http://www.networksolutions.com
   Name Server: NS1.PURPLECAT.NET
   Name Server: NS2.PURPLECAT.NET
   Updated Date: 05-nov-2001

...

  Domain servers in listed order:

   NS1.PURPLECAT.NET            209.16.228.148
   NS2.PURPLECAT.NET            209.16.228.149

However:
dig @a.gtld-servers.net. ns1.purplecat.net

; <<>> DiG 8.3 <<>> @a.gtld-servers.net. ns1.purplecat.net
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; QUERY SECTION:
;;      ns1.purplecat.net, type = A, class = IN

;; ANSWER SECTION:
ns1.purplecat.net.      2D IN A         208.133.44.46

;; AUTHORITY SECTION:
purplecat.net.          2D IN NS        ns1.purplecat.net.
purplecat.net.          2D IN NS        NS2.purplecat.net.

;; ADDITIONAL SECTION:
ns1.purplecat.net.      2D IN A         208.133.44.46
NS2.purplecat.net.      2D IN A         208.133.44.47

I've sent an e-mail to networksolutions with the same question but have not
heard back from them (surprise).

Peter Brezny
purplecat.net


-----Original Message-----
From: Forrest W. Christian [mailto:forrestc@imach.com]
Sent: Tuesday, April 30, 2002 11:18 AM
To: Peter Brezny
Cc: Doug Barton; freebsd-isp@FreeBSD.ORG
Subject: RE: Help host resolution mixup.


On Tue, 30 Apr 2002, Peter Brezny wrote:

> I can't really think of a more appropriate list for this kind of question
> than the freebsd-isp list, please let me know if there is one, however...

The dns-related newsgroups come to mind, that said...

> I guess the to-the-point question that I have is, is it a requirement to
> have proper reverse resolution for nameservers?

Yes and no.  In theory everything should work right.  In reality
nameservers occasionally get confused about their role in life and stop
working.  And when this occurs it usually is a problem with the local
nameservers.

I think Peter's other (implied) guess might be that there is something
seriously broken in the forward delegation of your domains, which (if it
is the case) should be taken up with the appropriate registrar.

If you post the actual domains and what brokenness you are seeing (perhaps
one that works vs one that doesn't work) generally someone on here will do
a couple of digs and be able to tell you where to look for the cause.
Saying "I'm doing something nonstandard, will this break anything?" will
probably get you more of the responses you got... I.E. we're not experts
at every concievable DNS mangling, try some other list.

- Forrest W. Christian (forrestc@imach.com) AC7DE
----------------------------------------------------------------------
The Innovation Machine Ltd.                              P.O. Box 5749
http://www.imach.com/                                Helena, MT  59604
Home of PacketFlux Technogies and BackupDNS.com         (406)-442-6648
----------------------------------------------------------------------
      Protect your personal freedoms - visit http://www.lp.org/



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?NEBBIGLHNDFEJMMIEGOOMEBIFBAA.pbrezny>