don't shoot me/ can we really use the primary i.p. also for a name server???

[DWHS.net]

I hate to be a broken record but is anyone doing this with 100% success.

It's seems weird to me that you can use the promary i.p. for a name server without some conflicts.

But it would save a ton of i.p.'s :]

Thanks all, Charles

[ozzi4648]

Originally posted by DWHS.net
I hate to be a broken record but is anyone doing this with 100% success.

It's seems weird to me that you can use the promary i.p. for a name server without some conflicts.

But it would save a ton of i.p.'s :]

Thanks all, Charles

Yes you can, its saves on 1 spare ip that you could use for other things. ns1.yourdomain.com <---- main server ip, ns2.yourdomain.com <--- a spare ip.

[MikeHihn]

I use the same IP for

1) My server

2) My ns1

3) My default IP for shared.

But ... I'm having problems implementing server-level SSL

[Website Rob]

There is no problem using an IP address for both, Nameserver and Shared IP addresses. As long as it not a Dedicated IP -- which "is" required for SSL.

[MikeHihn]

Originally posted by Website Rob
There is no problem using an IP address for both, Nameserver and Shared IP addresses. As long as it not a Dedicated IP -- which "is" required for SSL.

Thanks, Rob. I'm just starting with Enom, which has forced me to learn more about DNS.

My servername is server1.mydomain.com

My nameserver is ns1.mydomain.com

And my primary business site is www.mydomain.com -- on the shared IP.

I THINk I only need to change the A record for the "www" host, to a dedicated IP. Correct?

Thanks again,
-Mike

[perlchild]

Just so this doesn't turn into an even more frequently asked question than it already is on the ssl mailing lists...
SSL usually requires a dedicated ip for reverse DNS (and the fact that ssl doesn't allow host headers)
NS pointers, according to the RFCs are supposed to have proper reverse DNS as well(by the way, the RFCs also recommend all MailExchangers [that's mailservers...] also have proper reverse dns in place
one way to save on ips would be to have:

example.com. in NS example.com.
ns2.example.com. in NS example.com.
example.com. IN A [ipnumber]

and have a certificate for example.com without the www(example.com and www.example.com are both techically hosts in the example.com zone, to use proper dns terminology) To parry another FAQ, using CNAMEs without understanding them fully can cause all sorts of problems at this level...

As long as you can get reverse dns delegation for ipnumber, you should be fine.

dnsreport.com can be a useful web site with a checker that can warn you of "not quite rfc-compliant info in your domain"

The problems with ssl usually arise because the protocol itself was invented when http was a newborn... and virtual hosting a ridiculous idea, ips were plentiful...

of course back then the internet wasn't really commercial either

Ahh sometimes it makes me nostalgic

[MikeHihn]

Originally posted by perlchild
Ahh sometimes it makes me nostalgic

Is that like ..... old?

[Donna]

There are also existing issues with older versions of openSSL

Make sure you upgrade tot he latest version.

[DWHS.net]

What about using the i.p. for that is used for ns2. for a domain???

Can this be used for a domain???

Or should is be isolated for the second name server???

For example the server has 2 i.p.'s:

66.666.66.01

and

66.666.66.02

The 01 id used for the first name server, the shared accounts, and the server i.p.

Can 02 be used on another domain that is on the server???

Thanks again...

-Charles

[Website Rob]

Your example is correct, Charles. It is also a typical setup when one has their main Web site on the same Server.

I must of been half-awake with my earlier post as their is no problem with a NS IP also being a Dedicted IP -- say, using 02 in your example. The 01 IP would have to remain a Shared IP, used for Name based accounts on the Server, and would always show the Apache Test page.

[c4host]

I have 2 ip that came with the server 162 and 163 both are nameervers ns1 and ns2.
when I put in just the IP I get my web site not the apache page.

[Website Rob]

Keep 162 as the shared IP for the Server and ask your DC to make 163 a Dedicated IP for your Domain name -- this is also known as rDNS.

Make sure to allocate 163 to your Domain first, before contacting your DC, then 162 should always show the Apache test page.

When giving NS to Clients, you would continue to give them; 162 as NS1 and 163 as NS2.