Resolving a public IP to a domain name

Hi,
I own a public IP bought from an ISP.
How do I get this public IP to resolve to a domain name like https://remote.mycompany.com registered with my internet registrar?
Where do I configure the DNS to resolve the IP to a domain name?

Do I need to configure this DNS with the ISP or with the internet registar or both?
I assume I need to create the https://remote.mycompany.com subdomain first?
DonKwizoteAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

netcmhCommented:
Typically, you'd get in touch with your registrar and just point your domain name to the IP address. You can then point your ISP to resolve your domain name to your registrars DNS servers.
Jeremy WeisingerSenior Network Consultant / EngineerCommented:
Resolving an IP to a hostname requires a PTR record and is done by whoever controls the IP address. This is usually your ISP.

But if you want to resolve a domain name to an IP address (e.g. you want to host a website at remote.mycompany.com), that is done by looking up an A record. This is configured with whoever hosts the DNS for your domain. Often it is your registrar. So register the domain, then setup your A record to point to the IP address your ISP gave you.
David Johnson, CD, MVPOwnerCommented:
One really never owns either the domain name or it ip address but have the rights to use either for a specific period of time. this period could be indefinite.

Your registrar is your level of contact for your domain name and they can at the end of your period of rights then take over control of the name servers (DNS).  So your first point of contact is your domain registrar as we normal folk don't deal directly with the .org/.net/.com top level domain managers.

One of the requirements is to have 2 ns records (Name Servers) which are not supposed to be within the same subnet. You tell the registrar which name servers ip addresses and names that you will be using.  Each domain then also needs an A record that points to an ip address.

Here is a real world example.
I purchased a domain from 1and1 that was available in the .ca top level domain. 1and1 has name servers already in place but I chose to use cloudflare.com for my name servers since most domain registrars don't support the full range of DNS options that are available.  With my .CA domains it took a support call and a wait of a week for the name server change to come into effect.  There console kept telling me that there was an error.. when they fixed the console because of the TTL it was another 48 hours before the name servers were pointed to dora.cloudflare.com and mike.cloudflare.com.  At cloudflare in their management interface I had to setup all of my public facing domain records to point where I wanted them to be using either A records that point to an ip address, a cname that points to a domain address, various text records, my mx records, spf, and service records.

for items that I manage directly I have my own dns servers just for those records.. and the important A and AAAA records
so what happens is that when someone looks for remote.domain.ca here is the sequence of events
1 the .ca tld registrar looks and says I don't know about doman.ca but I know who does and forwards the request to my domain registrar who also says I don't know but I know who does and the request goes to dora.cloudflare and mike.cloudflare.com... they look in their records and say I don't have remote.domain.ca in my records but the A record points to 1.2.3.4 and maybe they know so the requests get forwarded to my ip addresses my dns then says Yes I have a record for remote.domain.ca and sends the ip address (10.10.5.2) back to my router which via nat translation then sends it out to the internet as 24.12.34.56 and then this request goes back to the ip making the request.. from now on everything is done by ip address.
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

profgeekCommented:
Let me expand on what Jeremy said.  There are two lookups that can take place:  First is a forward lookup, which translates a domain name (fully qualified domain name ... FQDN) to an IP address.  This is controlled by whomever owns the zone and editing is done on the SOA (start of authority) server designated by the zone SOA record.  Usually, you have access to editing this DNS record if you have registered the domain name.

The second type of lookup is an inverse (often called a reverse) lookup.  This translates an IP address to a domain name.  Because of the nature of the IPv4 system, this lookup is hierarchical, e.g. it is based on who is assigned to the IP block in question.  Generally, ISPs, from whom you obtain your public IP, have already created their own PTR records for the blocks of addresses assigned to them.  They are usually generic in nature, and won't point to an actual name that is used for forward lookup.

Since you are not assigned this block of IP addresses, you will not have access to the PTR records, as they are housed on a completely different DNS server than the one you are using to administer your domain.  The thing to do is to ask your ISP if it is possible for them to edit the IP address you have in their file to change it to something meaningful for you.  They may or may not allow this or have a way for you to do it.  But it's where you should start.

For more info, try this:

http://www.itworld.com/article/2833006/networking/how-to-setup-reverse-dns-and-ptr-records.html
DonKwizoteAuthor Commented:
Thanks everyone for your comments. I'm sorry if some of my questions seem strange but I'm fairly new to this. I appreciate your help

Basically, I need to https://xxx.xxx.xxx.xxx:4444 to forward to https://????????????.com:4444

I have bought the domain and SSL certificate then edited the A record's @ host to point to the IP address.

How do I go about setting up the https portion so that https://xxx.xxx.xxx.xxx:4444 forwards to https://????????????.com:4444
David Johnson, CD, MVPOwnerCommented:
for that you need a website @ https://mydomain.com to redirect to https://mydomain.com:4444 

or you would do it in your router in the forwarding section.
netcmhCommented:
You could do an html redirect on the landing page (index.html ?):

<meta http-equiv="refresh" content="0; URL=http://www.newsite.com/newurl.html">

Or

If the webserver is apache, you could use the 301 page to facilitate the redirect. Save the file as .htaccess

RewriteEngine On
RewriteRule ^(.*)$ http://www.newsite.com/$1 [L,R=301]

“L” indicates that it’s the last instruction and “R” means redirect, and “301” means a permanent redirect.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DonKwizoteAuthor Commented:
Thanks Everyone!
netcmhCommented:
You're welcome. Thanks for the grade. Good luck.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
DNS

From novice to tech pro — start learning today.