He needs to email [EMAIL PROTECTED] and ask for an RFC2317 style reverse
delegation.
Regards,
Mark
[EMAIL PROTECTED] wrote:
>
> On Wed, Sep 27, 2000 at 11:31:22AM -0400, Jan Knepper wrote:
> > [EMAIL PROTECTED] wrote:
> >
> > > > 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.
> >
> > I certainly run via a UUnet connection, but I think I am responsable for
> > 63.105.9.32/27
> > So whatever UUnet's DNS say's should come from my setup right?
>
> Well possibly. But uunet have to change their DNS to say that your DNS is
> the authoritative server for that range of addresses. They haven't done that bit.
>
> Just as the .cc people had to add an entry to say that your name servers are
> responsible for smartsoft.cc so do the 63.105.9 people have to add an entry to say
> that your name servers are responsible for 63.105.9.32/27
>
> > > 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.
> >
> > I thought before I even wrote the first message that the problem had to do with
> > reverse DNS as I think hub.FreeBSD.org is trying to find the host name for
> > 63.105.9.34. That by itself should be defined in my DNS setup as far as I know.
>
> >
> > > 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.
> >
> > Does this change anything
>
> No.
>
> > or is it still UUnet's responsability?
>
> Yes.
>
> Regards.
--
mark [EMAIL PROTECTED]
877 227 4330
