[cobalt-users] Re:Primary,secondary,auto-update,thanks

["Utopia Research Dept" <research@xxxxxxxxxxxxx>]

Hi, I can remember doing something v similar myself
All you need to do is tell your isp that you want them to make a ptr
(pointer) lets say,
the ip address that needs to resolve  (your ip address) eg 10.0.0.2 to
www.yourdomain.com
There is no point you trying to put a ptr record on your server unless you
have authority for that range of ip addresses normally a full class C . If
you have a good relationship with your isp they may agree to cname that ip
address to your name server. But it gets fiddly ! Unless you change your ptr
/ reverse records regularly I would have thought you should let you isp put
ptr record in for you . And remember an ip address can only have one ptr
record but might have many A records . And the ptr record MUST  have a
matching A record.
PTR REVERSE POINTER all mean the same thing.
If you can get hold of "DNS and BIND" by Paul Albtz & Cricket Liu (O'Reilly)
4th edition.
It sorted me out !!!
Hope this helps - good luck
martin
Utopia Coms

Message: 12
Date: Sat, 16 Feb 2002 05:43:10 +0200
To: cobalt-users@xxxxxxxxxxxxxxx
From: Patrick <rockdog@xxxxxxxxxxx>
Subject: [cobalt-users] Re:Primary,secondary,auto-update,thanks
Reply-To: cobalt-users@xxxxxxxxxxxxxxx

Jeff -

>FQDN=Fully Qualified Domain Name... a hostname and domain name pair,
registered as a nameserver(?)

>> on the IP I was issued and I am running a PTR record
>> for the single IP number.
>
>Why?  Did someone tell you to?

I'm running a PTR record because I want my host name, domain name to
resolve (and I agreed with my ISP I was running 'primary'.)

>> My ISP is running secondary DNS. The domain
>> resolves with Primary authority residing with me, and secondary
nameserver
>> services resolving to my ISP. This seems correct (though the primary
>> upstream PTR record was not resolving to my hostname... it now is...)
>
>What's a primary upstream PTR record?  I think you've invented a new
>term <smile>.

By "primary upstream PTR" I meant - when I did a local country domain
registration... I received a "No PTR records found" error:
>>>>>>>>>>>>>
CHECKING: Primary Server is myhost.mydomain.com at xxx.xx.xxx.xx
WARN: No PTR records?  - INFO: At xxx.xx.xxx.xx

CHECKING: secondary 1 is ns2.myisp.com at xxx.xx.xxx.xx
INFO: Name "isphost.ispdomain.com" - INFO: At xxx.xx.xxx.xx
>>>>>>>>>>>>>>.

Whereas - the hostname, domain name is resolving (on the nameserver lookup)
- and I am definitely running a PTR record (as previously recommended by
you, i.e., one PTR record per IP)... ergo... if I am running a PTR record
and the name is resolving... but the bot is telling me there are no PTR
records then the error must be somewhere else... my ISP's primary?

By upstream I meant: I'm at the end of a request chain(?) - therefore
everything else must be upstream(?) This is now fixed - with no change on
my end... though I did mention to my ISP I was seeing the error.

>> The issue is - if I add a sub-domain, i.e., another virtual site (with
it's
>> own domain name) under the same IP
>
>To start with, that's NOT a subdomain.

Okay - finally got this straight :)

>> Surely if I'm not running (a) PTR record I'm not doing Primary?
>
>Surely??? are you asking?  If so, then the answer is one has nothing to
>do with the other.

In my understanding a "Primary nameserver" resolves hostnames to ip numbers
and vice-versa. If a PTR record is part of this function - and I'm not
running a ptr record... then I can no longer be a nameserver, i.e., if I am
not resolving hostnames then I'm not running dns? I set this up with my ISP
on the understanding I was doing primary and they were doing secondary.

>Your domains are your domains.  Your reverse DNS is part of the
>in-addr.arpa domain.  It's not your domain.  It's got nothing to do with
>your domain.  You only reverse your domains in in-addr.arpa if part of
>in-addr.arpa has been delegated to you.

Don't understand the 'delegation' part - thought reverse mapping was part
of my function of running primary dns?

>> The fact that my FQDN is listed as primary nameserver on
>> the top level country DNS means it finally resolves to me (through other
>> upstream primaries, whether or not their DNS, PTR reflect mine?)
>
>Either you're making this more complex than it is, or your use of
>entirely new vocabulary just makes it seem so.

Sorry - I registered a nameserver - it has a fully-qualified domain name -
it is registered as the primary nameserver for my domain... Gee whiz... I
didn't make it complicated... I just discovered it is more complicated than
it seems :P

>Again, what does a PTR record have to do with resolving names?  Nothing
>I can see.

Thought the PTR record _resolved_ the hostname and domain name.

>Aha... a light at the end of the tunnel.  You have no idea what a PTR
>record is.

This may still be true.

> If you want
>your sites to resolve

My sites are resolving - and everything looks beautiful - including the new
domain - which will have no errors thanks to the help on this list.

Now - if I can just sort my email problem... well, the emails working...
but - it gets complicated :P Maybe next time.

Thank you all for your help.
Cheers - Patrick.
PS. Jeff - please don't feel you have to reply to this - though your input
would obviously be appreciated