On Wed, Sep 27, 2000 at 08:44:24AM -0400, Jan Knepper wrote:
> Greg White wrote:
>
> > Just to confirm -- Mark has probably hit the nail on the head with this
> > one:
> >
> > root@frodo:~# dig -x 63.105.9.34
> >
> > ; <<>> DiG 8.2 <<>> -x
> > ;; res options: init recurs defnam dnsrch
> > ;; got answer:
> > ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 4
> > ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
> > ;; QUERY SECTION:
> > ;; 34.9.105.63.in-addr.arpa, type = ANY, class = IN
>
> OK, let me try that.
>
> > IMHO, any competent DNS admin should _never_, _ever_ permit _any_
> > address he is responsible for to be answered NXDOMAIN for a PTR record.
> > This is just unacceptably sloppy DNS admin. Lots of DNS admins do it,
> > but then again lots of DNS admins run and like M$ DNS or BIND ;).
> >
> > Grrrrrr. Incompetent DNS administration at this level really yanks my
> > chain...
>
> I do run bind and set DNS up for the first time.
> What should I change, remove or add in your opinion?
Greg isn't talking about your DNS he's talking about the people who
manage the reverse DNS, the one that answers for 63.105.9.34 which looks
to be uunet. Leastwise they're responsible for 63.105.
If it's uunet, they have to fix their DNS by either adding a reverse entry
or delegating name serving of your IP(s) to you.
As I said previously, contact your ISP to get them to fix it or contact the
folks at Freebsd.org. It's currently not a problem you can fix at your end.
Regards.
